agentleFS
Sign inStart free
sreejithramansreejithraman/SreeStack/skills/snip-snap/SKILL.md

snip-snap

Skill1 starsChanged 17 days agoMITView on GitHub

Use when the user asks to save something for later, manage Snip Snap snips or lists, or work on a saved snip's task. Also use when an agent discovers a concrete improvement outside current and planned work.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use snipsnap --help to discover commands.

    line 8
  2. Distinctive:

    When you discover a concrete, worthwhile improvement, check the current task and any readily available plan or backlog.

    line 14
  3. Distinctive:

    When you take on a task from a saved snip, keep its ID so you can update that same snip when you finish.

    line 20
  4. Distinctive:

    Not Done and explain what remains at handoff.

    line 28
  5. Very specific:

    Use --json for results. Before changing saved data, read CLI writes for destinations, revisions, and retries.

    line 32

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

Snip Snap

Use snipsnap --help to discover commands. The CLI starts the app when needed.

Save for later

Save text when the user asks. Write deferred actions as standalone todos.

When you discover a concrete, worthwhile improvement, check the current task and any readily available plan or backlog. Save it only when it is outside both, as a note naming the area, action, and reason. Continue the current work.

Complete saved work

When you take on a task from a saved snip, keep its ID so you can update that same snip when you finish. Keep it Not Done while the work is underway.

snips copy normally marks the copied snip Done. When copying text to begin work, pass --mark-done off so copying leaves the task open.

Once you complete the work and verify the result, mark the source snip Done and confirm the update succeeded. If the work is partial or blocked, keep it Not Done and explain what remains at handoff.

Use the CLI

Use --json for results. Before changing saved data, read CLI writes for destinations, revisions, and retries. Confirm the result before reporting success. If saving fails, preserve the intended text and report it as unsaved at handoff.

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