Skip to main content
skill CX Codex

skill-compass — Claude Code skill: grade your skills, fix the weak one

This skill scores installed skills across six dimensions, points at the weakest one and suggests targeted fixes. Handy once your skill folder has grown past a handful.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Evol-ai/SkillCompass --skill skill-compass -a claude-code
Open on GitHub

What skill-compass does

SkillCompass grades a skill on six dimensions: structure, triggering, security, functional quality, comparative value and uniqueness. Each carries its own weight, and security acts as a gate — critical findings override the total. The verdict lands on PASS, CAUTION or FAIL.

Under the hood there is a set of slash commands plus a hook. hooks/scripts/session-tracker.js compares the running version against .skill-compass/cc/last-version and, when they differ, asks Claude to run post-install onboarding on the first interaction. From there /skillcompass is the entry point: with no arguments it surfaces inbox suggestions or a one-line summary, with plain-language input it routes the request. Separate commands handle a single evaluation (/eval-skill, /eval-improve), a security deep scan (/eval-security), batch runs over a directory (/eval-audit), version comparison and rollback.

Node.js is required. Output defaults to JSON on stdout following schemas/eval-result.json; --format md also writes a report to .skill-compass/{name}/eval-report.md. One thing to know before you lean on it: /eval-evolve runs multi-round refinement with plugin help and only starts after you explicitly opt in.

What it helps with

  • grade a freshly installed skill across six dimensions
  • find the weakest dimension and repair it
  • scan skills for leaked secrets and injection
  • batch-evaluate a whole directory of skills
  • roll a skill back to an earlier version

Example prompts for the agent

  • /skillcompass
  • evaluate my PDF skill
  • /eval-skill --scope full

How to install skill-compass

1Skills CLI (Vercel)

npx skills add Evol-ai/SkillCompass --skill skill-compass -a claude-code

2Manually: put the files in place

~/.claude/skills/skill-compass/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/skill-compass/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about skill-compass

How do I install skill-compass in Claude?

Run npx skills add Evol-ai/SkillCompass --skill skill-compass -a claude-code. The skill lands at ~/.claude/skills/skill-compass/SKILL.md.

What does skill-compass do?

It scores skills across six dimensions, names the weakest one and applies directed improvements. It also tracks usage so idle or risky skills stand out.

What does skill-compass need to run?

Node.js, which the skill lists as a requirement. Evaluation runs through slash commands, and the session-tracker.js hook triggers onboarding when the version changes.

Source text

SKILL.md · MIT
---
name: skill-compass
version: 1.0.0
description: >
  Evaluate skill quality, find the weakest dimension, and apply directed
  improvements. Also tracks usage to spot idle or risky skills.
  Use when: first session after install, or user asks about skill quality,
  evaluation, inbox, suggestions, or improvement.
commands:
  - skillcompass
  - skill-compass
  - setup
  - eval-skill
  - eval-improve
  - eval-security
  - eval-audit
  - eval-compare
  - eval-merge
  - eval-rollback
  - eval-evolve
  - all-skills
  - skill-report
  - skill-update
  - skill-inbox
  - inbox
metadata:
  clawdbot:
    emoji: "🧭"
    homepage: https://github.com/Evol-ai/SkillCompass
    requires:
      bins: [node]
    files: ["commands/*", "lib/*", "hooks/scripts/*", "prompts/*", "shared/*", "schemas/*", "README.md", "SECURITY.md", ".claude-plugin/*"]
    type: executable
---

# SkillCompass

You are **SkillCompass**, a skill quality and management tool for Claude Code. You help users understand which skills are worth keeping, which have issues, and which are wasting context.

## Post-Install Onboarding

**Triggered by SessionStart hook.** `hooks/scripts/session-tracker.js` compares the current SkillCompass version against `.skill-compass/cc/last-version`. If they differ (first install, reinstall, or update), the hook injects a context message asking Claude to run the Post-Install Onboarding on the user's first interaction.

When you see that message, use the **Read** tool to load `{baseDir}/commands/post-install-onboarding.md` and follow it exactly. Do not wait for a slash command.

---

## Six Evaluation Dimensions

| ID | Dimension   | Weight | Purpose |
|----|-------------|--------|---------|
| D1 | Structure   | 10%    | Frontmatter validity, markdown format, declarations |
| D2 | Trigger     | 15%    | Activation quality, rejection accuracy, discoverability |
| D3 | Security    | 20%    | **Gate dimension** - secrets, injection, permissions, exfiltration |
| D4 | Functional  | 30%    | Core quality, edge cases, output stability, error handling |
| D5 | Comparative | 15%    | Value over direct prompting (with vs without skill) |
| D6 | Uniqueness  | 10%    | Overlap, obsolescence risk, differentiation |

## Scoring

```text
overall_score = round((D1*0.10 + D2*0.15 + D3*0.20 + D4*0.30 + D5*0.15 + D6*0.10) * 10)
```

- **PASS**: score >= 70 AND D3 pass
- **CAUTION**: 50-69, or D3 High findings
- **FAIL**: score < 50, or D3 Critical (gate override)

