Is doncheli-drift-c55669 safe to install?

SaferSkills independently audited doncheli-drift-c55669 (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.

.agent/skills/doncheli-drift/SKILL.md · 1 file

.agent/skills/doncheli-drift/SKILL.md1.8 KB · Markdown

name: doncheli-drift

description: Detect and reconcile divergence between specs and implementation. Activate when user mentions "drift", "sync", "spec divergence", "out of sync", "spec doesn't match", "implementation differs".

Don Cheli: Spec Drift Detector

Instructions

Read the current spec files in .dc/specs/ and the relevant source code
Compare spec scenarios (Gherkin / acceptance criteria) against the actual implementation
Identify three categories of drift:

Ghost: code exists but no spec covers it
Phantom: spec exists but no code implements it
Mutant: code and spec exist but behavior diverges

For each drift finding, report: file path, spec reference, severity (critical / warning / info)
Propose a reconciliation: either update the spec or flag the code for correction
Never auto-modify code — output a reconciliation plan for human approval
Save a drift report to .dc/drift-report-<date>.md if findings exceed 3 items
If zero drift is found, confirm with a brief "No drift detected — spec and code are aligned"

Output Format

## Drift Report — <date>

### Ghost (code without spec)
- src/payments/refund.ts:42 — no spec covers the refund edge case

### Phantom (spec without code)
- specs/checkout.feature:Scenario 3 — "Apply coupon on mobile" — not implemented

### Mutant (behavior mismatch)
- specs/auth.feature:Scenario 1 expects 401 on expired token; code returns 403

### Reconciliation Plan
1. [Phantom] Implement "Apply coupon on mobile" or mark as backlog in .dc/backlog.md
2. [Mutant] Fix auth.ts to return 401 — spec is correct per RFC 7235
3. [Ghost] Add spec for refund edge case before next release

Do not use this skill when

The user only wants to run tests (use doncheli-tea instead)
The spec has not been written yet (use dc:especificar first)

doncheli-drift-c55669— agent skill

Is doncheli-drift-c55669 safe to install?

Don Cheli: Spec Drift Detector

Instructions

Output Format

Do not use this skill when

Audit the pieces. Scan the whole. Decide.