agentleFS
Sign inStart free
razzantrazzant/ouroboros/skills/templates/SKILL.md

Templates

Skill1.6k starsChanged 4 months agoMITView on GitHub

Starter buttons for the composer and instructions for making your own.

24 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about razzant/ouroboros

The biggest 5 of 33 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 33

Talked about on GitHub (33 times).

On GitHub · 33

28 more on GitHub

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 0

    Distinctive

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

    When the owner asks “make me a button that …”, create or edit my-buttons/SKILL.md in the installation's data-plane external skills …

    line 30
  2. Very specific:

    Never edit this bundled templates skill: updates reseed it.

    line 33
  3. Very specific:

    Keep one contribution per button and preserve the owner's other entries.

    line 35
  4. Very specific:

    Run the normal skill lifecycle: preflight → review → enable.

    line 59

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

Your own buttons

When the owner asks “make me a button that …”, create or edit my-buttons/SKILL.md in the installation's data-plane external skills directory. Resolve that directory from the current skill environment; do not put user skills in the source repository. Never edit this bundled templates skill: updates reseed it.

Keep one contribution per button and preserve the owner's other entries. Use a unique stable id, placement: composer.plus, a short label (at most 40 characters), and action.verb: draft.insert with the full requested text. These buttons insert an editable draft; only the owner's Send submits it.

Example user manifest:

---
name: my-buttons
version: 1.0.0
description: My composer buttons.
type: instruction
contributes:
  - id: next_steps
    placement: composer.plus
    label: Next steps
    action:
      verb: draft.insert
      text: "Suggest the next steps for what we are working on."
---
My personal composer shortcuts.

Run the normal skill lifecycle: preflight → review → enable. Tell the owner the button appears in the composer's “+” menu under my-buttons once enabled. For a change or removal, edit that entry and repeat the lifecycle.

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