create-skill
npx machina-cli add skill MSiccDev/ai-context-kit/create-skill --openclawCreate Skill
Purpose
Generate complete SKILL.md artifacts for one skill folder, with explicit constraints and reusable references.
When To Use
- Use this skill when creating a new skill folder under
skills/. - Use this skill when regenerating a
SKILL.mdfile to align with repository skill standards. - Do not use this skill for validating an existing skill.
Required Inputs
- Skill slug (
name) and target folder path. - Capability summary and usage triggers.
- Required inputs, workflow outputs, and failure boundaries.
- Safety and portability constraints.
Workflow
- Run discovery sequence in
references/discovery-phases.md. - Apply schema and field rules from
references/field-constraints.md. - Assemble required body sections using
references/output-schema.md. - Apply safety constraints from
references/safety.md. - Produce final artifact using
references/output-format.md. - Validate against
references/quality-checklist.mdbefore final output.
Output Expectations
- One complete
SKILL.mdartifact atskills/{name}/SKILL.md. - Frontmatter and folder-name parity are correct.
- Body sections are complete, actionable, and concise.
- Output remains provider-neutral and portable.
Resources
- Discovery workflow:
references/discovery-phases.md - Field constraints:
references/field-constraints.md - Output schema:
references/output-schema.md - Safety policy:
references/safety.md - Output contract:
references/output-format.md - Quality checklist:
references/quality-checklist.md - Skill template:
../../templates/skill_template/SKILL.md
Constraints And Safety
- Keep skill instructions concise and execution-oriented.
- Avoid provider-specific lock-in wording.
- Use relative paths for local references.
- Treat
allowed-toolsas optional/experimental unless explicitly required.
Source
git clone https://github.com/MSiccDev/ai-context-kit/blob/development/skills/create-skill/SKILL.mdView on GitHub Overview
Create Skill generates complete `SKILL.md` artifacts for one skill folder, with explicit constraints and reusable references. It enforces frontmatter parity, deterministic schema, and safety/quality checks to maintain repository standards. This helps ensure skill docs are actionable, portable, and ready for review.
How This Skill Works
Follow a six step workflow: discovery in references/discovery-phases.md, apply schema and field rules from references/field-constraints.md, assemble required body sections using references/output-schema.md, apply safety constraints from references/safety.md, produce the final artifact using references/output-format.md, and validate against the references/quality-checklist.md before final output.
When to Use It
- Create a new skill folder under skills/
- Regenerate a SKILL.md to align with repository skill standards
- Do not use this skill for validating an existing skill
- Update a skill's inputs, outputs, or safety constraints and regenerate
- Perform a full refresh after workflow or reference changes
Quick Start
- Step 1: Run discovery sequence in references/discovery-phases.md
- Step 2: Apply schema and field rules from references/field-constraints.md
- Step 3: Assemble required body sections using references/output-schema.md and apply safety/format checks using references/safety.md and references/output-format.md, then run the quality checklist
Best Practices
- Confirm the skill slug and target folder path before generation
- Reference discovery-phases, field-constraints, output-schema, safety, output-format, and quality-checklist exactly as in the SKILL.md guidelines
- Ensure frontmatter parity and folder-name parity
- Use the official skill template at ../../templates/skill_template/SKILL.md
- Validate the final artifact against the quality checklist and portability rules
Example Use Cases
- Create a new skill folder for parse-log-entries and generate its SKILL.md
- Regenerate SKILL.md after updating constraints or references to align with repo standards
- Update safety constraints for a skill that handles sensitive inputs and re-generate
- Refactor language to ensure provider-neutral terminology across SKILL.md
- Refresh a skill after a major dependency or workflow update