Create Moviepilot Skill
Use this skill when the user asks to create, scaffold, update, or review a MoviePilot...
Install
npx skills add jxxghp/MoviePilot --skill create-moviepilot-skill -g -a claude-code -y- Repository
- jxxghp/MoviePilot12k
- Category
- AI and agents
- Updated
- 3d ago
- License
- GPL-3.0
- Context cost
- Lightabout 1,253 tokens
- Runs scripts
- No, instructions only
What it does
Use this skill when the user asks to create, scaffold, update, or review a MoviePilot agent skill. This includes adding a new built-in skill under the repository `skills/` directory, editing an existing built-in skill, writing `SKILL.md` frontmatter and workflow instructions, choosing `allowed-tools`, adding helper scripts when needed, and bumping the built-in skill `version` so changes can sync into `config/agent/skills`.
Create MoviePilot Skill
This skill guides you through creating or updating a built-in MoviePilot agent skill in this repository.
Scope
Use this workflow for repository built-in skills:
- Create or update files under
skills/<skill-id>/ - Commit the skill as part of the MoviePilot repository
- Do not place the implementation only in
config/agent/skillsunless the user explicitly asks for a local override instead of a built-in skill
MoviePilot-Specific Rules
- The repository root
skills/directory is the bundled source of truth for built-in skills. - On agent startup, bundled skills are synced into
config/agent/skills. - Sync overwrite depends on the
versionfield inSKILL.md. If you update an existing built-in skill, incrementversion, or users may continue using an older copied version. - Keep the folder name and frontmatter
nameidentical. Use lowercase letters, digits, and hyphens only. - Prefer extending an existing skill instead of creating an overlapping duplicate.
Workflow
Step 1: Understand the Request
- Determine whether the user wants a new skill or a change to an existing one.
- Extract the target task, likely trigger phrases, needed tools, and whether helper scripts are necessary.
- If the goal is still ambiguous after reading the request and local context, ask one focused clarification question. Otherwise proceed with a reasonable default.
Step 2: Check Existing Skills First
- Inspect the repository
skills/directory before creating anything new. - If an existing skill already covers most of the workflow, update it instead of adding a near-duplicate.
- Reuse the repository style: concise YAML frontmatter, trigger-rich description, and procedural body sections.

