agentleFS
MihirokteMihirokte/agent-skills/skills/prism-status/SKILL.md

prism-status

Skill0 starsChanged 4 months agoMITView on GitHub

Reports PRISM GTR freshness/coverage by calling the `prism_status` MCP tool and formatting a detailed status report. Use when the user explicitly requests `prism_status` or asks to run PRISM status.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 1 is distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill only when the user explicitly asks for prism_status (or equivalent phrasing like “run prism status”).

    line 10
  2. Very specific:

    Call the MCP tool prism_status.

    line 14
  3. Very specific:

    Always pass root as the current workspace root path.

    line 15
  4. Very specific:

    If the user provided a specific repository path, use that as root instead.

    line 16
  5. Very specific:

    If symbolCount is 0: mention that symbol extraction appears empty.

    line 32
  6. Very specific:

    If fileCount is 0 or missing: mention the index likely failed or pointed at the wrong root.

    line 33
  7. Very specific:

    If builtAt is noticeably old relative to “now” (use judgment.

    line 34
  8. Distinctive:

    Do not invent fields that aren’t present in the tool output.

    line 38
  9. Very specific:

    If the tool call fails, report the failure and suggest re-running prism_refresh (or checking MCP server availability) before retrying …

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

PRISM Status

When to use

Use this skill only when the user explicitly asks for prism_status (or equivalent phrasing like “run prism status”).

Workflow

  1. Call the MCP tool prism_status.
    • Always pass root as the current workspace root path.
    • If the user provided a specific repository path, use that as root instead.
  2. Render a detailed report from the tool output.
  3. Provide actionable next steps when appropriate (typically prism_refresh).

Output template (detailed)

Return a response in this shape:

  • PRISM version: <metadata.prism_version> (if present)
  • Built at: <data.builtAt>
  • Files indexed: <data.fileCount>
  • Symbols indexed: <data.symbolCount>
  • GTR hash: <data.gtr_hash>

Then add an interpretation block:

  • If symbolCount is 0: mention that symbol extraction appears empty; suggest running prism_refresh, then re-run prism_status.
  • If fileCount is 0 or missing: mention the index likely failed or pointed at the wrong root; suggest verifying root and running prism_refresh.
  • If builtAt is noticeably old relative to “now” (use judgment; default threshold: ~24h): label as “possibly stale” and suggest prism_refresh.

Notes

  • Do not invent fields that aren’t present in the tool output.
  • If the tool call fails, report the failure and suggest re-running prism_refresh (or checking MCP server availability) before retrying prism_status.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.