How do I install the Crate Claim skill?

Run npx skillmds@latest add srobinson/crate-claim in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Crate Claim safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Crate Claim?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Crate Claim free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Crate Claim?

srobinson (@srobinson) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Crate Claim by srobinson — Agent Skill

Name: Crate Claim
Author: srobinson

Crate Claim

Claim a crates.io package name by checking availability and publishing a placeholder. Use when the user says "crate claim", "cargo claim", "reserve crate name", or wants to check if a crates.io name is available. Takes a crate name as an argument. Note: crates.io publishes are permanent (yank only, no unpublish).

srobinson a4807be 4 files · 3.6 KB Updated Sep 17, 2026

File contents

crate-claim

The crate name is: $ARGUMENTS

The template directory is: $SKILL_DIR/contents/

Steps

1. Validate

If $ARGUMENTS is empty or whitespace, tell the user to provide a name and stop.

2. Check crates.io availability

Run:

curl -s -o /dev/null -w "%{http_code}" -A "helioy-crate-claim (https://github.com/littleorgans)" "https://crates.io/api/v1/crates/$ARGUMENTS"

The -A User-Agent flag is mandatory. crates.io rejects every request without a User-Agent header and returns 403, which would otherwise read as a false negative (an available name reported as taken). Keep the flag on every crates.io call.

If output is 200: the crate already exists. Fetch the owners and report before stopping:
```
curl -s -A "helioy-crate-claim (https://github.com/littleorgans)" "https://crates.io/api/v1/crates/$ARGUMENTS/owners" | python3 -c "import sys,json; d=json.load(sys.stdin); print(', '.join(u['login'] for u in d['users']))"
```
Print: $ARGUMENTS already exists on crates.io. Owner: <comma-separated logins>. If an owner matches the user (e.g. srobinson), flag it as the user's existing claim ("that's you").
If output is 404: the name is available. Continue.
If output is 403: the User-Agent header was dropped. Re-run the command with the -A flag exactly as shown, do not treat 403 as a verdict.
Any other code: report the status and stop.

3. Scaffold

Set these substitution values:

{{NAME}} = the crate name ($ARGUMENTS)
{{TITLE}} = title case version (e.g. agent-matters becomes Agent Matters)

Then run these bash commands:

mkdir -p ~/.name-claim/$ARGUMENTS/src
sed 's/{{NAME}}/$ARGUMENTS/g; s/{{TITLE}}/$ARGUMENTS_TITLE_CASE/g' $SKILL_DIR/contents/Cargo.toml > ~/.name-claim/$ARGUMENTS/Cargo.toml
sed 's/{{NAME}}/$ARGUMENTS/g' $SKILL_DIR/contents/lib.rs > ~/.name-claim/$ARGUMENTS/src/lib.rs
sed 's/{{NAME}}/$ARGUMENTS/g' $SKILL_DIR/contents/publish.sh > ~/.name-claim/$ARGUMENTS/publish.sh
chmod +x ~/.name-claim/$ARGUMENTS/publish.sh

Replace $ARGUMENTS and $ARGUMENTS_TITLE_CASE with the actual values in the sed commands.

Why ~/.name-claim/ and not /tmp/ or ~/.claude/: cargo publish walks up from Cargo.toml until it finds a .git directory; if it finds one with uncommitted changes, it refuses to publish. ~/.claude/ is a dotfiles repo so it triggers the dirty check. ~/ is not a git repo, so ~/.name-claim/ sidesteps the check entirely. The path is also shared with sister skills npm-claim, pypi-claim, and the orchestrator name-claim.

4. Print next steps

Output the following exactly as shown, substituting the actual crate name. Do NOT wrap in a code block or add any formatting.

$ARGUMENTS is available!

Warning: crates.io publishes are permanent. Yank only, no unpublish.

~/.name-claim/$ARGUMENTS/publish.sh

Note: publishing requires cargo login <token> to have been run with a token from https://crates.io/settings/tokens.

---name: crate-claimdescription: Claim a crates.io package name by checking availability and publishing a placeholder. Use when the user says "crate claim", "cargo claim", "reserve crate name", or wants to check if a crates.io name is available. Takes a crate name as an argument. Note: crates.io publishes are permanent (yank only, no unpublish).---# crate-claimThe crate name is: `$ARGUMENTS`The template directory is: `$SKILL_DIR/contents/`## Steps### 1. ValidateIf `$ARGUMENTS` is empty or whitespace, tell the user to provide a name and stop.### 2. Check crates.io availabilityRun:```bashcurl -s -o /dev/null -w "%{http_code}" -A "helioy-crate-claim (https://github.com/littleorgans)" "https://crates.io/api/v1/crates/$ARGUMENTS"```The `-A` User-Agent flag is mandatory. crates.io rejects every request without a User-Agent header and returns `403`, which would otherwise read as a false negative (an available name reported as taken). Keep the flag on every crates.io call.- If output is `200`: the crate **already exists**. Fetch the owners and report before stopping: ```bash curl -s -A "helioy-crate-claim (https://github.com/littleorgans)" "https://crates.io/api/v1/crates/$ARGUMENTS/owners" | python3 -c "import sys,json; d=json.load(sys.stdin); print(', '.join(u['login'] for u in d['users']))" ``` Print: `$ARGUMENTS already exists on crates.io. Owner: <comma-separated logins>`. If an owner matches the user (e.g. `srobinson`), flag it as the user's existing claim ("that's you").- If output is `404`: the name is **available**. Continue.- If output is `403`: the User-Agent header was dropped. Re-run the command with the `-A` flag exactly as shown, do not treat `403` as a verdict.- Any other code: report the status and stop.### 3. ScaffoldSet these substitution values:- `{{NAME}}` = the crate name (`$ARGUMENTS`)- `{{TITLE}}` = title case version (e.g. `agent-matters` becomes `Agent Matters`)Then run these bash commands:```bashmkdir -p ~/.name-claim/$ARGUMENTS/srcsed 's/{{NAME}}/$ARGUMENTS/g; s/{{TITLE}}/$ARGUMENTS_TITLE_CASE/g' $SKILL_DIR/contents/Cargo.toml > ~/.name-claim/$ARGUMENTS/Cargo.tomlsed 's/{{NAME}}/$ARGUMENTS/g' $SKILL_DIR/contents/lib.rs > ~/.name-claim/$ARGUMENTS/src/lib.rssed 's/{{NAME}}/$ARGUMENTS/g' $SKILL_DIR/contents/publish.sh > ~/.name-claim/$ARGUMENTS/publish.shchmod +x ~/.name-claim/$ARGUMENTS/publish.sh```Replace `$ARGUMENTS` and `$ARGUMENTS_TITLE_CASE` with the actual values in the sed commands.Why `~/.name-claim/` and not `/tmp/` or `~/.claude/`: `cargo publish` walks up from `Cargo.toml` until it finds a `.git` directory; if it finds one with uncommitted changes, it refuses to publish. `~/.claude/` is a dotfiles repo so it triggers the dirty check. `~/` is not a git repo, so `~/.name-claim/` sidesteps the check entirely. The path is also shared with sister skills `npm-claim`, `pypi-claim`, and the orchestrator `name-claim`.### 4. Print next stepsOutput the following exactly as shown, substituting the actual crate name. Do NOT wrap in a code block or add any formatting.$ARGUMENTS is available!Warning: crates.io publishes are permanent. Yank only, no unpublish.~/.name-claim/$ARGUMENTS/publish.shNote: publishing requires `cargo login <token>` to have been run with a token from https://crates.io/settings/tokens.

Frequently asked questions