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).
Security Assessment
About workflow-skill-creator
Workflow Skill Creator is a meta-skill from Google DeepMind's science-skills bundle that distills a workflow or interaction that already happened into a reusable agent skill. It is specifically for packaging patterns from a completed multi-step process — not for building skills from scratch, which the description defers to a generic skill-creator. It solves the problem of capturing ad-hoc, one-off workflows before the reasoning behind them is lost, turning them into structured, repeatable skills.
The skill enforces a disciplined multi-phase process. Phase 1 is a mandatory iterative brainstorming conversation with question banks covering workflow understanding, flexibility and error handling, dependencies and resources, scope and shape, and optional testing — the guidance is emphatic that this must complete before any code or SKILL.md is written. Phase 2 produces a design document (skill name and description within frontmatter length rules, directory structure and install location, referenced existing skills, new scripts, rate-limiting strategy, and per-step error handling) for explicit user approval. Phase 3 implements, with guiding principles such as using `uv run` rather than `python`, preferring stdlib libraries like `urllib`, documenting and respecting API rate limits (favoring file-lock–based limiting so concurrent sub-agents share the limit), and referencing existing bundle skills rather than reimplementing them.
The target users are scientists and researchers working within DeepMind's Science Skills environment who want to convert an interaction into a durable skill. Use cases include packaging a data-fetching-and-analysis workflow, capturing a domain protocol, and standardizing a recurring research process into a shareable skill with a CLI helper script when programmatic work is involved.
FAQ
When should I use this skill instead of a generic skill creator?
Use it when you want to turn a workflow or interaction that already happened into a skill. For creating a skill from scratch with no existing workflow, the description directs you to a generic skill-creator instead.
Why is the brainstorming phase mandatory?
The skill marks Phase 1 brainstorming as required because skipping it produces skills that are either too rigid or too vague. It is an iterative back-and-forth (2-3 questions per round), not a single questionnaire.
What are the implementation conventions?
Use uv run rather than python or python3, prefer standard-library packages such as urllib to avoid extra installs, and document and respect any API rate limits in code — ideally with file-lock-based rate limiting so concurrent sub-agents share the limit.
How does it handle overlap with existing skills?
If an existing skill in the science bundle covers a workflow step, the new skill must reference it rather than reimplementing the functionality, and the skill checks installed skills for overlap during the dependencies round.
Do I get to approve the design before code is written?
Yes. Phase 2 produces a design document covering the name, directory structure and install location, referenced skills, scripts, rate limiting, and error handling, and the skill waits for explicit user approval before implementing.
Install workflow-skill-creator
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
google-deepmind/science-skills