agentleFS
Sign inStart free
QuintinShawQuintinShaw/pi-dynamic-workflows/skills/workflow-authoring/SKILL.md

workflow-authoring

Skill586 starsChanged 40 days agoMITView on GitHub

Guidance for writing, editing, reviewing, and debugging JavaScript workflow code for pi-dynamic-workflows. Use when authoring or changing workflow scripts; not for merely running an existing workflow.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. IsuruMaduranga/one-code★ 50same name
    2. dynamics365ninja/d365fo-cli★ 45same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 5 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read only what the task needs:

    line 14
  2. Distinctive:

    Write or edit: start with runtime. Add pattern selection for topology, lifecycle for limits or resume, and focused recipes for the

    line 16
  3. Very specific:

    Helper task: read quality helpers only for verify or judgePanel, the retry helper only for retry, and specialized helpers only for

    line 17
  4. Distinctive:

    Review: use the review checklist, plus only the matching quality or specialized helper contracts.

    line 18
  5. Distinctive:

    Debug: use the debugging map.

    line 19
  6. Very specific:

    Routing: read registry ownership before using model, tier, phase models, or agentType.

    line 20
  7. Distinctive:

    Exact lookup or portability: start with the generated capability index.

    line 21
  8. Very specific:

    Start with literal export const meta = { name, description }.

    line 25
  9. Very specific:

    Call agent() at least once, give every call a short unique label, and return plain JSON data explicitly.

    line 26
  10. Very specific:

    Use log() for new code; console is compatibility-only.

    line 29
  11. Very specific:

    Write plain JavaScript without imports or filesystem modules.

    line 30

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

Workflow authoring

Load this skill when workflow JavaScript changes. Running an existing workflow needs no authoring reference.

Choose a branch

Read only what the task needs:

  • Write or edit: start with runtime. Add pattern selection for topology, lifecycle for limits or resume, and focused recipes for the matching concern.
  • Helper task: read quality helpers only for verify or judgePanel, the retry helper only for retry, and specialized helpers only for completenessCheck, loopUntilDry, gate, or checkpoint.
  • Review: use the review checklist, plus only the matching quality or specialized helper contracts.
  • Debug: use the debugging map.
  • Routing: read registry ownership before using model, tier, phase models, or agentType; use environment-specific names only when context supplies them.
  • Exact lookup or portability: start with the generated capability index. Follow its exhaustive-facts pointer only for constraints or support boundaries. Use versions when moving scripts between installations.

Invariants

  • Start with literal export const meta = { name, description }; declare phases as an array of used { title } objects and enter each named phase.
  • Call agent() at least once, give every call a short unique label, and return plain JSON data explicitly.
  • Pair ordered results with stable work IDs before filtering. When one agent consumes another's selected result, include both its stable ID and actual data in the downstream prompt. Treat recoverable null as missing coverage and report it.
  • Bound fan-out, loops, retries, agents, and concurrency to the task. Treat invocation-level token and time caps as opt-in user constraints, not defaults.
  • Use log() for new code; console is compatibility-only.
  • Write plain JavaScript without imports or filesystem modules. Pass nondeterminism through args; Date.now(), Math.random(), and no-argument new Date() are unavailable.

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