agentleFS
Sign inStart free
RandyRawgustRandyRawgust/ai-knowledge-base-template/.claude/skills/workflow-author/SKILL.md

workflow-author

Skill1 starsChanged 6 months agoMITView on GitHub

Scaffold a new workflow markdown file with triggers/agents/steps frontmatter, then auto-regenerate the sibling canvas. Use when Andy says codify this as a workflow, make this a workflow, save this recipe.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Don't create a workflow for one-shot work - workflows are for recurring patterns

    line 43
  2. Distinctive:

    Don't skip the anti-patterns section - that's where the gotchas live

    line 44
  3. Distinctive:

    Don't forget triggers - without them, agents can't auto-route to the workflow

    line 45

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

When to use

Triggers: codify this as a workflow, make this a workflow, save this recipe, turn this into a workflow.

Load

  • 03 - Skills & Rules/Rules/workflow-spec.md - mandatory format
  • Existing workflows as reference: 05 - Workflows/audit-pass.md, 05 - Workflows/git-bootstrap.md

Confirm

  1. Workflow slug (lowercase-hyphens)
  2. Trigger phrases (what user words invoke it)
  3. Owning agent(s) (Builder? Auditor? Specialist?)
  4. The ordered steps (with optional [agent-name] prefix per step)

Create

05 - Workflows/<slug>.md with:

---
type: workflow
project: <AI-OS-Setup or sub-project>
name: <slug>
status: active
created: <date>
updated: <date>
agents: [<list>]
triggers: ["<phrase 1>", "<phrase 2>"]
tags: [workflow, <topic>]
---

Body sections: When to invoke, Inputs, Steps (numbered, optionally with [agent] prefix), Outputs, Status markers, Anti-patterns, Retrospective.

After creating

Workflow .canvas siblings were retired 05-17-26 — markdown-only is the current convention (see [[03 - Skills & Rules/Rules/superseded-infra]]). No canvas regen step.

Don't

  • Don't create a workflow for one-shot work - workflows are for recurring patterns
  • Don't skip the anti-patterns section - that's where the gotchas live
  • Don't forget triggers - without them, agents can't auto-route to the workflow

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