hesreallyhim

5. Awesome Claude Code 整理Claude Code相關技能、工具與資源。想擴充工作流程，可以從這份清單開始找。 hesreallyhim/awesome-claude-code 這5個你最想先試哪個？ 4/4

5 Free GitHub Repos Every Claude Code User Needs in 2026 🔥 #shorts 5 free GitHub repos every Claude Code user needs in 2026 — open-source tools that make Claude Code faster, cheaper and easier to control. 1. ccusage — Claude Code token usage and cost tracker: ccusage/ccusage 2. Claude Code Router — use DeepSeek, Gemini and other models in Claude Code: musistudio/claude-code-router 3. MarkItDown by Microsoft — convert PDF, Word and PowerPoint to Markdown for LLMs: microsoft/markitdown 4. wshobson/agents — marketplace of AI agents, skills and commands: wshobson/agents 5. Awesome Claude Code — curated Claude Code commands, hooks and workflows: hesreallyhim/awesome-claude-code All free and open source. #ClaudeCode #Claude #GitHub #OpenSource #AItools #AIcoding #shorts

CLAUDE.md Best Practices: A Template for Unattended Agents Originally published at Unattended. CLAUDE.md best practices come down to three things. Keep the file short. Include only what Claude can't work out from the code. Write it so that a new agent with nobody around to ask can still finish the job. For unattended runs, that last point carries the most weight: the file should cover what to decide alone, what to stop on, and where to leave a note. If you only copy a style guide, the agent drifts, stalls, or keeps hitting permission denials overnight. Anthropic's own test for each line is: "Would removing this cause Claude to make mistakes?" Which option is right for you? Choose by how Claude will run, not by how big the project is. If you're unsure, start with the first row. | Your situation | What to pick first | First page to open | |---|---|---| | Beginner, no CLAUDE.md yet | Run /init, then cut the draft down to commands, rules, and "never" lines | Best practices: Write an effective CLAUDE.md | | Daily interactive work | A short project CLAUDE.md in git, plus skills for workflows you only need sometimes | Skills docs | | Nightly cron or claude -p job | The unattended template below, plus permission rules in settings | Headless mode | | CI with --bare | Pass the file yourself with --append-system-prompt-file | Bare mode section | | Tight token budget | Move rarely used content into skills or @ imports that only load when needed | /claude-code-how-to-see-token-usage-and-reduce-it/ | | Rules that must never break | A PreToolUse hook or a deny rule instead of a CLAUDE.md line | Hooks guide | Here's why, one line each. /init gives you a draft quickly, but the draft is too long. Skills keep everyday sessions lean. Unattended runs can't ask you anything. --bare doesn't load CLAUDE.md at all. Every line in CLAUDE.md costs tokens on every run. And a hook is the only kind of rule that can't be talked out of. What should a CLAUDE.md file example look like? A good CLAUDE.md example is short and scoped. It covers project context, commands, conventions, and explicit rules for what the agent must never do unattended. It isn't a full style guide. Anthropic's own sample is just two headings, "Code style" and "Workflow", with two bullets each. The docs say "There's no required format for CLAUDE.md files, but keep it short and human-readable." An unattended agent needs a few extra sections that an interactive user never thinks about, because the interactive user is the one answering questions. Here is an example for a scheduled job. It's illustrative, so replace the commands and paths with your own: # Project Static blog generator (Node 22). Content in /content, build output in /dist. # Commands - Install: npm ci - Test: npm test -- --run - Build: npm run build (must exit 0 before any commit) # Conventions - ES modules only. No new dependencies without a note in REPORT.md. # Autonomy: decide alone - Fix failing tests caused by your own change. - Retry a flaky network step once, then move on. # Autonomy: stop and report - Anything touching /migrations, .env, or CI config. - A task that needs more than ~10 files changed. - Any ambiguity you would normally ask about. # When blocked - Do not wait for an answer. Write the question and what you tried to BLOCKED.md, commit nothing, and end the run. # Done means - Tests pass, build exits 0, REPORT.md lists files changed and commands run. # Compaction - When compacting, always preserve the full list of modified files and any test commands. Each section maps to a documented behavior. "Done means" comes from Anthropic's advice to give Claude a check it can run. Their wording: it's "the difference between a session you watch and one you walk away from." The compaction line is close to word for word what the best practices page suggests for keeping critical context through summarization. The "When blocked" section exists because a run started with --permission-prompts none removes tools that need a person, such as AskUserQuestion, according to the headless docs. Without that section, Claude has no planned route when it wants to ask you something. Common pitfalls in examples: - Putting permissions in prose. "Never run rm -rf" in CLAUDE.md is a request, not a block. Use a deny rule or hook instead (see /claude-code-permissions-best-practices-headless-template/). - Describing the codebase file by file. Anthropic's exclude list names this directly, along with "Self-evident practices like 'write clean code'" (best practices). - No definition of done. Without one, "Claude stops when the work looks done." What are the core CLAUDE.md best practices? Keep CLAUDE.md concise, include only information that changes decisions, and write it as onboarding for an agent that can't ask questions. The reason is the context window. Anthropic says "Claude's context window fills up fast, and performance degrades as it fills," and CLAUDE.md loads at the start of every session. The memory docs add that Claude treats these files as "context, not enforced configuration." Every line costs tokens, and none of them is guaranteed to be followed. Anthropic's include/exclude table (source), rearranged for unattended use: | Include | Exclude | |---|---| | Bash commands Claude can't guess | Anything Claude can figure out by reading code | | Code style rules that differ from defaults | Standard language conventions | | Test instructions and preferred runner | Detailed API docs (link instead) | | Branch naming and PR conventions | Information that changes frequently | | Project-specific architecture decisions | Long explanations or tutorials | | Required env vars and environment quirks | File-by-file descriptions | | Non-obvious gotchas | "Write clean code" | Steps to write or rewrite yours: 1. In the project folder, run claude, then type /init to generate a starter file (best practices). 2. Delete every line that fails the test "Would removing this cause Claude to make mistakes?" 3. Add the autonomy, "when blocked", and "done means" sections from the example above. 4. Run /context to confirm the file loaded (best practices). 5. For a checked-in file, run /doctor, and Claude proposes cuts for content it can work out from the codebase (best practices). 6. Commit it to git. Two failure signals tell you which way to fix the file. Anthropic puts it this way: "If Claude keeps doing something you don't want despite having a rule against it, the file is probably too long." If Claude asks about something the file already answers, the wording is probably ambiguous (best practices). Use emphasis sparingly. Mark only the one rule Claude keeps skipping with "IMPORTANT", because "If you emphasize many lines, none of them stands out." What CLAUDE.md patterns do top GitHub repos use? Popular GitHub repos usually use three CLAUDE.md patterns: a command-and-convention sheet, a behavior-principles file, or a shared team file updated after every mistake. | Pattern | Public example | What it contains | Good for unattended runs? | |---|---|---|---| | Command and convention sheet | EDSL file in awesome-claude-code | Build/test commands, strict style (Black, mypy), testing requirements | Yes, if you add stop rules | | Behavior principles | multica-ai/andrej-karpathy-skills | Four principles about assumptions, simplicity, edit scope, goals | Partly; it has no project commands | | Living team file | Claude Code team's own file (Boris Cherny on X) | Corrections added whenever Claude gets something wrong | Yes; it grows from real failures | A few structural habits show up again and again. One is splitting rules by directory or file type: Anthropic documents nested CLAUDE.md files and a .claude/rules/ folder for rules scoped to specific files (memory docs). Another is pointing to longer docs with @path/to/import instead of pasting them in (best practices). Imports help with organization. They don't make the file cheaper if the imported file loads every session anyway. If your repo already has an AGENTS.md, the memory docs say Claude "can also read a repository's AGENTS.md files in place of CLAUDE.md," so you don't need two copies. Limitation: most public examples are written for someone sitting at the terminal. Hardly any say what the agent should do when it's stuck at 3 a.m., and that's the section you'll need to write yourself. What does Anthropic's official guidance say about CLAUDE.md? Anthropic's official guidance treats CLAUDE.md as a short, advisory memory file that loads every session. It covers commands, conventions, and gotchas, and you refine it like code. The points that matter most for automation, all from Anthropic's docs as of October 2026: - Scopes. CLAUDE.md can live at managed-policy, user (~/.claude/CLAUDE.md), project (./CLAUDE.md or ./.claude/CLAUDE.md), and local (./CLAUDE.local.md) levels (memory docs). On a VPS, the user-level file belongs to whatever account the cron job runs as. That may not be the account you set up interactively. - Auto memory is separate. Claude writes its own notes, and only the first 200 lines or 25KB load each session (memory docs). - Hooks vs instructions. "Unlike CLAUDE.md instructions which are advisory, hooks are deterministic and guarantee the action happens". To block an action no matter what Claude decides, the memory docs point to a PreToolUse hook (memory docs). - Treat it like code. "Review it when things go wrong, prune it regularly, and test changes by observing whether Claude's behavior actually shifts" (best practices). The headless page is where unattended setups most often go wrong. Adding --bare skips auto-discovery of "hooks, skills, custom commands, subagents, installed plugins, MCP servers, auto memory, and CLAUDE.md" (headless docs). The same page warns that "--bare is the recommended mode for scripted and SDK calls, and will become the default for -p in a future release." So a cron job that depends on CLAUDE.md being picked up automatically may stop following it after an update, with no error to tell you. To make the file load whatever the default turns out to be: 1. Keep the unattended rules in a file, for example CLAUDE.md or a separate AGENT_RULES.md. 2. Pass it explicitly. The headless docs list --append-system-prompt-file for adding to the system prompt in bare mode: claude --bare -p "Run the nightly content check" \ --append-system-prompt-file ./CLAUDE.md \ --allowedTools "Read,Edit,Bash(npm test *)" \ --permission-prompts none 3. Remember that bare mode doesn't use your subscription login. Set ANTHROPIC_API_KEY first (headless docs). Two more defaults matter. With Claude Code v2.1.302 or later, claude -p starts in Manual mode when nothing sets a permission mode, and a call that needs approval is denied unless something approves it. --permission-prompts requires v2.1.259 or later (headless docs). This is why CLAUDE.md has to tell the agent what to do after a denial. The full flag set is covered in /claude-code-headless-mode-flags-auth-and-cost-2026/. What do Reddit discussions say works (and fails) in CLAUDE.md? The usual complaint on Reddit and developer forums is that long CLAUDE.md files get ignored. The fix people recommend is to trim the file to essentials and prune it regularly. Plenty of community posts carry titles like "Why your long CLAUDE.md gets ignored, and how to fix it", and forum threads ask whether popular rule files actually help (Devtalk). Treat these as anecdotes, not measurements. The pattern does line up with Anthropic's own failure list, which names "The over-specified CLAUDE.md" and says important rules "get lost in the noise". What community advice tends to get right: - Add rules only after a real mistake. That matches the practice used by the Claude Code team (next sections). - Turn rules into hooks. Anthropic's own fix for an over-specified file: "If Claude already does something correctly without the instruction, delete it or convert it to a hook." What it tends to get wrong for unattended work: - Shouting. Files full of "ALWAYS" and "NEVER" in capitals cancel themselves out, since emphasis only works on one line. - Language and tone rules at the top. In a nightly job nobody reads the tone. Spend those lines on stop conditions instead. For example, say your overnight agent keeps editing CI config even though a rule forbids it. Community advice would tell you to move the rule higher in the file. The more reliable fix is a deny rule or a PreToolUse hook on that path, with one line left in CLAUDE.md explaining why. Copy-paste hook scripts for this are in /claude-code-hooks-examples-7-copy-paste-scripts/. What does Andrej Karpathy say about CLAUDE.md style files? Karpathy didn't write a CLAUDE.md himself. The popular "Karpathy CLAUDE.md" is a community file built from his posts on how LLMs fail at coding, and it focuses on behavior rather than style. The repo multica-ai/andrej-karpathy-skills showed about 223.8k stars when checked in October 2026. It turns his observations into four principles: Think Before Coding, Simplicity First, Surgical Changes, and Goal-Driven Execution. The line that matters most for unattended runs is the one the repo quotes from Karpathy: "Don't tell it what to do, give it success criteria and watch it go." How to use it in a scheduled setup: 1. Keep "Surgical Changes" and "Goal-Driven Execution". They limit drift and define when the agent is finished. 2. Rewrite "Think Before Coding" for unattended runs. The original tells the agent to ask for clarification when a request is ambiguous. Overnight, nobody is there to answer, so change that to "write the question to BLOCKED.md and stop." 3. Add your own commands. The file has no project-specific build or test lines. Who it's not for: if your CLAUDE.md is already near the size where rules get lost, pasting in a generic principles file makes that worse. Take the two principles you need and leave the rest. How is CLAUDE.md best practice evolving for 2026 (skills, headless agents)? In 2026, CLAUDE.md is shrinking. Workflows are moving into skills, hard rules into hooks and permission settings, and the core file is turning into a statement of autonomy boundaries. The split, according to Anthropic's docs as of October 2026: | Content | Put it in | Why | |---|---|---| | Always-true commands, conventions, stop rules | CLAUDE.md | "CLAUDE.md is loaded every session, so only include things that apply broadly" | | Occasional domain knowledge or workflows | .claude/skills/<name>/SKILL.md | Claude loads skills on demand (best practices) | | Workflows with side effects | Skill with disable-model-invocation: true | Only runs when you trigger it (best practices) | | Must-never-happen actions | Hooks, deny rules | Deterministic (hooks guide) | | "Keep going until tests pass" | /goal condition or a Stop hook | Lets "an unattended run finish correctly without you" | Skills also work headless. User-invoked skills run in -p mode if you include /skill-name in the prompt string (headless docs). A clean nightly setup looks like this: 1. CLAUDE.md, about a screen long: commands, autonomy rules, "when blocked", "done means". 2. A skill such as /nightly-report that holds the step-by-step procedure. 3. Cron calls claude -p "/nightly-report" --permission-mode dontAsk --allowedTools "...". Under dontAsk, Claude Code "denies every call that would otherwise prompt" (headless docs). 4. A Stop hook runs your test command, so the run can't end while tests are red. Auto mode is the other 2026 change. From v2.1.283 it's the starting permission mode for interactive terminal and VS Code sessions, with a classifier that blocks actions like scope escalation (best practices). It reduces prompts, but it doesn't replace stop rules. The classifier judges risk. It doesn't know your business rules, such as "never publish on Sundays". Scheduling details are in /claude-code-cron-job-setup-run-automations-overnight/. What do practitioner write-ups (Medium, Boris Cherny) add to best practices? Practitioners, including Claude Code creator Boris Cherny, add one habit: update CLAUDE.md after every mistake you catch. Keep the file small enough that the new rule doesn't get lost. Cherny described the Claude Code team's setup on X in January 2026. They share one CLAUDE.md for the repo, check it into git, and "the whole team contributes multiple times a week". Whenever Claude gets something wrong, they add it to the file. In a follow-up post, he said he tags @.claude on coworkers' PRs to add CLAUDE.md lines through the Claude Code GitHub Action. For very long tasks, he mentioned having Claude verify its work or using a Stop hook (thread). Adapted for unattended runs: 1. Each morning, read the run's REPORT.md and BLOCKED.md. 2. For each real mistake, decide on the fix. A one-line CLAUDE.md rule works if the mistake was a judgment call. A hook or deny rule is better if it must never happen again. 3. Add the line in the same commit as the fix. 4. Once a month, delete rules the agent now follows without being told. Pitfall: a file that only grows. Adding a line after every mistake without ever pruning produces exactly the bloated file Anthropic warns about. A related mistake is reacting to a stalled run by adding more instructions. Stalls usually come from permissions or context, not missing rules. Check /why-claude-code-stops-mid-automation-and-how-to-fix-it/ before you edit the file. Next steps Do today (DIY): 1. Open your project, run /init (or open your existing file with /memory), and cut every line that fails "Would removing this cause Claude to make mistakes?" 2. Add four sections from the example: "Autonomy: decide alone", "Autonomy: stop and report", "When blocked", and "Done means". 3. If your cron job uses -p, add --append-system-prompt-file ./CLAUDE.md now, so the coming --bare default doesn't silently drop the file. If you'd rather not do it yourself: Anthropic's paid plans include Claude Code. Pro is $20/month ($17/month billed annually), and Max starts at $100/month (as of October 2026; check the official pricing page). Pro suits one person running light scheduled jobs. It's not a good fit if you need many long runs per night, because Claude Code "shares the same usage limits as the rest of your plan." Bare-mode runs bill through an API key instead, so they don't draw on a subscription. Anthropic also publishes a Claude Code 101 course on CLAUDE.md; check the page for current access terms. It suits beginners, but it won't write your stop rules for you. Related guides on this site: - /claude-code-permissions-best-practices-headless-template/ - /claude-code-hooks-examples-7-copy-paste-scripts/ - /claude-code-headless-mode-flags-auth-and-cost-2026/ - /claude-code-cron-job-setup-run-automations-overnight/ - /why-claude-code-stops-mid-automation-and-how-to-fix-it/ FAQ Where can I find CLAUDE.md best practices examples? Anthropic's best practices page has a short official sample and an include/exclude table. Community examples are collected in awesome-claude-code. The template in this guide adds the unattended sections most public examples leave out. What are Anthropic's CLAUDE.md best practices? Keep it short. Include only commands, rules that differ from defaults, and gotchas. Check it into git and prune it regularly. Anthropic also says CLAUDE.md is advisory, so anything that must always happen belongs in a hook (best practices). Are there good CLAUDE.md best practices on GitHub? Yes. The most-starred example is multica-ai/andrej-karpathy-skills, a behavior-principles file. Language-specific files such as the EDSL example in awesome-claude-code show the command-sheet pattern. Either way, add your own commands and stop rules. What are the Karpathy CLAUDE.md best practices? They're four principles taken from Karpathy's posts: Think Before Coding, Simplicity First, Surgical Changes, and Goal-Driven Execution. Karpathy didn't publish the file himself; the multica-ai repo did. For unattended runs, change "ask for clarification" to "log the question and stop". Sources - Best practices for Claude Code (Anthropic) - How Claude remembers your project (Anthropic memory docs) - Run Claude Code programmatically (headless docs) - Hooks guide (Anthropic) - Skills (Anthropic) - Claude pricing - Claude Code 101: The CLAUDE.md file (Anthropic Academy) - Boris Cherny on X: shared CLAUDE.md - Boris Cherny on X: tagging @.claude in PRs - Boris Cherny on X: long-running tasks - multica-ai/andrej-karpathy-skills (GitHub) - awesome-claude-code EDSL CLAUDE.md (GitHub) - Why your long CLAUDE.md gets ignored (DEV Community) - Has anyone tried the Karpathy CLAUDE.md rules? (Devtalk) - Writing the Best CLAUDE.md (DataCamp) - Creating the Perfect CLAUDE.md (Dometrain) --- This article was created with the help of AI. Sources are linked inline; check the official documentation for the latest details.

