Agent skill · operations · google-deepmind
workflow-skill-creator
Distills a completed user workflow or interaction into a reusable agent skill. Use when the user asks to turn their workflow, interaction, or multi-step process into a skill, or when they say "make this a skill", "create a skill from what we just did", "package this workflow" or similar. Do not use for creating skills from scratch without an existing workflow (use a generic skill-creator for that).
Why this skill is useful
Adds structured methods for transforming user workflows into reusable agent skills, which the AI wouldn't generate on its own.
What it needs
About 8k tokens when loaded. Last updated 2026-07-07. 2,648 stars on the source repository.
What this skill does
Workflow-to-Skill Distiller Turns a completed workflow into a reusable agent skill. Specifically, this skill extracts patterns from an interaction or workflow that already happened and packages them. [!CAUTION] You MUST complete Phase 1 (Brainstorming) before writing any code or SKILL.md content. Skipping brainstorming produces skills that are either too rigid or too vague. The brainstorming conversation is the most important part of this process. Phase 1: Brainstorming (MANDATORY) Have an iterative back-and-forth conversation with the user. Do NOT ask all questions at once. Pick 2-3 relevant questions per round from the bank below, refine your understanding, and ask follow-ups. Round 1: Understand the Workflow Start by summarizing what you observed from the workflow, then ask: 1. "Here's my understanding of the workflow: [summary]. Is this accurate? What would you change?" 2. "What are the expected inputs and outputs for this workflow?" 3. "How often do you expect to run this workflow? Is it recurring or one-off?" Round 2: Flexibility and Error Handling For each step identified in the workflow, determine its rigidity: 1. "For [step X], if the primary approach fails (e.g., API down, no results), should the agent: (a) ask you for guidance, (b) try alternative approaches automatically, or (c) fail loudly with an error?" 2. "Are there any steps where the exact method matters (e.g., must use a specific database), vs. steps where any reasonable approach is fine?" 3. "Should the skill handle edge cases silently or surface them to the user?" Round 3: Dependencies and Resources Before asking these questions, check which of your installed skills overlap with the workflow. If an existing skill from the science bundle covers a step, the new skill MUST reference it — do not offer a self-contained option. 1. "I noticed the workflow uses functionality covered by [existing skill X, skill Y]. The new skill will reference these rather than reimplementing them. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google-deepmind/workflow_skill_creator