
Skill Creator
Create or improve OpenChatCut custom skills.
Install
npx skills add 0xsline/OpenChatCut --skill skill-creator -g -a claude-code -y- Repository
- 0xsline/OpenChatCut2.8k
- Category
- Writing
- Updated
- 14d ago
- License
- AGPL-3.0
- Context cost
- Lightabout 1,034 tokens
- Runs scripts
- No, instructions only
What it does
Create or improve OpenChatCut custom skills. Use whenever the user asks to create a skill, capture a workflow as a skill, write a SKILL.md, add a reusable workflow, 创建技能, 把流程做成技能, 写一个技能, or improve an existing custom skill. Pushy: treat any workflow the user repeats as a skill candidate, even if they do not say "skill".
Skill Creator
Create or improve custom skills for OpenChatCut. A skill is a SKILL.md file
(plus optional references/ support docs) that teaches the agent a reusable
workflow. Custom skills live at ~/.openchatcut/skills/<slug>/SKILL.md and
are managed with the manage_skill tool.
Workflow
- Capture intent. If the current conversation already contains the workflow (tools used, steps, corrections), extract it from the history first. Confirm with the user before writing.
- Interview. Pin down:
- What should this skill enable the agent to do?
- When should it trigger? Which user phrases or contexts?
- Expected output format?
- Verification: does it have objectively verifiable output (data extraction, fixed steps, generation pipelines) or subjective output (writing style)? Suggest test prompts for the former.
- Write the SKILL.md (rules below).
- Create it with
manage_skill action=create. The tool reports the install path (~/.openchatcut/skills/<slug>/SKILL.md). - Test. Run 2, 3 realistic prompts in the current session and confirm
results with the user. Iterate with
manage_skill action=update.
SKILL.md anatomy
<slug>/
├── SKILL.md (required, frontmatter + instructions)
└── references/ (optional, docs loaded on demand with load_skill file=)
- name: kebab-case slug matching the directory (lowercase letters, digits, hyphens only). It becomes the load_skill name.
- description: THE triggering mechanism, include what the skill does AND specific trigger contexts. Skills undertrigger easily, so be explicit: list concrete user phrases. "When to use" goes here, not in the body.
- body: imperative instructions. Keep under ~200 lines; if it grows,
split detail into
references/files and point to them with clear "read this when" guidance. For references over 300 lines, add a TOC.
