| name | seed-to-skill-converter |
| description | Elevate a frequently-used Dojo Seed into a fully-fledged reusable Skill with templates and workflows. Use when a seed has proven value and describes a repeatable process. Trigger phrases: "promote this seed to a skill", "convert this seed into a skill", "make this seed into a skill", "formalize this pattern", "turn this seed active". |
OpenClaw Integration: This skill is invoked by the Dojo Genesis plugin via /dojo run seed-to-skill-converter.
The agent receives project context automatically via the before_agent_start hook.
Use dojo_get_context for full state, dojo_save_artifact to persist outputs,
and dojo_update_state to record phase transitions and decisions.
Seed-to-Skill Converter Skill
Version: 1.0
Created: 2026-02-04
Author: Manus AI
Purpose: To provide a structured process for identifying when a Dojo Seed has become important enough to be promoted into a reusable Skill, and to guide the conversion process.
I. The Philosophy: From Insight to Instrument
A Dojo Seed is a potent insight, a moment of clarity captured. It is a reminder of a lesson learned. A Skill is an instrument. It is that same lesson transformed into a repeatable, structured process that can be reliably executed by any agent.
The Seed-to-Skill Converter is the alchemical process that turns the passive wisdom of a Seed into the active utility of a Skill. It is the recognition that some insights are so fundamental to our practice that they deserve to be formalized, to become part of the very machinery of our workflow.
II. When to Use This Skill
- When a Seed is referenced frequently: If you find yourself constantly referring back to the same Seed across multiple projects or sprints, it may be ready for promotion.
- When a Seed describes a multi-step process: If a Seed isn't just a simple reminder but outlines a series of actions, it is a strong candidate for a Skill.
- When a Seed represents a core part of our workflow: If a Seed is fundamental to how we build, reflect, or collaborate, it should be a Skill.
- During a Retrospective: A retrospective is a perfect time to ask, "Which of our learnings from this sprint are so important they should become a permanent Skill?"
III. The Conversion Workflow
Step 1: Identify the Candidate Seed
Select a Dojo Seed that meets the criteria from Section II. Announce the intention to convert it into a Skill.
Example: "The Seed 'Workflow as Practice' has become so central to our collaboration that I believe it's time to elevate it into a formal Skill."
Step 2: Deconstruct the Seed's Wisdom
Analyze the Seed and break down its core components:
- The Core Insight: What is the fundamental truth or idea the Seed represents?
- The Trigger: When should this wisdom be applied?
- The Process: What are the concrete steps an agent should take to apply this wisdom?
- The Desired Outcome: What is the result of applying this wisdom correctly?
Step 3: Draft the Skill Using the Standard Template
Create a new directory in SKILLS/ and a SKILL.md file. Use the standard Skill template (see skill-creation skill) to structure the new Skill. The components deconstructed in Step 2 will form the core of the new Skill's content.
| Seed Component | Skill Section |
|---|
| Core Insight | I. The Philosophy |
| Trigger | II. When to Use This Skill |
| Process | III. The Workflow |
| Desired Outcome | IV. Best Practices / V. Quality Checklist |
Step 4: Define the Workflow and Templates
This is the most critical step. Transform the abstract process from the Seed into a concrete, step-by-step workflow. If the Skill involves creating a document, provide a complete markdown template.
Step 5: Commit the New Skill
Commit the new Skill to the AROMA repository and copy it to the local /home/ubuntu/skills/ directory to make it available for immediate use.
IV. Example Conversion: 'Workflow as Practice' Seed
Let's imagine we are converting the Seed: Seed: Workflow as Practice — Why it matters: It reframes our collaboration from a means to an end to a valuable practice in itself. — Revisit trigger: When we feel rushed, frustrated, or focused only on the outcome.
Deconstruction:
- Core Insight: Our collaboration is a practice, not just a series of tasks.
- Trigger: Feeling rushed, frustrated, or overly outcome-focused.
- Process: Pause, re-read the project's
PHILOSOPHY.md or STATUS.md, reflect on the how not just the what, and consciously choose to slow down to the "pace of understanding."
- Desired Outcome: A return to a more mindful, less reactive state of work.
Skill Creation:
This would likely become a Skill called mindful-workflow-check. The workflow would guide an agent to:
- Recognize the trigger (frustration, rushing).
- Pause current work.
- Read the project's
STATUS.md and PHILOSOPHY.md.
- Write a brief, private reflection in
thinking/ on how the current work aligns with the project's deeper purpose.
- State a clear intention for how to proceed with the work in a more mindful way.
V. Best Practices
- Not Every Seed Needs to Be a Skill: The beauty of Seeds is their lightness. Only promote a Seed when it has proven its value and utility over time.
- Skills Should Be Actionable: A Skill must describe a process. If a Seed is purely a philosophical reminder, it should remain a Seed.
- Skills Require Maintenance: Once a Seed becomes a Skill, it is part of our formal infrastructure and must be kept up-to-date.
- The Goal is Utility: The purpose of this conversion is to create a useful instrument. If the resulting Skill is not useful, the conversion has failed.
OpenClaw Tool Integration
When running inside the Dojo Genesis plugin:
- Start by calling
dojo_get_context to retrieve full project state, history, and artifacts
- During the skill, follow the workflow steps documented above
- Save outputs using
dojo_save_artifact with the artifacts output directory
- Update project state by calling
dojo_update_state to record skill completion and any phase transitions
