Repository navigation
Claude Code and Codex plugin marketplace for the agent skills in skills/dev-skills #71912
Description
Which @angular/* package(s) are relevant/related to the feature request?
None of them; this is about the agent skills in skills/dev-skills, which are published to https://github.com/angular/skills. That repo's README sends feedback to this tracker.
Description
Angular already ships agent skills in skills/dev-skills (published to angular/skills): angular-developer, angular-new-app.
What I couldn't find is a one-command install for Claude Code or Codex. Both can install a plugin from a git repository that carries a small marketplace file, and the file can point at skills a repo already has, so nothing needs copying or maintaining twice.
Proposal: add .claude-plugin/marketplace.json at the repo root, along these lines:
{
"name": "angular",
"owner": {
"name": "Angular"
},
"description": "Angular agent skills",
"plugins": [
{
"name": "angular",
"source": "./skills/dev-skills",
"strict": false,
"skills": [
"./angular-developer",
"./angular-new-app"
],
"description": "Angular agent skills for Claude Code"
}
]
}Then claude plugin marketplace add <owner>/<repo> followed by claude plugin install angular@angular installs the skills. Codex has its own marketplace file (.agents/plugins/marketplace.json, documented at https://developers.openai.com/codex/plugins/build) and could be added the same way if you want it.
What I checked: I validated and installed exactly this manifest in Claude Code against a stand-in folder with the same layout and placeholder SKILL.md files named like yours; claude plugin details listed all 2 skills. Separately I installed Chakra UI's real skills/ through a different marketplace with a git-subdir source, and its three skills appeared with no change to Chakra's repo. I only read each skill's front matter and README to judge that they are meant for end users.
If you'd rather not carry a marketplace file, tell me and I won't pursue it. I'm not offering a PR unless you ask for one.
Drafted with Claude Code.
Proposed solution
A .claude-plugin/marketplace.json as above, in whichever location flows to angular/skills through your publishing setup. I don't know how that output is generated, so I haven't guessed at the path.
Alternatives considered
Keeping npx skills add https://github.com/angular/skills as the only install route, which works for tools that read that format but is not a one-command install inside Claude Code or Codex.
Activity
GamerDubz commentedon Nov 10, 2026
Closing in favour of the PR that adds the file: #71913
GamerDubz commentedon Nov 10, 2026
Reopening: I closed this too early in favour of a PR, and the PR is now closed. The proposal and a ready branch (https://github.com/GamerDubz/angular/tree/feat/claude-plugin-marketplace) are here if you want it; I'll wait for your view before sending a PR.
Flarette commentedon Nov 10, 2026
I'm not even sure that skills are worth supporting in the long run. They were all the rage half a year ago but now it's all in model weights already. They need to be re-measured, optimized and deleted regularly or they just become the context bloat. In fact some people say to avoid angular skills and use MCP only.
GamerDubz commentedon Nov 10, 2026
Thanks for the perspective, @Flarette. That's a fair concern about skills, but I think it's a separate question from what this proposal changes.
This doesn't add or change any skills. The skills in
skills/dev-skillsalready exist and are already published. The proposal only adds two small manifest files so people who want those skills can install them through the Claude Code and Codex plugin marketplaces, instead of copying files by hand.So I'd frame it as: if the team keeps shipping these skills, is making them installable in one step reasonable? Happy to adjust the scope if the maintainers see it differently.