agent-workflow-packager
Agent Workflow Packager
Overview
A skill is a folder holding a SKILL.md that an agent loads when a task matches it. This skill takes a procedure that people currently paste into chats over and over, and converts it into such a folder that works in any host that implements the Agent Skills format (Claude Code, Codex and others). The result is one focused skill with a description that triggers reliably, steps with a clear end state, approval gates for risky actions, and a validator run as proof.
Hosts read skills in three layers, per the Agent Skills specification: name and description are loaded at startup for every skill (about 100 tokens), the full SKILL.md body loads only when the skill activates (under 5000 tokens recommended), and files in scripts/, references/ and assets/ load on demand. Design every packaging decision around that.
Instructions
1. Decide whether it deserves a skill
Collect evidence of repetition: past chat prompts, a runbook, merged PRs, an AGENTS.md section. A candidate has (a) inputs that look the same each time, (b) steps that mostly do not change, (c) a way to tell it is finished. If the user describes a one-off or a taste ("write cleaner code"), say so and offer a short checklist in AGENTS.md or CLAUDE.md instead. If it is a rule that must hold in every session, that also belongs in those files, not in a skill.
2. Write down the workflow as facts
Fill in six lines before drafting: who runs it, the trigger phrase they actually type, the input artifacts (PR URL, failing log, ticket, repo path), the output artifact (patch, report, file), the corrections users keep making to the agent, and the command or check that proves it is done. Ask for any line you cannot fill from the evidence; do not invent it.