Is wrap-up safe to install?

SaferSkills independently audited wrap-up (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.

skills/wrap-up/SKILL.md · 1 file

skills/wrap-up/SKILL.md1.5 KB · Markdown

name: wrap-up

description: End-of-session ritual that audits changes, runs quality checks, captures learnings, and produces a session summary. Use when saying "wrap up", "done for the day", "finish coding", or ending a coding session.

Wrap-Up Ritual

End your coding session with intention.

Trigger

Use when ending a session, saying "wrap up", "done for now", or before closing the editor.

Workflow

Changes Audit — What files were modified? Anything uncommitted? TODOs left in code?
Quality Check — Run lint, typecheck, and tests. All passing? Any warnings?
Learning Capture — What mistakes were made? What patterns worked well? Format as [LEARN] Category: Rule
Next Session Context — What's the next logical task? Any blockers? Context to preserve?
Summary — One paragraph: what was accomplished, current state, what's next.

Commands

git status
git diff --stat

npm run lint 2>&1 | head -20
npm run typecheck 2>&1 | head -20
npm test -- --changed --passWithNoTests

Learning Categories

Navigation, Editing, Testing, Git, Quality, Context, Architecture, Performance

Guardrails

Do not skip any checklist step.
If tests are failing, flag before ending session.
If uncommitted changes exist, ask whether to commit or stash.

Output

Modified file list with uncommitted changes highlighted
Quality gate results
Captured learnings (if any)
One-paragraph session summary
Next session resume context

After completing checklist, ask: "Ready to end session?"

wrap-up— agent skill

Is wrap-up safe to install?

Wrap-Up Ritual

Trigger

Workflow

Commands

Learning Categories

Guardrails

Output

Audit the pieces. Scan the whole. Decide.