skill-creator SKILL.md skillA
skill-creator from 0xsline/openchatcut is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add 0xsline/openchatcut/skill-creator@git:20260805.ff44b0aPins git:20260805.ff44b0a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- 0xsline/openchatcut
- Path
src/agent/skills/skill-creator/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260805.ff44b0a, committed Aug 5, 2026
- Size
- 4,563 bytes
- Repository stars
- 3,198
- License
- AGPL-3.0
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".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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
1. **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.
2. **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.
3. **Write the SKILL.md** (rules below).
4. **Create it** with `manage_skill action=create`. The tool reports the
install path (`~/.openchatcut/skills/<slug>/SKILL.md`).
5. **Test.** Run 2–3 realistic prompts in the current session and confirm
results with the user. Iterate with `manage_skill action=update`.
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_isy3k2prdcbbjxg4/ff3fbb4bc58d25b9175a51a084c377b7ad171f4f86992cb6fe22ef44d2923179.json
Then /plugin install skill-creator@markdownregistry-isy3k2prdcbbjxg4 in Claude Code. It installs git:20260805.ff44b0a, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add 0xsline/openchatcut/skill-creator@sha256:ff3fbb4bc58d25b9The line at the top of this page pins the label git:20260805.ff44b0a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_isy3k2prdcbbjxg4)
7 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in 0xsline/openchatcut/skill-creator since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of skill-creator from somewhere else? Ask it: where did my skill-creator come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Aug 5, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/skill-creator/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4563 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
0xsline/openchatcut · 3,198 stars · license AGPL-3.0 · pushed 2026-11-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_isy3k2prdcbbjxg4 GET https://markdownregistry.com/api/v1/resolve?ref=0xsline/openchatcut/skill-creator GET https://markdownregistry.com/api/v1/blob/ff3fbb4bc58d25b9175a51a084c377b7ad171f4f86992cb6fe22ef44d2923179
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from 0xsline/openchatcut
Every file in 0xsline/openchatcut