agentleFS
Sign inStart free
TheWatcher01TheWatcher01/skills/AGENTS.md

skills

AGENTS.md0 starsChanged 7 months agoMITView on GitHub

Central registry for agent skills used across /home/TheWatcher01/projects. Each skill follows the Agent Skills spec: - GitHub Copilot skills docs: https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/create-skills - Agent Skills spec: https://agentskills.io/specification

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Use SKILLS_INVENTORY.md instead of manually maintained static skill counts.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md 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
AGENTS.md

AGENTS.md — TheWatcher01/skills

Central registry for agent skills used across /home/TheWatcher01/projects.

Canonical Layout

  • .claude/skills/ : canonical skill source (Claude Code config + assets + instructions).
  • .github/skills/ : GitHub Copilot Chat/CLI compatible path (symlink to .claude/skills/).

Important Policy

  • openclaw/ skills must remain in openclaw and are not imported here.
  • Imported/excluded provenance is documented in SKILLS_INVENTORY.md.
  • Use SKILLS_INVENTORY.md instead of manually maintained static skill counts.

Skill Format

Each skill follows the Agent Skills spec:

<skill-name>/
├── SKILL.md
├── references/
├── scripts/
└── assets/

References

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