Index of every page on this site: llms.txt
All skills
imawais-engineer avatar

/agent-workflow-design

@5ecc5ec
Run it yourself

Design reliable AI agent workflows with goals, state, tools, permissions, memory, handoffs, human approval, retries, timeouts, logging, evaluation, and security boundaries. Use when building agents, multi-step AI automation, tool-using assistants, background AI workers, autonomous workflows, or human-in-the-loop agent systems.

Use this Skill: https://skilld.dev/gh/imawais-engineer/skills/agent-workflow-design

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈88 tokens for metadata: the name and description. ≈510 when used: this file. ≈49 more on demand in 1 file.

Description uses 4.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈352 characters, or 4.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Agent Workflow Design

Principle

Use an agent only when a deterministic workflow is not enough. Design the agent as a controlled state machine with explicit tools, permissions, stop conditions, and human approval points.

Agent Design Workflow

  1. Define the objective and success criteria.
  2. Decide whether an agent is justified or whether a normal service/job is safer.
  3. Define the workflow states, transitions, and stop conditions.
  4. Define tools and the exact actions each tool may perform.
  5. Define required user approvals before external side effects.
  6. Define memory and persistence: what is stored, for how long, and why.
  7. Define retries, timeouts, cancellation, fallback, and escalation.
  8. Define logs, audit trail, cost tracking, and observability.
  9. Define evals for successful, failed, unsafe, and ambiguous runs.

Tool And Permission Rules

  • Give each tool the smallest useful permission.
  • Make external side effects explicit: sending messages, changing records, charging money, deploying, deleting, publishing, or contacting users.
  • Require approval for high-impact or irreversible actions.
  • Make tool calls idempotent when practical.
  • Validate tool inputs and outputs.
  • Store enough run state to resume or explain the workflow.

Human-In-The-Loop

Add review gates for:

  • Destructive operations
  • Financial actions
  • Security-sensitive changes
  • Customer-facing messages
  • Legal/compliance outputs
  • Bulk updates
  • Low-confidence decisions

Implementation Order

  1. Build the non-agent app workflow first when possible.
  2. Add the simplest agent loop that completes the core task.
  3. Add tool boundaries and approvals.
  4. Add persistence, run history, and visibility.
  5. Add auth, rate limits, audit logs, and abuse controls before stable release.
  6. Add evals and replayable test cases.

Done Check

Agent workflow work is done when the agent has a bounded goal, controlled tools, visible state, tested failure behavior, approval gates, auditability, and verification plus validation.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts26d2 checks · Risk LOW
  • Socket26d

    No alerts

  • Snyk26d

    Risk: LOW · No issues

Signed by skilld at 5ecc5ec. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 5 days ago.

Activeupdated last week

README badge

README badge for imawais-engineer/skills/agent-workflow-design