agentleFS
jqaisystemsjqaisystems/jqai-ai-skills/skills/agents-md-writer/SKILL.md

agents-md-writer

Skill3 starsChanged 6 months agoMITView on GitHub

Create or update project-level AGENTS.md and CLAUDE.md guidance that maps real skills to project tasks without replacing native skill discovery. Use for cross-tool workspace instructions, scoped routing, and preserving existing project rules.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep project instructions accurate without forcing every skill to load for every task.

    line 8
  2. Distinctive:

    Read existing guidance at the workspace and relevant parent/subproject levels.

    line 10
  3. Distinctive:

    Verify referenced files exist and confirm routing/discovery with the target tool after its supported refresh.

    line 18
  4. Distinctive:

    Do not paste private profiles, inventories, source registries, or access configuration into public instructions.

    line 39

“Common” is measured: kept by at least 6 in 10 of the 4 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

Workspace Guidance Writer

Keep project instructions accurate without forcing every skill to load for every task.

  1. Read existing guidance at the workspace and relevant parent/subproject levels. Preserve unrelated rules and user edits.
  2. Inventory relevant skill locations, real folders, shared targets, missing entries, and name collisions. Do not read account settings or access files.
  3. Distinguish discovery from project routing:
    • Codex discovers repository/user .agents/skills folders and supports linked skill folders. Official guidance, checked 2026-10-14.
    • Claude Code discovers project/personal .claude/skills folders. Official guidance, checked 2026-10-14.
    • Inspect compatibility locations already in use; do not move or duplicate skills automatically.
  4. Propose a small task-specific map using verified workspace-relative references. Avoid blanket claims that a tool cannot discover skills.
  5. Show the intended diff before replacing substantive instructions. Update only requested files. A short CLAUDE.md pointer can be useful if it preserves existing load order, but is not mandatory.
  6. Verify referenced files exist and confirm routing/discovery with the target tool after its supported refresh. File existence alone is not integration success.

Example structure

# Project guidance

## Scope

These rules apply to this project. Preserve more specific subproject instructions.

## Skill routing

- For release preparation, use the installed safety-review skill when available.
- For a local-only reference, read the verified relative path listed here.

## Project constraints

Record actual project requirements and authorization boundaries.

Do not paste private profiles, inventories, source registries, or access configuration into public instructions. Do not replace, relink, or install skills as a side effect of writing guidance.

Return the diff, unresolved references/conflicts, and discovery checks performed or pending.

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.