workflow-building

A guide for creating YAML workflow templates: written plans for repeatable processes made of connected steps. The steps can be assigned to team roles and run according to their dependencies.

In plain words
What is it for?
Use it to design recurring multi-step work involving several agents, such as processes that run daily or weekly. It is not intended for one-off or simple tasks.
Why use it?
It helps replace repeated manual coordination with a defined process that can track which step depends on which other step and run on a schedule.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/markus-global/markus/workflow-building
Any agent
npx skills add markus-global/markus --skill workflow-building
Clone the repo
git clone --depth 1 https://github.com/markus-global/markus

Made for: Claude Code, Codex.

Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,544 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.03544
Opus 5 $0.00010 $0.01772
Sonnet 5 $0.00004 $0.00709
Haiku 4.5 $0.00002 $0.00354

Measured 2d ago against content hash f488e88c64e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

workflow-building scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

templates/skills/workflow-building/SKILL.md · 468 lines

How it starts

The opening of the file, as written. The whole thing — 468 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Workflow Building

This skill teaches you how to create workflow templates — YAML-based definitions of multi-step processes that are executed as a DAG (Directed Acyclic Graph) of tasks. Each step is assigned to a team member by role and runs automatically with dependency tracking.

When to Use Workflows

Workflows are for repeatable, multi-step processes where:

  • Multiple agents need to collaborate in a defined sequence
  • Steps have clear dependencies (B waits for A to finish)
  • The same process runs repeatedly with different parameters
  • You want automatic scheduling (daily, weekly, etc.)

Do NOT use workflows for: one-off tasks, simple single-agent work, or ad-hoc coordination.

How to Create Workflows

There are two ways to create a workflow, depending on context:

For an existing (live) team

Use the workflow_create tool:

workflow_create(name: "content-publishing", yaml: "<full YAML content>")

This writes the YAML file directly to ~/.markus/teams/{teamId}/workflows/.

For a team package (builder artifact)

Write the YAML file via file_write to the team's artifact directory, then reference it in team.json:

file_write("~/.markus/builder-artifacts/teams/{team-name}/workflows/my-workflow.yaml", "<YAML content>")

In team.json, add:

{
  "team": {
    "members": [...],
    "workflows": ["workflows/my-workflow.yaml"]
  }
}

The workflow YAML files are copied to ~/.markus/teams/{teamId}/workflows/ when the team is installed.

YAML Format Reference

Top-Level Fields

name: content-publishing           # REQUIRED. Identifier (kebab-case, English)
displayName: Content Publishing    # Optional. Human-readable name (any language)
description: Research, write, ...  # REQUIRED. What this workflow does
version: "1.0.0"                   # REQUIRED. Semver

schedule:                          # Optional. Auto-trigger configuration
  every: "1d"                      #   Interval shorthand: 30m, 6h, 1d, 1w
  cron: "0 9 * * 1-5"             #   OR cron expression
  run_at: "2025-06-01T09:00:00Z"  #   OR one-shot ISO timestamp
  timezone: "Asia/Shanghai"        #   IANA timezone (default: server local)
  max_runs: 10                     #   Stop after N runs (0 = unlimited)

params:                            # Optional. User-provided or auto-generated inputs
  - name: topic                    #   Referenced as {{topic}} in step prompts
    type: string                   #   string | enum | text | agent
    label: "Content Topic"
    required: true
  - name: platform
    type: enum
    options: ["wechat", "zhihu", "xiaohongshu", "x.com"]
    default: "wechat"

steps:                             # REQUIRED. The task DAG (at least one step)
  - id: research
    name: Research Topic
    type: agent_task
    role: researcher
    prompt: "Research {{topic}} thoroughly and produce a summary."
    priority: high

Read the full file on GitHub · 468 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 468 lines · 20 tokens per session scan A f488e88c64e5

Subscribe to this mod's changes

workflow-building is a skill published in the GitHub repository markus-global/markus (157 stars, last pushed 6d ago), licensed Apache-2.0. It adds 20 tokens to every session and 3,544 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.