with-grounding — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited with-grounding (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 exercises the v8 rule non-empty project[] → grounding required. It also carries keywords so routing-quality checks have realistic activation metadata to inspect, but keywords are not schema-required.
What it is: A project-anchored skill declares which projects it belongs to (project[]) and grounds its claims in those projects' truth sources (grounding). Mental model: Project membership implies repo-specific claims, which the schema makes grounding mandatory for. Why it exists: To prove the v8 rule that a non-empty project[] requires a populated grounding block (re-anchored from the retired deployment_target: project rule). What it is NOT: It is not a portable/ambient skill (those carry no project[] and need no grounding), and public: false here marks it as not-for-marketplace, independent of grounding. Adjacent concepts: grounding, project[], drift detection, the public publishability gate. One-line analogy: Grounding is a citation; a project-anchored claim without it is hearsay. Common misconception: That publishability (public) drives the grounding requirement — it does not; project[] presence does.
The five required grounding sub-fields (subject_matter, grounding_mode, truth_sources, failure_modes, evidence_priority), an object-shaped truth_source entry with path + anchor + note, and a non-empty keywords array for routing realism. No relations, no Audit Status, no Understanding fields.
The grounding block is the contract that distinguishes a knowledge skill from a hallucinated one. A project-anchored skill (non-empty project[]) is making claims about specific local files; those claims rot when the files move. The grounding block records which files anchor the claim, how to detect drift (anchor or line_range hashing), and what failure modes appear when drift occurs. This fixture is the smallest configuration that exercises every grounding required field without depending on a sibling skills clone.
node scripts/skill-lint.js --path examples/fixture-skills/with-grounding
# expected: 0 errorsLint must accept this fixture even when the published @skill-graph/cli package is installed standalone (no sibling ../skills/skills/ clone). The truth_source path resolves under the package's own examples/fixture-skills/ tree, not under the canonical skill library.
minimal-capability.with-relations.comprehension-full.skills/ (for example skill-router or graph-audit).~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.