skills/meta-skill/SKILL.md
Decompose a skill into child skills and convert it into a meta-skill orchestrator. Use when the user says "meta-skill X", "decompose skill X", or "break skill X into sub-skills". Takes an existing skill with multiple sequential tasks and splits each task into its own standalone skill, then rewrites the original as a meta-skill that triggers child skills in order via the Skill tool.
npx skillsauth add razbakov/skills skills/meta-skillInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are converting skill {argument} into a meta-skill with child skills.
~/.cursor/skills/{argument}/SKILL.md
If not found, check project-local .claude/skills/{argument}/SKILL.md.
Parse the SKILL.md fully: frontmatter, description, all steps/tasks/phases.
Extract every distinct task, phase, or step from the skill. A task is discrete if:
List the tasks in execution order. Confirm with the user before proceeding:
I found N tasks in skill "{argument}":
1. task-name-a — one-line summary
2. task-name-b — one-line summary
3. task-name-c — one-line summary
Should I create a child skill for each and convert "{argument}" into a meta-skill?
For each task, create a standalone skill at:
~/.cursor/skills/{argument}-{task-name}/SKILL.md
Each child skill MUST:
description and user_invocable: trueReplace the original {argument}/SKILL.md with a meta-skill that:
description (updated to mention orchestration)Skill tool to invoke each child skill sequentiallyUse this template for the rewritten meta-skill:
---
description: (original description, updated to mention it orchestrates child skills)
user_invocable: true
argument: (same as original if applicable)
---
# {Skill Name} (Meta-Skill)
This is a meta-skill that orchestrates the following child skills in order:
1. **{argument}-{task-1}** — summary
2. **{argument}-{task-2}** — summary
3. **{argument}-{task-3}** — summary
## Execution
Run each child skill sequentially using the Skill tool:
### Step 1: {task-1}
Invoke: `//{argument}-{task-1}`
Captures: (what this step produces for the next)
### Step 2: {task-2}
Invoke: `//{argument}-{task-2}`
Depends on: (what it needs from step 1)
Captures: (what this step produces)
### Step 3: {task-3}
Invoke: `//{argument}-{task-3}`
Depends on: (what it needs from previous steps)
## Notes
- Each child skill can also be run independently via `/{argument}-{task-name}`
- If a step fails, fix the issue and re-run that specific child skill
Decomposed "{argument}" into N child skills:
- /{argument}-{task-1} — summary
- /{argument}-{task-2} — summary
- /{argument}-{task-3} — summary
Meta-skill "/{argument}" now orchestrates all children in order.
Each child skill can also be invoked independently.
development
Seed a new or empty Instagram account with a 9-post grid (3×3) so the profile looks established the moment a new visitor lands. Designed for festivals, new businesses, product launches, conferences, communities — any time an empty IG profile would hurt conversion from external traffic (QR scans, flyer drops, cross-promo). Generates assets via /image-from-gemini (per content-publishing rules — never HTML), writes captions with hashtag sets, and outputs a posting order + cadence plan. Trigger generously: phrases like '9 posts for instagram', 'fill my IG', 'starter grid', 'launch grid', 'instagram seed', '9-post grid', 'IG account not to look empty', 'first instagram posts', 'feed bootstrap', '3x3 grid', 'instagram launch content'. Even if the user mentions only one piece (just the images, just the captions, just the order), use this skill — the grid only works as an integrated bundle.
testing
Translate one English blog post into multiple target languages via parallel sub-agents, preserving frontmatter conventions, hero image, and brand voice. Use when the user shares a published English post URL or markdown path and says 'translate it', 'add other languages', 'publish in DE/ES/RU/UK', 'translate to 5 languages', or asks for localized versions of a specific post.
development
Build a complete press kit for an event, product launch, or campaign — in multiple languages — and publish it as a shareable Google Drive folder ready to send to journalists, partners, or a delegate. Produces press releases (typically DE/EN/ES, or configurable), uploads press photos and flyers, creates an Overview document for at-a-glance briefing, and creates a Handover document with pending tasks, contacts, risks, and decisions so press distribution can be delegated. Use when the user says 'I need a press release', 'create a press kit', 'press release in X languages', 'set up a Drive folder for press', 'handover doc for someone else to run press', or has an upcoming announcement that needs to be sent to media. Trigger generously: even partial requests (just a press release, just a flyer folder) typically evolve into the full kit.
development
Track ticket sales for a live event (concert, festival, conference, workshop) with daily snapshots, generate a burndown chart comparing actual sales to ideal-linear targets and tier-cumulative milestones, and report whether the event is on pace. Use when the user asks how sales are going, wants to know if their event will sell out, asks for a daily sales report, wants to set up sales tracking for an upcoming event, or asks about ticket pace / velocity / projection. Trigger generously: phrases like 'how is concert sales going', 'burndown for my event', 'are we going to sell out', 'sales velocity', 'daily ticket chart', 'how many tickets do we need to sell', or any case where the user has a ticketed event with a fixed sales window and wants visibility on pacing.