Claude Code 玩不转？这个仓库把社区玩法全收进来了。 工作流、Slash Commands、Hooks、插件、自动化技巧，一个合集打包。 我翻了半小时，Slash Commands 那块最实用。 仓库：hesreallyhim/awesome-claude-code 你最想先试哪块？ t.co

Huge props to hesreallyhim for pulling this incredible collection together—seriously slick workflow and architecture for getting the absolute most out of Claude Code. ⚡ 🔗 项目地址：hesreallyhim/awesome-claude-code

7 Free GitHub Repos for Claude Code: Memory, Research, PPT and Video AI (Part 2) ✅ No Code App Building - Bootcamp Registration 👉 roydigital.in 🎬 Claude is smart, but it has 3 hidden flaws: it forgets everything in a new chat, its work gets worse as a chat gets long (context rot), and it cannot see what people are saying on YouTube, Reddit or X. In this video I show 6 free, open source GitHub repos for Claude Code that fix exactly these flaws, plus one secret 7th repo you should install before any other. 🔍 For every repo you see the real GitHub page, the stars, what it does, and how to install it. You do not need to be a coder: copy the link, paste it in Claude Code and say "install this". ⏱️ TIMESTAMPS 0:00 Claude's 3 hidden flaws 1:32 Who I am 1:48 Why these GitHub repos matter 3:03 Repo 1: claude-mem (memory) 4:24 Repo 2: GSD Core (context rot) 5:51 Repo 3: Agent-Reach (internet research) 7:25 Repo 4: no-ai-slop (human writing) 8:47 Repo 5: PPT Master (editable PowerPoint) 9:53 Repo 6: video-use (video editing) 11:09 6 repos, 1 workflow 12:08 Repo 7 (secret): SkillSpector by NVIDIA 13:25 Where to start 14:10 The real AI skill 14:36 Which repo will you install first? 🔗 ALL REPOS FROM THE VIDEO (free and open source, not sponsored) 1️⃣ claude-mem (memory for Claude): thedotmack/claude-mem 2️⃣ GSD Core (big projects without context rot): open-gsd/gsd-core (the original get-shit-done repo is archived, do not use the old link) 3️⃣ Agent-Reach (YouTube, Reddit, X and web research): Panniantong/Agent-Reach 4️⃣ no-ai-slop (writing that does not sound like AI): petergyang/no-ai-slop 5️⃣ PPT Master (editable PowerPoint decks): hugohe3/ppt-master 6️⃣ video-use (raw footage to edited video): browser-use/video-use 7️⃣ SkillSpector by NVIDIA (scan any repo before you install it): NVIDIA/SkillSpector 👉 More repos: awesome-claude-code: hesreallyhim/awesome-claude-code 🛡️ SAFETY FIRST: research on 31,132 AI agent skills found security problems in about 1 in 4 of them. Scan every new repo with SkillSpector before you install it, even the ones I recommend. ▶️ Missed Part 1 (the Lamborghini vs Swift one)? Watch it here 👉 youtu.be 🎓 This Sunday there is also a live No-Code App Bootcamp: build your first app with AI from zero, without coding 👉 roydigital.in 📚 SOURCES 👉 Agent Skills in the Wild (security study of AI agent skills): arxiv.org 👉 Greg Isenberg, GitHub repos video: youtube.com 👉 Nate Herk, GitHub repos video: youtube.com 📅 Star counts checked on GitHub on 14 Oct 2026; they change every day. 📌 HONEST NOTES 🎙️ The voice in this video is my own AI voice clone (ElevenLabs), trained on my real recordings with my permission. 🔢 Some numbers in the video (like claude-mem's token savings) are the makers' own claims, and the video says so. 🔑 video-use needs an ElevenLabs API key for transcription (it uses your ElevenLabs credits). 🆓 The claude-mem repo is free and open source; its installer may also offer an optional hosted trial, which you can skip. ⚠️ Agent-Reach: never connect your main X, Reddit, Instagram or LinkedIn account, use a second account. 💬 Comment which repo you will install first, and which Claude problem still bothers you. I read every comment and reply myself, not with AI. #ClaudeCode #GitHub #AI --------------------------------------------------------------------- Disclaimer: Knowledge in this video is purely based on my experience. The results may vary from person to person and from time to time and I don't guarantee any fixed or variable results for an individual or group of individuals. --------------------------------------------------------------------- ✅ INSTAGRAM | instagram.com ✅ TWITTER | twitter.com ✅ FACEBOOK PAGE | facebook.com --------------------------------------------------------------------- Thanks for watching the video🙏

