cli: Skill for Claude Code

.claude/skills/review-prompts-quality/SKILL.md

review-prompts-quality is a skill for Claude Code from archcore-ai/cli. It costs 0 tokens per session (691 once invoked), scanned A, original, Apache-2.0.

A review guide for prompt-related changes in the Archcore command-line project. It checks tool descriptions, shared agent instructions, and document templates in the project’s code changes.

In plain words
What is it for?
Use it when reviewing staged or unstaged changes to the specified Go prompt files, server instructions, and template code.
Why use it?
It helps detect unclear or inconsistent instructions before they affect how agents use tools or generate documents.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is archcore-ai/cli's own configuration. It tells Claude Code how to work on cli itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything cli configures →

Reuse

Borrowing it

Nothing to install: this file belongs to archcore-ai/cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/archcore-ai/cli/main/.claude/skills/review-prompts-quality/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/archcore-ai/cli

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for review-prompts-quality

README.md
[![agentmods](https://agentmods.dev/badge/skills/archcore-ai/cli/review-prompts-quality/github.svg)](https://agentmods.dev/skills/archcore-ai/cli/review-prompts-quality)
Your own site
<a href="https://agentmods.dev/skills/archcore-ai/cli/review-prompts-quality"><img src="https://agentmods.dev/badge/skills/archcore-ai/cli/review-prompts-quality/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for review-prompts-quality

Your own site · 80×15
<a href="https://agentmods.dev/skills/archcore-ai/cli/review-prompts-quality"><img src="https://agentmods.dev/badge/skills/archcore-ai/cli/review-prompts-quality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 691 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00691
Opus 5 $0.00000 $0.00345
Sonnet 5 $0.00000 $0.00138
Haiku 4.5 $0.00000 $0.00069

Measured 2d ago against content hash 08dbd51a9837, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

review-prompts-quality scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/review-prompts-quality/SKILL.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Review Prompts Quality

Prompt Locations in This Project

File pattern What it contains
internal/mcp/tools/*.go MCP tool descriptions (mcp.WithDescription(...)) and parameter descriptions
internal/mcp/server.go mcpServerInstructions — system context served to all AI agents
templates/templates.go Document templates with section guidance for human authors

Workflow

Step 1: Find changed prompt files

Run both commands to capture staged and unstaged changes:

git diff --cached --name-only
git diff --name-only

Filter the results to files matching these patterns:

  • internal/mcp/tools/*.go
  • internal/mcp/server.go
  • templates/templates.go

If no matching files are found, report: "No prompt-related files changed." and stop.

Step 2: Extract changed prompt content

For each matched file, read the current content of that file. Focus on:

  • internal/mcp/tools/*.go: All mcp.WithDescription(...) call arguments and parameter description strings
  • internal/mcp/server.go: The mcpServerInstructions variable and buildInstructions() function
  • templates/templates.go: The generate*Template() functions

Also run git diff HEAD -- <file> (or git diff --cached -- <file>) to see exactly what changed.

Step 3: Delegate to prompt-engineer agent

Launch the ai-kit:prompt-engineer agent with all extracted prompt content and diffs. Ask it to review each changed prompt on these four axes:

  1. Effectiveness — Does the prompt clearly communicate intent? Are instructions unambiguous and actionable? Would an AI agent follow them correctly without guessing?

  2. Best practices — For MCP tool descriptions: does it specify when to call the tool, what inputs are expected, and what the output looks like? For system instructions: is there a logical hierarchy, no contradictions, clear scope? For templates: do sections guide the author toward complete, useful content?

  3. Token cost — Is the prompt unnecessarily verbose? Identify: repeated information, overly long examples, content that could be condensed without loss. Estimate rough token impact for significant issues.

Read the full file on GitHub · 62 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago Changed 08dbd51a9837
  2. 9d ago First seen · 62 lines · 0 tokens per session scan A dd8ccac8e436

Subscribe to this mod's changes

review-prompts-quality is a skill published in the GitHub repository archcore-ai/cli (64 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 691 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.