How do I install the Meta Skill Creator skill?

Run npx skillmds@latest add flashfoxer/meta-skill-creator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Meta Skill Creator safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Meta Skill Creator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Meta Skill Creator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Meta Skill Creator?

flashfoxer (@flashfoxer) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Meta Skill Creator by flashfoxer — Agent Skill

Name: Meta Skill Creator
Author: flashfoxer

Meta Skill Creator

Use this meta-skill instead of answering directly only when the current user explicitly asks to create, compose, synthesize, or propose a new meta-skill that orchestrates multiple existing skills. It uses multi-skill orchestration for intent clarification, optional history mining, trigger-collision checks, linting, smoke/runtime gates, preview, and optional proposal persistence. Do not use it for creating a normal standalone skill, asking how meta-skills work, analyzing pasted skill lists, or discussing existing meta-skills.

flashfoxer 520cd4f 2.2 KB Updated Sep 17, 2026

File contents

Meta-Skill Creator

Safeguarded DAG that synthesizes a new bundled meta-skill from observed skill co-occurrence patterns + user description of the desired workflow. It now separates preview-only, persisted-proposal, and fully gated modes so lightweight requests do not pay for persistence or smoke testing. The workflow separates generic skill creation from meta-skill composition, checks trigger collisions, classifies operational risk, and previews the proposal before optional persistence.

Output is a SKILL.md candidate written to ~/.opensquilla/proposals/<id>/. By default it is not auto-loaded; run opensquilla meta accept <id> (Phase 2) to enable. If the operator has enabled the auto-propose auto_enable setting, this manual path also runs the same conservative static safety preflight used by cron/dream auto-propose and may promote a low-risk gated proposal immediately.

Fallback

If creator's pipeline fails at any step, report the failure verbatim to the user:

State which step failed (e.g. "harvest", "lint")
Quote the error message from the orchestrator's structured log
Stop. Do NOT improvise.

Do NOT:

Claim a proposal was written unless you have verified it by reading ~/.opensquilla/proposals/<id>/SKILL.md with the read_file tool
Invent file paths, proposal IDs, or skill names that you have not seen in the orchestrator's actual output
"Manually run" the individual skills as a recovery — that bypasses the validation gates the user explicitly opted into

If the user wants to retry, suggest they re-issue the request after the underlying error is resolved (often a sandbox or provider issue), not a manual workaround.

---name: meta-skill-creatordescription: Use this meta-skill instead of answering directly only when the current user explicitly asks to create, compose, synthesize, or propose a new meta-skill that orchestrates multiple existing skills. It uses multi-skill orchestration for intent clarification, optional history mining, trigger-collision checks, linting, smoke/runtime gates, preview, and optional proposal persistence. Do not use it for creating a normal standalone skill, asking how meta-skills work, analyzing pasted skill lists, or discussing existing meta-skills.---# Meta-Skill CreatorSafeguarded DAG that synthesizes a new bundled meta-skill from observed skillco-occurrence patterns + user description of the desired workflow. It nowseparates preview-only, persisted-proposal, and fully gated modes so lightweightrequests do not pay for persistence or smoke testing. The workflow separatesgeneric skill creation from meta-skill composition, checks trigger collisions,classifies operational risk, and previews the proposal before optionalpersistence.Output is a SKILL.md candidate written to `~/.opensquilla/proposals/<id>/`.By default it is not auto-loaded; run `opensquilla meta accept <id>` (Phase 2)to enable. If the operator has enabled the auto-propose `auto_enable` setting,this manual path also runs the same conservative static safety preflight used bycron/dream auto-propose and may promote a low-risk gated proposal immediately.## FallbackIf creator's pipeline fails at any step, **report the failure verbatim** to theuser:1. State which step failed (e.g. "harvest", "lint")2. Quote the error message from the orchestrator's structured log3. Stop. Do NOT improvise.Do NOT:- Claim a proposal was written unless you have verified it by reading `~/.opensquilla/proposals/<id>/SKILL.md` with the `read_file` tool- Invent file paths, proposal IDs, or skill names that you have not seen in the orchestrator's actual output- "Manually run" the individual skills as a recovery — that bypasses the validation gates the user explicitly opted intoIf the user wants to retry, suggest they re-issue the request after theunderlying error is resolved (often a sandbox or provider issue), not amanual workaround.

Frequently asked questions