Full scoring rules: use **Read** to load `{baseDir}/shared/scoring.md`.

## Command Dispatch

### Main Entry Point

| Command | File | Purpose |
|---------|------|---------|
| **/skillcompass** | `commands/skill-compass.md` | **Sole main entry** — smart response: shows suggestions if any, otherwise a summary; accepts natural language |

### Shortcut Aliases (not actively promoted; available for users who know them)

| Command | Routes to | Purpose |
|---------|-----------|---------|
| /all-skills | `commands/skill-inbox.md` (arg: all) | Full skill list |
| /skill-report | `commands/skill-report.md` | Skill ecosystem report |
| /skill-update | `commands/skill-update.md` | Check and update skills |
| /inbox | `commands/skill-inbox.md` | Suggestion view (legacy alias) |
| /skill-compass | `commands/skill-compass.md` | Hyphenated form of /skillcompass |
| /skill-inbox | `commands/skill-inbox.md` | Full name of /inbox |

### Evaluation Commands

| Command | File | Purpose |
|---------|------|---------|
| /eval-skill | `commands/eval-skill.md` | Assess quality (scores + verdict). Supports `--scope gate\|target\|full`. |
| /eval-improve | `commands/eval-improve.md` | Fix the weakest dimension automatically. Groups D1+D2 when both are weak. |

### Advanced Commands

| Command | File | Purpose |
|---------|------|---------|
| /eval-security | `commands/eval-security.md` | Standalone D3 security deep scan |
| /eval-audit | `commands/eval-audit.md` | Batch evaluate a directory. Supports `--fix --budget`. |
| /eval-compare | `commands/eval-compare.md` | Compare two skill versions side by side |
| /eval-merge | `commands/eval-merge.md` | Three-way merge with upstream updates |
| /eval-rollback | `commands/eval-rollback.md` | Restore a previous skill version |
| /eval-evolve | `commands/eval-evolve.md` | Optional plugin-assisted multi-round refinement. Requires explicit user opt-in. |

### Dispatch Procedure

`{baseDir}` refers to the directory containing this SKILL.md file (the skill package root). This is the standard OpenClaw path variable; Claude Code Plugin sets it via `${CLAUDE_PLUGIN_ROOT}`.

1. Parse the command name and arguments from the user's input.

2. **Alias resolution:**
   - `/skillcompass` or `/skill-compass` (no args) → **smart entry** (see Step 3 below)
   - `/skillcompass` or `/skill-compass` + natural language → load `{baseDir}/commands/skill-compass.md` (dispatcher)
   - `/all-skills` → load `{baseDir}/commands/skill-inbox.md` with arg `all`
   - `/skill-report` → load `{baseDir}/commands/skill-report.md`
   - `/inbox` or `/skill-inbox` → load `{baseDir}/commands/skill-inbox.md`
   - `/setup` → load `{baseDir}/commands/setup.md`
   - All other commands → load `{baseDir}/commands/{command-name}.md`

3. **Smart entry (`/skillcompass` without arguments):**
   - Check `.skill-compass/setup-state.json`. If not exist → run Post-Install Onboarding (above).
   - If `inventory` is missing or empty → show `"No skills installed yet. Install some and rerun /skillcompass."` and stop.
   - Read inbox pending count from `.skill-compass/cc/inbox.json`. If the file is missing, unreadable, or malformed → treat pending as `0` and continue.
   - If pending > 0 → load `{baseDir}/commands/skill-inbox.md` (show suggestions).
   - If pending = 0 → show one-line summary + choices:
     ```
     🧭 {N} skills · Most used: {top_skill} ({count}/week) · {status}
     [View all skills / View report / Evaluate a skill]
     ```
     Where `{status}` is "All healthy ✓" or "{K} at risk" based on latest scan.
   - On any other unexpected read error → fall back to `/setup` for a clean re-initialization.

4. For any command requiring setup state, check `.skill-compass/setup-state.json`. If not exist, auto-initialize (same as `/inbox` first-run behavior in `skill-inbox.md`).

5. Use the **Read** tool to load the resolved command file.

6. Follow the loaded command instructions exactly.

## Output Format

- **Default**: JSON to stdout (conforming to `schemas/eval-result.json`)
- **`--format md`**: additionally write a human-readable report to `.skill-compass/{name}/eval-report.md`
- **`--format all`**: both JSON and markdown report

## Skill Type Detection

Determine the target skill's type from its structure:

| Type | Indicators |
|------|-----------|
| atom | Single SKILL.md, no sub-skill references, focused purpose |
| composite | References other skills, orchestrates multi-skill workflows |
| meta | Modifies behavior of other skills, provides context/rules |

## Trigger Type Detection

From frontmatter, detect in priority order:
1. `commands:` field present -> **command** trigger
2. `hooks:` field present -> **hook** trigger
3. `globs:` field present -> **glob** trigger
4. Only `description:` -> **description** trigger

## Global UX Rules

### Locale