@marcoporracin haz intentado con esta? obra/superpowers o esta Graphify-Labs/graphify O esta compilación? hesreallyhim/awesome-claude-code Basicamente te ayuda muchisimo, sin eso hay muchas que siemplemente no puedes hacer

5.5 万颗星的 Claude Code 资源清单：命令、技能、工作流按用途分好类，只留被社区验证过的那批。 装一堆插件用得上的没几个，工具越多越乱时最值钱的是别人替你看过的目录。 hesreallyhim/awesome-claude-code

Best Claude Code skills in 2026: 27 picks by job A skill gives Claude Code a method: how to review a plan, how to lay out a page, how to write a figure that survives print. This list groups the skills worth installing by the job you want done. It mixes two kinds: community skills, open-source folders maintained on GitHub that SkillGild lists and credits, and hosted skills, which run through SkillGild with free monthly runs. Each entry links to its SkillGild page, where the install command, license and author are shown. Every skill here installs with one command once the SkillGild CLI is set up: skillgild install <slug> --agent claude-code Use --agent codex, cursor or gemini-cli for other clients; the folder format is the same. Writing Humanizer by blader. Rewrites AI-sounding text so it reads like a person wrote it, using the patterns catalogued in Wikipedia's guide to AI writing, then audits its own output. The most-searched community skill of the year. Stop Slop by Hardik Pandya. Seven rules that strip the tells (not-X-but-Y contrasts, staged openers, forced triads, filler closers) from any draft. Many people run it as the final pass after Humanizer. Writing Guidelines by Vercel. Reviews documentation and product prose against 80-plus rules from Vercel's style guide. Best for docs and UI copy rather than essays. Humanizer and Stop Slop are often confused: Humanizer vs Stop Slop sets out what each one changes and the order to run them in. Planning and workflow Superpowers by Jesse Vincent. A complete development methodology as composable skills: brainstorm, plan, work test-first, review, hand off. Install it when you want Claude Code to behave like a disciplined engineer rather than a fast typist. grill-me by Matt Pocock. Interviews you about a plan, one question at a time, until the holes are gone. Run it before any non-trivial change. From the same author: Handoff compacts a long conversation into a document another agent can continue from, and TDD enforces a red-green-refactor loop. GSD. A context-engineering framework that runs Claude Code through phases with planning, verification and fresh context per phase. Heavier than Superpowers; suits long builds. Karpathy Guidelines. Four rules drawn from Andrej Karpathy's observations on how LLMs fail at code: think before coding, simplicity first, surgical changes, verify. Small, and worth installing everywhere. Ponytail by Dietrich Gebert. The lazy senior developer ruleset: climb the dependency tree before writing anything, reuse what exists, write less code. OpenSpec Propose (hosted). Spec-first proposals that turn an idea into a change proposal with requirements and tasks before any code, following the OpenSpec workflow. Frontend and design The full ranking, with four of these run on the same brief, is in the top 10 Claude frontend and design skills. Impeccable by Paul Bakaus. A design language for AI harnesses with 24 commands to craft, audit, polish and harden interfaces. The most complete design skill available. Taste Skill (hosted; from Leonxlnx's taste-skill). Anti-slop defaults for landing pages and product UI: layout, type, colour and spacing rules that keep generated pages from looking generic. We tested it on a real brief. Frontend Design by Anthropic. Anthropic's own baseline for distinctive interface code, shipped in the official plugin marketplace. See what it changed on a real brief. UI UX Pro Max. A searchable database of styles, palettes and font pairings that the agent reasons over before it codes. Good when you need options rather than one opinion (tested here). Emil Kowalski's skills: Animate, Apple Design and design engineering. Motion and polish from a design engineer's point of view: easing, springs, when not to animate. Logo Design (hosted). SVG logo marks from a brief, with variants and a review checklist. Testing and review Playwright Skill by lackeyjb. General-purpose browser automation: the agent writes and runs Playwright scripts to click through a flow, screenshot every route and capture console errors. Pair it with the Playwright MCP server from the best MCP servers for Claude Code. Webapp Testing by Anthropic. A verification method for local web apps in a real browser. Code Review and Security Guidance by Anthropic. Official plugins: a structured review of a diff or pull request, and pattern warnings on risky code as it is written. Research and data Deep Research by 199 Biotechnologies. An eight-phase pipeline (scope, plan, retrieve, triangulate, synthesise, critique) that returns cited reports with source-credibility scores. Scientific Agent Skills by K-Dense. 177 validated skills for science: single-cell RNA-seq, structure prediction, statistics, figure generation. Academic Plotting (hosted). Publication-quality matplotlib figures with a hosted palette validator. See the research plots walkthrough for a recorded run. last30days. Researches any topic across Reddit, X, YouTube, Hacker News and GitHub for the last thirty days, which is what you want for "what are people saying about" questions. Documents and productivity Anthropic's document skills: pptx, docx, xlsx and pdf. Create and edit PowerPoint decks, Word documents, Excel workbooks with live formulas, and read, merge, split and fill PDFs. They are source-available rather than open source: install and use them, but do not redistribute them. Obsidian Skills by Steph Ango. Official skills from Obsidian's CEO that teach an agent Obsidian-flavoured Markdown, canvases and properties so it edits a vault correctly. I Have ADHD. Stops the agent burying the answer: short, action-first, numbered. Useful far beyond its name. Marketing and SEO Marketing Skills by Corey Haines. Sixty-plus skills for CRO, copywriting, SEO, paid ads, email, pricing and analytics. The largest marketing set and the one to install first. Claude SEO by Agrici Daniel. 26 sub-skills and 19 specialist agents for full SEO audits: technical, content, schema, local, e-commerce, backlinks, sitemaps and generative-engine readiness. Marketing is the deepest category here, so it has its own page: best Claude skills for marketing covers these two sets plus the copy, creative and research skills that go with them. Video Brag (hosted). Turns a repository into a launch video. Remotion Skills by Remotion are the official skills for video in React. HyperFrames renders HTML compositions to video, and Lyric Music Video times animated lyrics to the syllable. Compare them in Claude Code video skills. Images Nano Banana by Keanan Koppenhaver. Generate and edit images from Claude Code with Google's Gemini image models; bring a Gemini API key. Excalidraw Diagram draws diagrams as editable Excalidraw files and renders them to check the layout. Making your own Skill Creator by Anthropic scaffolds a correct SKILL.md and runs an evaluation loop over your examples. The step-by-step version is in how to create a Claude skill. Claude Code skills on GitHub Almost every community skill above lives in a public GitHub repository, and most people find them through a handful of large lists. These are the places to look, with star counts and last-push dates checked on 9 October 2026: | Repository | What it is | Stars | License | | --- | --- | --- | --- | | anthropics/skills | Anthropic's own skills: Frontend Design, Skill Creator, Webapp Testing, MCP Builder and the document skills | 180k | Varies per skill | | anthropics/claude-plugins-official | The official Claude Code plugin directory, which bundles several of those skills as plugins | 37.5k | Apache-2.0 | | obra/superpowers | The Superpowers methodology listed under planning above | 297k | MIT | | ComposioHQ/awesome-claude-skills | The largest "awesome Claude skills" list | 76.7k | None stated | | hesreallyhim/awesome-claude-code | A broader list for Claude Code: skills, hooks, commands and workflows | 55.3k | Not standard | | VoltAgent/awesome-agent-skills | 1,000+ agent skills from official teams and the community, across agents | 35.4k | MIT | | travisvn/awesome-claude-skills | A curated list of skills and resources; last pushed in April 2026 | 15.3k | None stated | | BehiSecc/awesome-claude-skills | Another curated list of Claude skills | 10.2k | None stated | Stars measure attention, not quality. An awesome list links to repositories; it does not review them. Before you install a skill from any list, open its SKILL.md and any scripts it runs, check that the repository has a license, and look at when it was last updated. A skill can tell your agent to run commands on your machine. You can install a GitHub skill by hand: clone the repository and copy the skill's folder into ~/.claude/skills/ (or .claude/skills/ in a project). The install guide covers the folder locations for each agent. Every community skill in this article is also listed on SkillGild with its author, license and source credited, and skillgild install <slug> copies the same folder from its upstream repository. How we chose Each pick does one job well, is maintained by a named person or organisation, and is used widely enough that people search for it by name (see the state of Claude skills for the search data). We read every README and verified the repository, author and license before listing it on SkillGild; licenses marked "not stated" on a listing mean the repository had no license file at the time of review, so treat the code as all rights reserved until one is added. Community skills run locally in your agent with your own model; SkillGild lists and credits them and installs them from source. Hosted skills run through the SkillGild MCP server, which keeps private prompts and server tools off your machine and counts runs against a monthly allowance. Both appear in the same catalog, and the Claude Code skills page lists everything that works in Claude Code.