skill-analyzer

skill-analyzer is an agent for Claude Code from VersoXBT/skill-manager. It costs 29 tokens per session (335 once invoked), scanned A, original, MIT.

A review agent for checking Claude Code skills, including their instructions, organization, and activation wording.

In plain words
What is it for?
It reviews a skill and its reference files, then gives ratings and specific improvement suggestions.
Why use it?
It identifies unclear instructions, unreliable trigger phrases, structural problems, and integration issues that may make a skill work poorly.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions Claude Code.

Part of the skill-manager plugin — 1 skill, 1 command, 1 agent shipped together

Good fit It reviews a skill and its reference files, then gives ratings and specific improvement suggestions.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/versoxbt/skill-manager/skill-analyzer
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/VersoXBT/skill-manager

Made for: Claude Code.

Or install skill-manager, the plugin that ships this one along with the rest of its 1 skill, 1 command, 1 agent.

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 skill-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/agents/versoxbt/skill-manager/skill-analyzer/github.svg)](https://agentmods.dev/agents/versoxbt/skill-manager/skill-analyzer)
Your own site
<a href="https://agentmods.dev/agents/versoxbt/skill-manager/skill-analyzer"><img src="https://agentmods.dev/badge/agents/versoxbt/skill-manager/skill-analyzer/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 skill-analyzer

Your own site · 80×15
<a href="https://agentmods.dev/agents/versoxbt/skill-manager/skill-analyzer"><img src="https://agentmods.dev/badge/agents/versoxbt/skill-manager/skill-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 335 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.
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.00029 $0.00335
Opus 5.5 $0.00012 $0.00134
Sonnet 5.5 $0.00006 $0.00067
Haiku 4.5 $0.00003 $0.00034

Measured 1mo ago against content hash df3b3b0ef71c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

skill-analyzer 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 1mo 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.

agents/skill-analyzer.md · 50 lines

What it actually says

You are a skill quality analyst. You review Claude Code skill files (SKILL.md) for clarity and effectiveness.

Input

You will receive:

  1. A skill's SKILL.md content
  2. Its references/ contents (if any)
  3. Structural issues from the audit

What to Evaluate

  1. Trigger Reliability — Will the description reliably activate for intended use cases? Could it conflict with other skills?
  2. Instruction Clarity — Are instructions clear, actionable, and unambiguous?
  3. Content Organization — Is content well-structured? Heavy content in references/?
  4. Integration Quality — Uses Claude Code tools correctly? Works within the ecosystem?

Output

For each skill:

### [skill-name]

**Trigger Reliability:** Good/Fair/Poor — [reason]
**Instruction Clarity:** Good/Fair/Poor — [reason]
**Content Organization:** Good/Fair/Poor — [reason]
**Integration Quality:** Good/Fair/Poor — [reason]

**Top improvements:**
1. [Specific suggestion]
2. [Specific suggestion]
3. [Specific suggestion]

Constraints

  • Keep output under 300 words per skill
  • Be specific: "line 42 says X, should say Y" — not vague advice
  • Focus on quality issues, not feature suggestions
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. 1mo ago First seen · 50 lines · 29 tokens per session scan A df3b3b0ef71c

Subscribe to this mod's changes

skill-analyzer is an agent published in the GitHub repository VersoXBT/skill-manager (6 stars, last pushed 6mo ago), licensed MIT. It adds 29 tokens to every session and 335 once invoked, about $0.0001 per session on Opus 5.5. 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-31.

Related

Other agents, from other repositories

scout

Cheap read-only explorer on Haiku. Use proactively when a question needs several files read, a wide code search, or web docs fetched — anything that would pull more than 10K tokens into the main conversation. Returns a short answer with file:line references. Not worth it for one known file or a single grep.

egorfedorov/claude-context-optimizer · 68 tokens

brain-merge

Semantically merge brain knowledge from multiple Claude Code machines. Use when brain-sync or brain-join detects unstructured content (memory, CLAUDE.md) that needs intelligent merging. This agent gets smarter over time by remembering merge patterns and user preferences.

toroleapinc/claude-brain · 54 tokens

job-search

Use this agent for finding job opportunities, searching job boards, tracking applications, and researching companies. Invoke when the user needs job listings, salary data, company research, or application management. Handles LinkedIn, Indeed, TrueUp, Glassdoor, and Levels.fyi data through MCP tools. Context: User…

Aznatkoiny/zAI-Skills · 220 tokens

idea-validator

Isolated Claude Opus that critiques ideas, designs, patterns, hypotheses, or plans without context from the parent conversation. Use proactively when a non-trivial design decision needs adversarial review from a fresh perspective. Pair with Gemini second-opinion (parallel call) for two independent opinions from…

awrshift/claude-friends · 94 tokens

security-auditor

Use this agent when you need to perform a comprehensive security audit of a codebase, identify vulnerabilities, and generate a detailed security report with actionable remediation steps. This includes reviewing authentication mechanisms, input validation, data protection, API security, dependencies, and infrastructure…

andisab/swe-marketplace · 341 tokens

sync-spec-kit-agent

Analyzes implementation changes on a feature branch and updates the spec-kit specification folder (.specify/specs/ /) to reflect the current state — new requirements, architecture changes, completed tasks, research findings, and any drift from the original specification. Context: User finished implementing something…

lukaskellerstein/claude-my-marketplace · 229 tokens