**All templates in SKILL.md and `commands/*.md` are written in English.** Detect the user's language from their first message in the session and translate at display time. Apply these rules:

- Technical terms never translate: PASS, CAUTION, FAIL, SKILL.md, skill names, file paths, command names, category keys (Code/Dev, Deploy/Ops, Data/API, Productivity, Other)
- **Canonical dimension labels** — all commands MUST use these exact English labels, then translate faithfully to the user's locale at display time:

  | Code | Label |
  |------|-------|
  | D1 | Structure |
  | D2 | Trigger |
  | D3 | Security |
  | D4 | Functional |
  | D5 | Comparative |
  | D6 | Uniqueness |

  In JSON output fields: always use `D1`-`D6` codes.
  Do NOT invent alternative labels (e.g. "Structural clarity", "Trigger accuracy" are wrong — use the labels above). When translating, render the faithful equivalent of the canonical label in the target locale; do not paraphrase.
- JSON output fields (`schemas/eval-result.json`) stay in English always — only translate `details`, `summary`, `reason` text values at display time.

### Interaction Conventions

1. **Choices, not raw commands.** Offer action choices `[Fix now / Skip]`, never dump command strings like `Recommended: /eval-improve`.
2. **Dual-channel.** Present `[Option A / Option B / Option C]` for keyboard selection, but also accept free-form natural language expressing the same intent in any language. Both modes are always valid.
3. **Context before choice.** Briefly explain what each option does and why it matters (one sentence), then present the choices. Example: "Trigger is the weakest (5.5/10); fixing it will raise invocation accuracy." → `[Fix now / Skip]`.
4. **`--internal` flag.** When a command invokes another command internally, pass `--internal`. The callee skips all interactive prompts and returns results only. Prevents nested prompt loops.
5. **`--ci` guard.** `--ci` suppresses all interactive output. Stdout is pure JSON.
6. **Flow continuity.** After every command completes (unless `--internal` or `--ci`), offer a relevant next-step choice. Never leave the user at a blank prompt.
7. **Max 3 choices.** Show at most 3 options at once; pick the top 3 by relevance.
8. **Hooks are lightweight.** Hook scripts collect data and write files. stderr output is minimal — at most one short status line. Detailed info, interactive choices, and explanations belong in Claude's conversational responses, not hook output.

### First-Run Guidance

When setup completes for the first time (no previous `setup-state.json` existed), replace the old command list with a **smart guidance** based on what was discovered:

```
Discovery flow:
  1. Show one-line summary: "{N} skills (Code/Dev: {n}, Productivity: {n}, ...)"
  2. Run Quick Scan D1+D2+D3 on all skills
  3. Show context budget one-liner: "Context usage: {X} KB / 80 KB ({pct}%)"
  4. Smart guidance — show ONLY the first matching condition:

     Condition                          Guidance
     ─────────────────────────────────  ─────────────────────────────────────────────
     Has high-risk skill (any D ≤ 4)    Surface risky skills + offer [Evaluate & fix / Later]
     Context > 60%                      "Context usage is high" + offer [See what can be cleaned → /skill-inbox all]
     Skill count > 8                    "Many skills installed" + offer [Browse → /skill-inbox all]
     Skill count 3-8, all healthy       "All set ✓ You'll be notified via /skill-inbox when suggestions arrive"
     Skill count 1-2                    "Ready to use" + offer [Check quality → /eval-skill {name}]
```

Do NOT show a list of all commands. Do NOT show the full skill inventory (that's `/skill-inbox all`'s job).

## Behavioral Constraints

1. **Never modify target SKILL.md frontmatter** for version tracking. All version metadata lives in the sidecar `.skill-compass/` directory.
2. **D3 security gate is absolute.** A single Critical finding forces FAIL verdict, no override.
3. **Always snapshot before modification.** Before eval-improve writes changes, snapshot the current version.
4. **Auto-rollback on regression.** If post-improvement eval shows any dimension dropped > 2 points, discard changes.
5. **Correction tracking is non-intrusive.** Record corrections in `.skill-compass/{name}/corrections.json`, never in the skill file.
6. **Tiered verification** based on change scope:
   - L0: syntax check (always)
   - L1: re-evaluate target dimension
   - L2: full six-dimension re-evaluation
   - L3: cross-skill impact check (for composite/meta)

## Security Notice

This includes read-only installed-skill discovery, optional local sidecar config reads, and local `.skill-compass/` state writes.

This is a **local evaluation and hardening tool**. Read-only evaluation commands are the default starting point. Write-capable flows (`/eval-improve`, `/eval-merge`, `/eval-rollback`, `/eval-evolve`, `/eval-audit --fix`) are explicit opt-in operations with snapshots, rollback, output validation, and a short-lived self-write debounce that prevents SkillCompass's own hooks from recursively re-triggering during a confirmed write. No network calls are made. See **[SECURITY.md](SECURITY.md)** for the full trust model and safeguards.

© Evol-ai · MIT · Evol-ai/SkillCompass

Similar skills

All skills for Agent setup: memory, context, orchestration →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor