agentleFS
Sign inStart free
zecodzecod/claude-queue/skills/add/SKILL.md

add

Skill2 starsChanged 10 days agoMITView on GitHub

Add tasks to this project's queue file (.claude-queue.md). /queue:run then works through them one by one.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use note.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    note

    Use this skill to record progress, partial findings, hypotheses, and page-anchored evidence while investigating a long document. Call Note aggressively — any time you read a page and confirm, narrow, or update your understanding of the user's question. Triggers include "jot that down", "save this finding", "note that page 7 says X", or (more often) implicit internal signals — you just learned something and want it recoverable later. Notes persist in the session and Review can select among them. Never paraphrase notes back from memory; write them as you go.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Add the tasks below to the queue file .claude-queue.md in the project root.

    line 7
  2. Very specific:

    Add each task as a new line at the end of the file, written exactly like this: - [ ] <task>

    line 9
  3. Very specific:

    If the text holds several tasks (separated by ;, numbered, or one per line), add each one as its own line, in the same order.

    line 10
  4. Distinctive:

    Keep the user's wording. Don't change the lines already in the file.

    line 11
  5. Distinctive:

    Don't start any of the tasks.

    line 12

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

Add the tasks below to the queue file .claude-queue.md in the project root. Create the file if it doesn't exist.

  • Add each task as a new line at the end of the file, written exactly like this: - [ ] <task>
  • If the text holds several tasks (separated by ;, numbered, or one per line), add each one as its own line, in the same order.
  • Keep the user's wording. Don't change the lines already in the file.
  • Don't start any of the tasks.

Then reply with one line: how many tasks you added, how many are waiting now, and that /queue:run starts them.

Tasks: $ARGUMENTS

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