agentsclimarketplace
Sign in

Gguard report

Skill sanjeewamadhuranga/grounding-guard/skills/gguard-report

Summarize Grounding Guard findings for this session or recent sessions — fabricated packages, unpublished versions, unresolved imports, and nonexistent git SHAs that were caught and corrected.From its SKILL.md

Install
npx -y skills add sanjeewamadhuranga/grounding-guard --skill gguard-report

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

  • 1 stars1 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.

SKILL.md

1.2 KB, as published. Nobody here has run it

Grounding Guard Report

Summarize what Grounding Guard caught.

  1. Find the session logs: ~/.cache/grounding-guard/sessions/*.jsonl. Each line is one finding event with ts, mode, verifier, severity, name, message. Prefer the file matching the current session id if known; otherwise use the most recently modified files (last 24h).
  2. Read the relevant log file(s) and aggregate:
    • Total findings by verifier (packages, imports, gitrefs) and severity (block, warn, info).
    • List each distinct fabricated reference caught (name + one-line reason).
    • Note which were blocking (Claude was forced to self-correct) vs. warnings.
  3. Present a short report:
    • Headline count ("Grounding Guard caught N fabricated references this session").
    • Table or list of findings.
    • If zero findings: say so plainly — that is the desired state.

Do not re-verify anything against registries here; this skill only reports what the hooks already logged.

Keep looking

Skills are one crate of 627,801. 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.