agentleFS
gtskevingtskevin/skill-guide/SKILL.md

skill-guide

Skill1 starsChanged 6 months agoMITView on GitHub

Use when the user wants to discover, inspect, compare, diagnose, or choose installed Agent Skills across Codex, Claude Code, cc-switch, or plugin directories.

6 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions6 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 6

    1. amtiYo/agents★ 102same name
    2. VV1NN/skill-guide★ 5same name
    3. AttackXiaoJinJin/best-claude-skills★ 1same name
    4. psw7205/skills★ 1same name
    5. taecontrol/skills★ 1same name
    6. vancebs/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the bundled zero-dependency CLI to scan local skill metadata and generate a browser-ready HTML dashboard.

    line 12
  2. Distinctive:

    Run the default dashboard:

    line 16
  3. Very specific:

    Add --lang zh for a Chinese dashboard.

    line 22
  4. Distinctive:

    Never delete skills, install packages, or publish results based only on a generated score.

    line 32
  5. Distinctive:

    If the CLI is unavailable, report the missing file instead of silently replacing its behavior.

    line 35
  6. Very specific:

    All modes default to the current platform (auto-detected from env vars or install path).

    line 36

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Skill Guide

Overview

Use the bundled zero-dependency CLI to scan local skill metadata and generate a browser-ready HTML dashboard. Treat health scores and recommendations as local review prompts, not usage metrics or deletion decisions.

Default: Dashboard

Run the default dashboard:

node <skill-dir>/skill-guide.js --open

Add --lang zh for a Chinese dashboard. Add --refresh to force re-scan. Add --all to see skills from all platforms. Add --platform claude or --platform codex to force a specific platform view.

Sub-commands

For other modes, use sub-commands: /skill-guide: review, /skill-guide: find, /skill-guide: doctor, /skill-guide: recommend, /skill-guide: share, /skill-guide: lint. Or run node <skill-dir>/skill-guide.js --overlap to find semantically overlapping skills.

Guardrails

  • The scanner reads local metadata; it does not measure actual usage frequency.
  • Same-category suggestions and directory mentions require human review before installing, editing, or deleting anything.
  • Never delete skills, install packages, or publish results based only on a generated score.
  • The CLI only prepares evidence and questions — semantic judgment comes from the agent. Always wait for agent assessment before acting on any finding.
  • Built-in dashboard labels support English and Chinese. For other languages, summarize the result in the user's language without rewriting generated HTML unless explicitly requested.
  • If the CLI is unavailable, report the missing file instead of silently replacing its behavior.
  • All modes default to the current platform (auto-detected from env vars or install path). Cross-agent duplicates are normal — each agent needs its own skill copies. Use --all to see the full inventory across all agents.

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.