dangling-verify-with — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited dangling-verify-with (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.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This fixture is intentionally invalid: its relations.verify_with edge points at a non-existent sibling skill. The structural lint gate MUST reject the dangling pointer.
What it is: A deliberately broken capability skill used only by the conformance runner. Mental model: Point one relation edge at a missing target so the lint error isolates that rule. Why it exists: To give the "every relations. target must resolve" rule a failing example. What it is NOT: It is not a production skill and never routes outside the test runner. Adjacent concepts: the other negative fixtures under this directory. One-line analogy: It is a unit test's fixture, not a real skill. Common misconception:* That a negative fixture should also be lint-clean — it must not be.
Valid v8 frontmatter except a dangling relations.verify_with target.
One broken field per fixture keeps the failing assertion unambiguous.
Exercised by the gate-conformance runner; expected to fail structural lint with a dangling-relation error.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.