agentleFS
Sign inStart free
0disoft0disoft/mcp-security-proxy/.agents/skills/cli-tool/SKILL.md

cli-tool

Skill2 starsChanged 4 months agoApache-2.0View on GitHub

Use this when working on cli-tool changes in this repository scaffold.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. ThuPhuong1010/claude-factory★ 0same 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 repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the matching checklist.

    line 18
  2. Distinctive:

    Do not invent product-specific technology choices.

    line 24
  3. Distinctive:

    Do not generate fake credentials or secrets.

    line 25
  4. Very specific:

    Do not treat generated/cache/build output as source truth.

    line 26
  5. Distinctive:

    Use stable validation names only.

    line 36

≈ “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

cli-tool

Read First

  • AGENTS.md
  • VALIDATION.md
  • CHECKLIST.md
  • .agents/context-map.md

Procedure

  1. Identify the source of truth.
  2. Read the matching checklist.
  3. Make the smallest change that preserves ownership boundaries.
  4. Validate with the stable validation names from VALIDATION.md.

Never

  • Do not invent product-specific technology choices.
  • Do not generate fake credentials or secrets.
  • Do not treat generated/cache/build output as source truth.

Checklist

  • Source of truth confirmed.
  • Failure mode checklist reviewed.
  • Validation plan stated.

Validation

Use stable validation names only. If a runner command is unconfigured, report it as skipped with reason.

Final Report

List files changed, validations run, validations skipped, skip reasons, and remaining risk.

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.

Check your setup, free