agentleFS
Sign inStart free
LeoFusoLeoFuso/blaine/skills/task-create/SKILL.md

task-create

Skill1 starsChanged 50 days agoMITView on GitHub

Translate requests for durable work into a TaskSpec and submit through an available binding.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the TaskSpec contract and operation boundary.

    line 8
  2. Distinctive:

    Default to interactive mode and the contract's conservative cloud/sharing defaults.

    line 15
  3. Distinctive:

    Do not ask again for authorization already granted within the same scope.

    line 19
  4. Distinctive:

    Do not add workflow graphs, retry plans, or worker-specific lifecycle instructions.

    line 26

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

task-create

Read the TaskSpec contract and operation boundary.

  1. Apply BLAINE.md's Task boundary. A discussion, explanation, or short supplied-text transformation needs no Task. A follow-up to existing work may need a signal instead.
  2. Extract outcome, scope, required context, capabilities, constraints, cloud policy, and observable completion criteria. Separate user facts from assumptions.
  3. Default to interactive mode and the contract's conservative cloud/sharing defaults. Include scheduling only for timed work. Use examples if helpful; do not force the request into a coding template.
  4. Clarify missing targets, consequential permissions, or ambiguous scheduling. Do not ask again for authorization already granted within the same scope.
  5. Form the smallest complete TaskSpec. Context requirements describe what must be resolved, not everything retrieved. Check criteria can be verified independently of a worker saying it succeeded.
  6. Submit via an available creation binding. Report the returned ID and actual state. Without a binding, show the draft and explicitly say no Task has been created.

Do not add workflow graphs, retry plans, or worker-specific lifecycle instructions.

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