A skill your agent uses when writing, testing, or preparing ANY contribution or pull request to the JSONbored/awesome-claude (HeyClaude) repo — adding a community content entry (agent/MCP…
Install the "contributing-to-awesome-claude" agent skill from https://github.com/JSONbored/awesome-claude/tree/main/.claude/skills/contributing-to-awesome-claude into .claude/skills/contributing-to-awesome-claude/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contributing-to-awesome-claude", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add JSONbored/awesome-claude --skill contributing-to-awesome-claude -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "contributing-to-awesome-claude" agent skill from https://github.com/JSONbored/awesome-claude/tree/main/.claude/skills/contributing-to-awesome-claude into .agents/skills/contributing-to-awesome-claude/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contributing-to-awesome-claude", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add JSONbored/awesome-claude --skill contributing-to-awesome-claude -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "contributing-to-awesome-claude" agent skill from https://github.com/JSONbored/awesome-claude/tree/main/.claude/skills/contributing-to-awesome-claude into .cursor/skills/contributing-to-awesome-claude/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contributing-to-awesome-claude", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add JSONbored/awesome-claude --skill contributing-to-awesome-claude -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "contributing-to-awesome-claude" agent skill from https://github.com/JSONbored/awesome-claude/tree/main/.claude/skills/contributing-to-awesome-claude into .gemini/skills/contributing-to-awesome-claude/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contributing-to-awesome-claude", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add JSONbored/awesome-claude --skill contributing-to-awesome-claude -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "contributing-to-awesome-claude" agent skill from https://github.com/JSONbored/awesome-claude/tree/main/.claude/skills/contributing-to-awesome-claude into .github/skills/contributing-to-awesome-claude/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contributing-to-awesome-claude", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add JSONbored/awesome-claude --skill contributing-to-awesome-claude -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "contributing-to-awesome-claude" agent skill from https://github.com/JSONbored/awesome-claude/tree/main/.claude/skills/contributing-to-awesome-claude into .opencode/skills/contributing-to-awesome-claude/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contributing-to-awesome-claude", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
contributing-to-awesome-claude
GitHub stars
300
Token cost
~1.9k tokens
SKILL.md length
800 words
Files
2
Skills in repo
2
Repo updated
First seen
Licence
MIT
At a glance
A skill your agent uses when writing, testing, or preparing ANY contribution or pull request to the JSONbored/awesome-claude (HeyClaude) repo — adding a community content entry (agent/MCP…
Works in 6 steps: Read the schema and examples first:… → One file, one PR. Add exactly one… → Source-back everything. Canonical… → …
Preparing ANY contribution
SKILL.md covers Step 0 — Which kind of…, If you're adding a content entry, If you're making a… and Common pitfalls (both paths)
Calls pnpm
What it does
Contributing To Awesome Claude is an agent skill from JSONbored/awesome-claude. Use when writing, testing, or preparing ANY contribution or pull request to the JSONbored/awesome-claude (HeyClaude) repo — adding a community content entry (agent/MCP server/skill/hook/command/rule/guide/collection/statusline), or making a platform/code change (website, registry package, MCP package, scripts). The repo has two separate review paths: a private, one-shot "HeyClaude submission gate" that decides single-file content PRs, and the shared gittensory-orb bot that posts an advisory readiness/linked-issue…
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `reference.md`).
It sits in Development, covering Pull requests and MCP servers. It works with Model Context Protocol. The repository describes itself as: HeyClaude is a curated registry and distribution surface for Claude and AI-workflow assets: agents, MCP servers, skills, commands, hooks, rules, guides, tools, jobs, Raycast… The licence is MIT.
When your agent uses it
Preparing ANY contribution
Making a platform/code change (website
Registry package
Example prompts
“HeyClaude submission gate”
“/contributing-to-awesome-claude”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
1Read the schema and examples first: content/SCHEMA.md (required/optional fields
2One file, one PR. Add exactly one content//.mdx. Do not touch
3Source-back everything. Canonical source/docs/repo URLs, not affiliate or
4A linked issue is genuinely optional here. CONTRIBUTING.md says plainly: "a PR
5Validate narrowly — a content PR does not need the full platform test suite
6Understand who actually decides your PR's fate. It is the private submission
What it can do on your machine
Read from SKILL.md and the folder at commit 372672b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Contributing To Awesome Claude loads about 1.9k tokens when it runs. Until then it costs about 225 tokens; SKILL.md has 800 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~225
When it runs· the whole SKILL.md, loaded when a task matches
~1.9k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/contributing-to-awesome-claude/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
contributing-to-awesome-claude
description
Use when writing, testing, or preparing ANY contribution or pull request to the JSONbored/awesome-claude (HeyClaude) repo — adding a community content entry (agent/MCP server/skill/hook/command/rule/guide/collection/statusline), or making a platform/code change (website, registry package, MCP package, scripts). The repo has two separate review paths: a private, one-shot "HeyClaude submission gate" that decides single-file content PRs, and the shared gittensory-orb bot that posts an advisory readiness/linked-issue comment on platform/code PRs but does not itself merge or close content PRs. Unlike JSONbored/gittensory and JSONbored/metagraphed, a linked issue is OPTIONAL here — do not import their mandatory-linked-issue rule into this repo. Invoke for any "contribute to / open a PR against / submit an entry to / fix a bug in awesome-claude (HeyClaude)" task.
Contributing to awesome-claude (HeyClaude)
HeyClaude is a file-backed directory of Claude/AI workflow resources
(content/<category>/<slug>.mdx) plus a website, registry package, and MCP package that
serve that content. It has two kinds of contribution with two different review
mechanisms — get the kind right first, everything else follows from it.
reference.md (next to this file) has the exhaustive command tables, the two-gate
architecture in detail, the current Codecov numbers, and the content-PR pitfalls. Read it
when a section below tells you to.
Standard CI + the shared gittensory-orb bot (advisory)
These are handled by genuinely different systems (see reference.md §1). Do not mix
them in one PR — CONTRIBUTING.md is explicit that a content PR touches exactly one
content/<category>/<slug>.mdx file, and platform/code changes should stay separate from
individual content imports.
If you're adding a content entry
Read the schema and examples first: content/SCHEMA.md (required/optional fields
per category) and examples/content/SUBMISSION_EXAMPLES.md (accepted vs.
rejected/rerouted examples — read this before you draft anything non-trivial).
One file, one PR. Add exactly one content/<category>/<slug>.mdx. Do not touch
README.md, apps/web/public/data/**, apps/web/src/generated/**,
apps/web/src/routeTree.gen.ts, or apps/web/public/downloads/** — those are
maintainer-owned generated outputs and editing them in a content PR is a reject
reason.
Source-back everything. Canonical source/docs/repo URLs, not affiliate or
tracking links. For hooks, MCP servers, skills, commands, and statuslines, fill
safetyNotes (execution, install, writes, destructive actions, background workers,
network access, account writes) and privacyNotes (local files, logs, credentials,
telemetry, retained data) — use prerequisites only for setup requirements and
disclosure only for commercial/listing status, not runtime safety.
A linked issue is genuinely optional here. CONTRIBUTING.md says plainly: "a PR
with no linked issue is fine." Filing your own issue and resolving it is fine too.
What is not fine is multi-account farming (opening an issue on one account,
"resolving" it from another) — see reference.md §4 for the exact contrast with
gittensory/metagraphed's mandatory policy.
Validate narrowly — a content PR does not need the full platform test suite:sh
Do not run generate:readme / generate:openapi or commit build output for a
one-file content submission — those are build-time outputs regenerated by CI/deploy.
Understand who actually decides your PR's fate. It is the private submission
gate, not gittensory-orb — see the Step 1 architecture note below and reference.md
§2 for the full disposition table.
Show full SKILL.md (388 more words)Show less
If you're making a platform/code change
Trace an existing analogue in apps/web/src/, packages/registry/src/, or
packages/mcp/ before writing new code — the repo has a strong existing house style
per surface.
Scope your validation to the surface you touched — see reference.md §3 for the
exact command lists AGENTS.md prescribes per change type (README, submission/API,
or general platform).
Codecov is enforcing, not informational, on code changes.codecov/patch
requires 70% coverage of your changed lines (5% threshold), and codecov/project
compares against your PR's own base commit (target: auto, 1% threshold). Both post
a real pass/fail status — see reference.md §5 for the exact codecov.yml values and
what's ignored (tests/, **/*.test.ts, **/*.config.ts,
apps/web/src/generated, apps/web/public/data, integrations).
Regenerate what you invalidate, then commit it — see reference.md §3 for the
exact regen command per surface (README, OpenAPI, etc.). Keep generated-artifact
churn out of PRs that don't need it; external contributors especially should leave
generated output out unless a maintainer asks for it.
gittensory-orb reviews your PR, but advisory only. It posts a readiness score,
linked-issue/no-issue check, and coverage-evidence comment — useful signal, but it
is not the merge authority for platform PRs either; ordinary CI + maintainer review
is (see reference.md §2).
Common pitfalls (both paths)
Editing generated files.README.md, apps/web/public/data/**,
apps/web/src/generated/**, apps/web/src/routeTree.gen.ts are maintainer-owned
outputs. Hand-editing them (in either a content or platform PR) is flagged/rejected.
Requesting HeyClaude host your ZIP/MCPB. Community package uploads for hosting at
/downloads/... are not accepted — link the source repo, an install command, or
copyable source content instead. Maintainer-built download artifacts are a separate,
post-review, maintainer-only path.
Bringing gittensory/metagraphed's mandatory-linked-issue habit here. It does not
apply — see reference.md §4.
Missing safety/privacy notes on a risk-bearing entry (a hook, MCP server, skill,
command, or statusline that executes code, writes files, calls out to third parties,
or runs in the background). Generic boilerplate is a common review nit; be specific
about what the resource can actually do.
Multi-account issue/PR farming. Explicitly against policy and is a permanent,
cross-repo block per CODE_OF_CONDUCT.md — not a gray area.
Chasing a review. CONTRIBUTING.md warns that pinging for status on a queued
submission deprioritizes it (adds ~5 days to the manual queue) rather than
speeding it up.
When you need the exact command lists, the full two-gate disposition tables, or the
current Codecov numbers verified against the live codecov.yml, read reference.md
in this skill directory.
Contributing To Awesome Claude next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Contributing To Awesome Claude compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Contributing To Awesome Claude this skillJSONbored/awesome-claude
Assess a FastMCP pull request for justified behavior, compatibility, and correctness, then follow CI and review feedback to a revision-specific verdict.
A skill your agent uses when starting any task the organization may already have an approved skill, prompt, MCP server, or Agent for: reviewing code, a commit, a diff, or a pull request; writing…
Maintenance of the contributor issue pipeline for JSONbored/awesome-claude (HeyClaude) — closing issues that are already done but not marked so, and keeping a small, high-value contributor-available…
A skill your agent uses when writing, testing, or preparing ANY contribution or pull request to the JSONbored/awesome-claude (HeyClaude) repo — adding a community content entry (agent/MCP…. Contributing To Awesome Claude is an agent skill from JSONbored/awesome-claude. Use when writing, testing, or preparing ANY contribution or pull request to the JSONbored/awesome-claude (HeyClaude) repo — adding a community content entry (agent/MCP server/skill/hook/command/rule/guide/collection/statusline), or making a platform/code change (website, registry package, MCP package, scripts).
When should I use Contributing To Awesome Claude?
Contributing To Awesome Claude fits situations like: preparing ANY contribution; making a platform/code change (website; registry package.
How do I install Contributing To Awesome Claude in Claude Code?
Run `npx skills add JSONbored/awesome-claude --skill contributing-to-awesome-claude -a claude-code`. Or copy the skill folder (.claude/skills/contributing-to-awesome-claude in JSONbored/awesome-claude) into .claude/skills/contributing-to-awesome-claude in your project. Claude Code loads it when a task matches its description.
How do I install Contributing To Awesome Claude in Codex?
Run `npx skills add JSONbored/awesome-claude --skill contributing-to-awesome-claude -a codex`. Or copy the skill folder (.claude/skills/contributing-to-awesome-claude in JSONbored/awesome-claude) into .agents/skills/contributing-to-awesome-claude in your project. Codex loads it when a task matches its description.
Can I use Contributing To Awesome Claude in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JSONbored/awesome-claude --skill contributing-to-awesome-claude -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/contributing-to-awesome-claude, .gemini/skills/contributing-to-awesome-claude, .github/skills/contributing-to-awesome-claude and .opencode/skills/contributing-to-awesome-claude in your project.
What does Contributing To Awesome Claude need to run?
Going by SKILL.md and its folder, Contributing To Awesome Claude needs the command-line tools its instructions call (pnpm).
Does Contributing To Awesome Claude access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Contributing To Awesome Claude safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Contributing To Awesome Claude use?
Contributing To Awesome Claude is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Contributing To Awesome Claude use?
About 1.9k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Contributing To Awesome Claude?
Skills that share tags, products or a category with Contributing To Awesome Claude: Review PR (PrefectHQ/fastmcp, 28k stars), Observal (Observal/Observal, 4.3k stars), Code Review (imbenrabi/Financial-Modeling-Prep-MCP-Server, 150 stars) and Fix Issue (PrefectHQ/fastmcp, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Contributing To Awesome Claude?
JSONbored (a GitHub user) maintains it in JSONbored/awesome-claude, which has 300 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on August 16, 2026.
Source: JSONbored/awesome-claude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
