Is c--projects-dashclaw-route-changes safe to install?

SaferSkills independently audited c--projects-dashclaw-route-changes (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/c--projects-dashclaw-route-changes/SKILL.md · 1 file

.claude/skills/c--projects-dashclaw-route-changes/SKILL.md1.3 KB · Markdown

name: c--projects-dashclaw-route-changes

description: Make focused changes to API routes with verification.

c--projects-dashclaw-route-changes

Trigger

Use when an HTTP route or server module needs to be added or changed.

Files to inspect first

C:\Projects\DashClaw\app\api-keys\page.js
C:\Projects\DashClaw\app
C:\Projects\DashClaw\app\lib\sessionViewer.mjs
C:\Projects\DashClaw\app\api\mcp\route.js
C:\Projects\DashClaw\middleware.js

Steps

Read each file listed above before any edit.
Establish a verification baseline before any edit.
Plan the changes — list edits up front.
Apply edits in one pass; avoid re-reading the same file ≥ 3 times.
Run the project's verification command; do not declare done until it passes.

Verification gates

No new high-confidence repeated-run signals in the session's tool sequence.
No secret-output guard hits.

What not to do

Don't introduce new abstractions when an existing one fits.
Don't add error handling for scenarios that can't happen — only at system boundaries.
Don't widen scope to a refactor when the trigger calls for a focused change.

Generated by AgentLens from session acec7ebd-b7d3-4e21-8582-f9617e66b654 at 2026-05-12T21:42:09.652Z. Skill candidate distilled from 3 similar prior session(s). Review and edit before relying on it.

c--projects-dashclaw-route-changes— agent skill

Is c--projects-dashclaw-route-changes safe to install?

c--projects-dashclaw-route-changes

Trigger

Files to inspect first

Steps

Verification gates

What not to do

Audit the pieces. Scan the whole. Decide.