L
Lucas-Belucci-Bellini/All-Skills-for-the-claude-code
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
- Star count
- 1 ★ · Lucas-Belucci-Bellini/All-Skills-for-the-claude-code · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-31 · last seen 2026-11-14 · seen 15× · listed by 2 sources
- Score
- score 200 · 1 ★ · 2 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
Lucas-Belucci-Bellini/All-Skills-for-the-claude-code;first catalogued 2026-10-31;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# All Skills for Claude Code — Community Collection
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
This is an independent, community-maintained collection of Claude Code skills and plugins. It is not affiliated with or endorsed by Anthropic. The combined collection currently packages 2512 distinct skills: 2512 original skills and zero retained/imported skills. The 161 retained/imported entries were removed and replaced with 161 newly authored language-engineering workflows covering all 31 languages in the public profile.
> Distribution note: the 161 retained/imported skill entries and their generated bundle copies have been removed. Third-party plugin packages and their non-skill components may still exist elsewhere in this repository; their LICENSE/NOTICE and provenance requirements remain applicable. This cleanup is not blanket legal approval for every plugin in the marketplace.
## Repository structure
curated-skill-sources/ — canonical source files for newly authored skills.
plugins/all-skills-collection/ — generated aggregate plugin; do not edit its skill copies by hand.
plugins/ — plugin packages in this collection, including imported and community-maintained components. Check each component's README, LICENSE, and NOTICE.
externalplugins/ — upstream plugin sources and supporting files; their own license and provenance notices remain applicable.
roadmap/skill-batches/ — planning folders for future skill batches; these folders are not counted as completed skills.
## Validate and test locally
From a clone of this repository, with a current Claude Code CLI:
bash
claude plugin validate . --strict
claude plugin validate ./plugins/all-skills-collection --strict
For a disposable local installation test, add this checkout as a marketplace and install the aggregate plugin:
text
/plugin marketplace add /absolute/path/to/All-Skills-for-the-claude-code
/plugin install all-skills-collection@all-skills-for-the-claude-code
The installation/discovery smoke test is documented in docs/research/plugin-install-smoke-test.md. Passing repository CI does not substitute for running the real Claude Code validator and installation test.
## Contributing
Add new authored skills under curated-skill-sources/; do not hand-edit the generated plugin copies.
Run node tools/sync-skill-bundles.mjs --write, inspect the diff, then run node tools/sync-skill-bundles.mjs --check.
Validate the active batch with its manifest and keep changes on a feature branch with a pull request.
For imported components, record the upstream repository/revision, preserve required LICENSE/NOTICE/attribution, and verify redistribution terms before adding or publishing them.
## Plugin Structure
Each plugin follows a standard structure:
plugin-name/
├── .claude-plugin/
│ └── plugin.json # Plugin metadata (required)
├── .mcp.json # MCP server configuration (optional)
├── commands/ # Slash commands (optional)
├── agents/ # Agent definitions (optional)
├── skills/ # Skill definitions (optional)
└── README.md # Documentation
## Plugin names are immutable
The name field in a marketplace entry is an immutable slug. Once a plugin has been published, its name must not change — users have it installed under that slug, and renaming it breaks their install with a plugin-not-found error.
> Distribution note: the 161 retained/imported skill entries and their generated bundle copies have been removed. Third-party plugin packages and their non-skill components may still exist elsewhere in this repository; their LICENSE/NOTICE and provenance requirements remain applicable. This cleanup is not blanket legal approval for every plugin in the marketplace.
## Repository structure
curated-skill-sources/ — canonical source files for newly authored skills.
plugins/all-skills-collection/ — generated aggregate plugin; do not edit its skill copies by hand.
plugins/ — plugin packages in this collection, including imported and community-maintained components. Check each component's README, LICENSE, and NOTICE.
externalplugins/ — upstream plugin sources and supporting files; their own license and provenance notices remain applicable.
roadmap/skill-batches/ — planning folders for future skill batches; these folders are not counted as completed skills.
## Validate and test locally
From a clone of this repository, with a current Claude Code CLI:
bash
claude plugin validate . --strict
claude plugin validate ./plugins/all-skills-collection --strict
For a disposable local installation test, add this checkout as a marketplace and install the aggregate plugin:
text
/plugin marketplace add /absolute/path/to/All-Skills-for-the-claude-code
/plugin install all-skills-collection@all-skills-for-the-claude-code
The installation/discovery smoke test is documented in docs/research/plugin-install-smoke-test.md. Passing repository CI does not substitute for running the real Claude Code validator and installation test.
## Contributing
Add new authored skills under curated-skill-sources/; do not hand-edit the generated plugin copies.
Run node tools/sync-skill-bundles.mjs --write, inspect the diff, then run node tools/sync-skill-bundles.mjs --check.
Validate the active batch with its manifest and keep changes on a feature branch with a pull request.
For imported components, record the upstream repository/revision, preserve required LICENSE/NOTICE/attribution, and verify redistribution terms before adding or publishing them.
## Plugin Structure
Each plugin follows a standard structure:
plugin-name/
├── .claude-plugin/
│ └── plugin.json # Plugin metadata (required)
├── .mcp.json # MCP server configuration (optional)
├── commands/ # Slash commands (optional)
├── agents/ # Agent definitions (optional)
├── skills/ # Skill definitions (optional)
└── README.md # Documentation
## Plugin names are immutable
The name field in a marketplace entry is an immutable slug. Once a plugin has been published, its name must not change — users have it installed under that slug, and renaming it breaks their install with a plugin-not-found error.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/lucas-belucci-bellini-all-skills-for-the-claude-code/)
- Source
- github · https://github.com/Lucas-Belucci-Bellini/All-Skills-for-the-claude-cod
- Browse by field
- Open source
- Traction
- 1 ★
- Listed by
- 2 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.