Name the pack Cargo Skills in the README title - #89
Merged
Merged
Conversation
We were shipping three names: "Cargo" in every plugin manifest and marketplace.json, "Cargo Skills" in the CLI's npm README, and "Cargo Agent Skills" here. Three names build recall for none. Settling on two, deliberately: "Cargo" in-product, where the install is `cargo@cargo` and context disambiguates, and "Cargo Skills" everywhere external. The external name matches the repo slug that renders beside it in every listing, and it avoids the collision a bare "Cargo" has with Rust's package manager -- searching a 2,281-plugin registry for "cargo" returns only Rust tooling. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We ship three names today:
displayName,marketplace.json, the Gemini manifestThree names build recall for none. This settles on two, deliberately:
displayName,/plugin install cargo@cargo. Already consistent, and context disambiguates there.Why not the short name externally: in a developer-tool catalog, "Cargo" is Rust's package manager. Searching the 2,281-plugin Anthropic community registry for "cargo" returns only Rust tooling —
cargo-deny,Cargo.tomlparsing, "npm, pip, Cargo, NuGet", even one plugin warning against "cargo-culting". None of them us. "Cargo Skills" also matches the repo slug that renders right beside the name in every listing.Why not "Agent Skills": it's the proper noun of the open standard and carries some category weight, but matching our own URL wins, and it reads redundant inside a directory category already called Skills.
Already applied to the pending awesome-ai-plugins entry (hashgraph-online/awesome-ai-plugins#72) before review.
One line. Lint clean.
🤖 Generated with Claude Code
Note
Low Risk
Documentation-only heading change with no impact on code, installs, or runtime behavior.
Overview
Renames the README H1 from Cargo Agent Skills to Cargo Skills so external-facing branding matches the repo slug and listings, while in-product naming stays Cargo.
No functional, install, or skill content changes—title line only.
Reviewed by Cursor Bugbot for commit 76aef2e. Bugbot is set up for automated code reviews on this repo. Configure here.