meta-skill-creator
The meta-skill-creator orchestrates multiple existing skills to synthesize new bundled meta-skills that coordinate complex workflows. Use it only when a user explicitly requests creation of a meta-skill (not a standalone skill), providing intent clarification, trigger-collision detection, linting, safety gates, and optional persistence to proposals that can be reviewed before acceptance.
git clone --depth 1 https://github.com/opensquilla/opensquilla /tmp/meta-skill-creator && cp -r /tmp/meta-skill-creator/src/opensquilla/skills/bundled/meta-skill-creator ~/.claude/skills/meta-skill-creatorSKILL.md
# 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: 1. State which step failed (e.g. "harvest", "lint") 2. Quote the error message from the orchestrator's structured log 3. 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.
Submit audio or video for multilingual dubbing, poll status, and download dubbed audio. Use when the user asks for dubbing, 多语言配音, 视频翻译配音, 译制片, or wants a source clip dubbed into another language.
Generate a structured short-video shooting script from a topic. Emits a strict, machine-parseable shot list (3 shots by default) with image prompt + video prompt + voiceover + on-screen text per shot. Trigger when the user asks for a video script, 分镜, 短视频文案, AI视频, 短剧脚本, or wants visual prompts ready for image/video generation.
Use when the user asks to schedule recurring tasks, one-off reminders, timers, or cron-style jobs through the OpenSquilla cron tool.
Multi-round research with explicit methodology, evidence tracking, and citation-tagged synthesis. Trigger on 'deep dive', 'research report', 'literature review', 'investigate X across sources', 'multi-round investigation'. Distinct from the `summarize` skill, which is a single-pass condensation; this skill maintains a state file across iterations, tracks coverage, and produces a long-form report with per-claim citations. Three execution stages: plan (scope into sub-questions), iterate (record evidence per round), compile (synthesize report). The skill itself does not fetch the web — it tells the host agent which fetches to perform via OpenSquilla's existing web tools, and records what comes back.
Read, edit, or create Microsoft Word `.docx` files. Trigger this skill whenever the user mentions a Word document, .docx file, contract, report, brief, memo, or asks to extract text, modify an existing doc, generate one from a brief, or audit tracked changes. Three execution paths: text-and-structure extraction, in-place edit-by-run (preserves styles), and create-from-scratch with python-docx. Falls back to OOXML unzip-and-patch for layout work python-docx cannot reach.
Capture the current git diff (staged, working-tree, or staged file list) as text. Direct shell call for workflows that need repository diffs without an LLM agent loop.
GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.
Query the per-turn DecisionEntry log for skill co-occurrence patterns, meta-skill usage stats, and the router fixture corpus. Returns a JSON summary suitable for downstream LLM consumption. Used by meta-skill-creator's harvest step but also useful standalone for 'which skills did I use most this week?'