Is customer-escalation-timeline-6f8189 safe to install?

SaferSkills independently audited customer-escalation-timeline-6f8189 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.claude/skills/customer-escalation-timeline/SKILL.md · 1 file

.claude/skills/customer-escalation-timeline/SKILL.md1.6 KB · Markdown

name: customer-escalation-timeline

description: Reconstruct customer support escalation timelines from exported tickets, event logs, handoff notes, and account context so CS, support, engineering, and CX leaders can produce a structured handoff packet, SLA/ownership risk report, and closure plan without connecting to Zendesk, Intercom, Slack, Jira, or a CRM.

Customer Escalation Timeline

Use this mirror with the full repository checkout so relative paths such as customer-escalation-timeline/scripts/customer_escalation_timeline.py resolve correctly.

Workflow

Confirm the user wants an escalation review, not live ticket modification or customer messaging.
Ask for local exports: tickets, event/conversation logs, and optional account context.
Run the local scanner when file paths are available:

python3 customer-escalation-timeline/scripts/customer_escalation_timeline.py \
  --tickets customer-escalation-timeline/scripts/fixtures/tickets.csv \
  --events customer-escalation-timeline/scripts/fixtures/events.csv \
  --accounts customer-escalation-timeline/scripts/fixtures/accounts.csv \
  --now 2026-05-21T09:00:00

Produce an escalation timeline report with handoff packet, timeline findings, controls checked, closure gate, and open questions.
Never close, reassign, delete, or edit live tickets. Do not send customer messages without human approval.

Expected fixture terms include Escalation Timeline Decision, owner_acceptance_required, customer_update_due, handoff_packet_required, and repeat_contact_or_fix_validation.

customer-escalation-timeline-6f8189— agent skill

Is customer-escalation-timeline-6f8189 safe to install?

Customer Escalation Timeline

Workflow

Audit the pieces. Scan the whole. Decide.