skill-creator SKILL.md skillA
skill-creator from cgoinglove/thursday is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cgoinglove/thursday/skill-creator@git:20260927.d196644Pins git:20260927.d196644 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cgoinglove/thursday
- Path
skills/skill-creator/SKILL.md- Versions recorded
- 6
- Latest version
- git:20260927.d196644, committed Sep 27, 2026
- First version recorded
- Sep 22, 2026
- Size
- 21,471 bytes
- Repository stars
- 58
- License
- MIT
Creates new skills and improves existing ones. Use it when the user wants a repeatable way of working written down, or a skill fixed or made to trigger better, even without the word 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 A skill for creating new skills and iteratively improving them. At a high level, the process of creating a skill goes like this: - Decide what you want the skill to do and roughly how it should do it - Write a draft of the skill - Create a few test prompts and run them yourself with the skill loaded - Show the user the results and ask what they would change - Rewrite the skill based on the user's feedback - Repeat until you're satisfied - Expand the test set and try again at larger scale Your job when using this skill is to figure out where the user is in this process and then jump in and help them progress through these stages. So for instance, maybe they're like "I want to make a skill for X". You can help narrow down what they mean, write a draft, write the test cases, run all the prompts, and repeat. On the other hand, maybe they already have a draft of the skill. In this case you can go straight to the test/iterate part of the loop. Of course, you should always be flexible and if the user is like "I don't need to run a bunch of evaluations, just vibe with me", you can do that instead. Cool? Cool. ## In this app …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5zptbe6lgeactvl4/777b5d7f961a9415d2db6edc4ec1e6e1b53251c356af3c69d8ac99d708217ea4.json
Then /plugin install skill-creator@markdownregistry-5zptbe6lgeactvl4 in Claude Code. It installs git:20260927.d196644, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add cgoinglove/thursday/skill-creator@sha256:777b5d7f961a9415The line at the top of this page pins the label git:20260927.d196644, 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_5zptbe6lgeactvl4)
2 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 cgoinglove/thursday/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 6 versions of this file, between Sep 22, 2026 and Sep 27, 2026, about one every day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260927.d196644 latest | 2026-09-27 | d196644 | 21,471 B | A | view · diff |
| git:20260925.9eaf266 | 2026-09-25 | 9eaf266 | 21,456 B | A | view · diff |
| git:20260924.07ce2aa | 2026-09-24 | 07ce2aa | 21,153 B | A | view · diff |
| git:20260924.68e4815 | 2026-09-24 | 68e4815 | 21,105 B | A | view · diff |
| git:20260923.b0f5b18 | 2026-09-23 | b0f5b18 | 21,187 B | A | view · diff |
| git:20260922.d760929 | 2026-09-22 | d760929 | 6,764 B | A | view |
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 (21471 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
cgoinglove/thursday · 58 stars · license MIT · pushed 2026-11-10 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5zptbe6lgeactvl4 GET https://markdownregistry.com/api/v1/resolve?ref=cgoinglove/thursday/skill-creator GET https://markdownregistry.com/api/v1/blob/777b5d7f961a9415d2db6edc4ec1e6e1b53251c356af3c69d8ac99d708217ea4
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 cgoinglove/thursday
Every file in cgoinglove/thursday