agentsclimarketplace

Source grounding

Skill HetCreep/CoalMine/skills/source-grounding

Nine quality-canary skills for AI coding agents - code health, world-class rule completeness, grounding, supply chain, resilience, drift & more - plus the auto-cadence hooks that run them unprompted at session start and session end. Cross-agent, consent-gated, token-lean.

Install
npx -y skills add HetCreep/CoalMine --skill source-grounding

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Verify version-sensitive facts against live authoritative sources before asserting them in code or answers. Triggers on: "/source-grounding", "source-grounding", "sourcing". Standing rule — always active via CLAUDE.md. Invoke for deep verification work (API signatures, CVEs, model IDs, auth flows, deprecated patterns, security advisories).

SKILL.md

2.3 KB, as published. Nobody here has run it

Source Grounding

<!-- SHARED:LANGUAGE_HEADER -->

Standing rule — active every response. No invocation needed for routine use.

What to verify (not memory)

  • CRITICAL (always fetch or flag): API/SDK call signatures · library versions & deprecations · CVEs/security advisories · auth/crypto specs · LLM model IDs & params
  • MEDIUM (verify when unsure): package names · config keys · CLI flags · protocol specs
  • LOW/stable: math, algorithms, language syntax → memory fine

How

  1. Identify the version-sensitive claim.
  2. Name the authoritative source (official docs, advisory DB, package registry, spec, source code).
  3. Fetch (WebSearch/WebFetch/docs MCP) — or flag ⚠️ unverified: check [source].
  4. Cite at CRITICAL/MEDIUM. Don't over-verify stable facts.

Per-claim-type authoritative source map: read references/sources.md when choosing where to verify.

Source hierarchy

  1. Source code / spec / RFC — primary ground truth
  2. Official/vendor docs — authoritative secondary (honor .coalmine.json trustedDomains if set: treat those domains as additional authoritative / tier-2 sources)
  3. Multiple reputable third-party sources — triangulated
  4. Single blog — weak; corroborate first
  5. Training memory — weakest for volatile facts

Non-interactive runs: log unfetchable claims as ⚠️ UNVERIFIED and continue — never block. Interactive: when sources cannot be fetched, confirm how to proceed via ask_question.

Output

  • Verified: ✅ [claim] — source: [link/file]
  • Unverified: ⚠️ unverified — check [exact source]
  • Stable fact: no annotation needed

AUTHORITATIVE vs DIVERSE

  • AUTHORITATIVE (one ground truth): API/version/config/spec → go to the actual source code or official docs.
  • DIVERSE (triangulate ≥ 3): "what's best" / landscape / patterns → multiple repos + docs + community; note conflicts.
<!-- SHARED:ORCHESTRATION --> <!-- SHARED:ESCALATION_FOOTER -->

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.