agentleFS
Sign inStart free
dees91dees91/agent-skill-manager/video/AGENTS.md

agent-skill-manager / video

AGENTS.md1 starsChanged 3 months agoMITView on GitHub

This directory contains the reproducible source for the README demo animation and GitHub social preview. When updating the demo, use this order: Keep STORYBOARD.md and src/storyboard.ts aligned. Marketing copy and scene timings belong in the storyboard projection, not scattered through scene code. - Use only synthetic skill names, groups, paths, repository URLs, and counts. - Never capture the real user's home, installed skills, provider state, email, account, or filesystem inventory. - Capture UI assets from the frontend's built-in demo backend.…

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository3 other files it gives its agents.

The file

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

8 rules. About 0 are common, 4 are distinctive, and 4 are 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.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When updating the demo, use this order:

    line 8
  2. Very specific:

    Keep STORYBOARD.md and src/storyboard.ts aligned.

    line 15
  3. Distinctive:

    Use only synthetic skill names, groups, paths, repository URLs, and counts.

    line 20
  4. Distinctive:

    Never capture the real user's home, installed skills, provider state, email, account, or filesystem inventory.

    line 21
  5. Very specific:

    Update STORYBOARD.md and increment its revision.

    line 39
  6. Very specific:

    Update src/storyboard.ts and any synthetic UI captures.

    line 40
  7. Very specific:

    Run npm ci, npm run check, and npm run render.

    line 41
  8. Distinctive:

    Update the README or wiki when the public product story changes.

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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

Demo Video Agent Brief

This directory contains the reproducible source for the README demo animation and GitHub social preview.

Source Precedence

When updating the demo, use this order:

  1. The current user's request.
  2. STORYBOARD.md, the human-readable product story and review contract.
  3. src/storyboard.ts, the executable timing, copy, and asset projection.
  4. Scene and component implementation.

Keep STORYBOARD.md and src/storyboard.ts aligned. Marketing copy and scene timings belong in the storyboard projection, not scattered through scene code.

Privacy And Product Accuracy

  • Use only synthetic skill names, groups, paths, repository URLs, and counts.
  • Never capture the real user's home, installed skills, provider state, email, account, or filesystem inventory.
  • Capture UI assets from the frontend's built-in demo backend.
  • Show only functionality available in the public preview. Do not expose the dormant Discover interface until it becomes a supported public feature.

Output Contract

  • Composition: 1920x1080, 30 fps, 600 frames (20 seconds), no audio.
  • Master: out/demo-master.mp4 (generated and ignored by Git).
  • README asset: ../.github/assets/demo.gif, infinite loop, at most 10 MiB.
  • Social preview: ../.github/assets/social-preview.png, 1280x640 PNG, at most 1 MiB.
  • The GIF conversion script may reduce frame rate, palette size, or resolution in that order, but must not shorten the story without user approval.

Update Workflow

  1. Update STORYBOARD.md and increment its revision.
  2. Update src/storyboard.ts and any synthetic UI captures.
  3. Run npm ci, npm run check, and npm run render.
  4. Run npm run gif, npm run social-preview, and npm run verify.
  5. Inspect the animation and social preview at full and reduced size.
  6. Update the README or wiki when the public product story changes.

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