create-command SKILL.md skillA
create-command from tailcallhq/forgecode is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tailcallhq/forgecode/create-command@git:20260126.0427bf8Pins git:20260126.0427bf8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tailcallhq/forgecode
- Path
.forge/skills/create-command/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260126.0427bf8, committed Jan 26, 2026
- Size
- 15,714 bytes
- Repository stars
- 7,634
- License
- Apache-2.0
Create new commands for the code-forge application. Commands are stored as .md files in the <cwd>/.forge/commands directory with YAML frontmatter (name, description) and markdown body containing command steps. Use when users need to add new commands, modify existing commands, or understand the command file structure. Supports special command tags like <lint> and <test> for automated workflows.
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
# Create Commands
Create and manage commands for the code-forge application. Commands are modular workflows that can be invoked to perform specific tasks.
## File Location
**CRITICAL**: All command files must be created in the `<cwd>/.forge/commands` directory, where `<cwd>` is the current working directory of your code-forge project.
- **Directory**: `<cwd>/.forge/commands`
- **File format**: `{command-name}.md`
- **Example**: If your project is at `/home/user/my-project`, commands go in `/home/user/my-project/.forge/commands/`
This is the only location where forge will discover and load custom commands.
## Command File Structure
Every command file must have:
1. **YAML Frontmatter** (required):
- `name`: Command identifier (use hyphens for multi-word names)
- `description`: What the command does
2. **Command Body** (required):
- List of steps to execute
- Special tags for automated workflows
- Clear instructions for each step
### Example Command File
```markdown
---
name: check
description: Checks if the code is ready to be committed
---
- Run the `lint` and `test` commands and verify if everything is fine.
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_oxgnqt3ge3bebm45/18e7e101b3a8ef47c1ff9a96e4b9a2db5fac7e297bd6b12c361c304a3ed32d19.json
Then /plugin install create-command@markdownregistry-oxgnqt3ge3bebm45 in Claude Code. It installs git:20260126.0427bf8, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add tailcallhq/forgecode/create-command@sha256:18e7e101b3a8ef47The line at the top of this page pins the label git:20260126.0427bf8, 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_oxgnqt3ge3bebm45)
4 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 tailcallhq/forgecode/create-command 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 create-command from somewhere else? Ask it: where did my create-command 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 Jan 26, 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/create-command/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 (15714 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
tailcallhq/forgecode · 7,634 stars · license Apache-2.0 · pushed 2026-11-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_oxgnqt3ge3bebm45 GET https://markdownregistry.com/api/v1/resolve?ref=tailcallhq/forgecode/create-command GET https://markdownregistry.com/api/v1/blob/18e7e101b3a8ef47c1ff9a96e4b9a2db5fac7e297bd6b12c361c304a3ed32d19
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 tailcallhq/forgecode
Every file in tailcallhq/forgecode