create-moviepilot-skill
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
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 11 784
- Лиценз
- Не е посочен. Проверете в репозитория.
- Последна проверка на записа
- Няма посочена дата
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add jxxghp/MoviePilotСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
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.
Step 3: Choose the Skill ID and Path
- New built-in skill path:
skills/<skill-id>/SKILL.md - Keep
<skill-id>short, hyphen-case, and under 64 characters. - Use a verb-led or domain-led name that makes the trigger obvious, such as
transfer-failed-retry,moviepilot-api, orcreate-moviepilot-skill.
Step 4: Write Frontmatter Correctly
Use this shape:
---
name: create-moviepilot-skill
version: 1
description: >-
Explain what the skill does and exactly when to use it.
allowed-tools: list_directory read_file write_file edit_file execute_command
---
Rules: