HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
multica-ai
andrej-karpathy-skills
AI & Machine Learning2026–2026
multica-ai / andrej-karpathy-skills

andrej-karpathy-skills

A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.

5Distinct people
5Mentions
0Explicit recommenders
232.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month5 dated mentions

Observed mentions: 2026-01-27 23:44:12 UTC to 2026-09-07 03:03:14 UTC.

012026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJan 20262026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 20262026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC110
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC101
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC000
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC110
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC000
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC101
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC000
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC000
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC101

What Hacker News says

5 sources
> has anyone found a good way to improve code quality? just wondering ... - keep prompts focused on atomic tasks. - use expert prompting[0] when possible. - require coding agents to verify changes. - require coding agents to create/update unit tests with 100% coverage. - use git to commit/revert atomic tasks manually. - leverage planning capabilities to review instead of recover. - consider using something like Karpathy guidelines[1]. - leverage Constraint Programming[2] concepts when formulating prompts. 0 - https://arxiv.org/pdf/2305.14688 1 - https://github.com/multica-ai/andrej-karpathy-skills 2 - https://en.wikipedia.org/wiki/Constraint_programming
In Ponytail: Lazy Senior Engineer Skill
Five of the top 10 AI repos on GitHub trending this week are "skills" packs for Claude Code. The label is doing wildly different work across them. forrestchang/andrej-karpathy-skills (~70k stars). One CLAUDE.md file, four behavioral rules, derived from Karpathy's January tweet about agent coding failure modes (silent wrong assumptions, over-complication, not surfacing tradeoffs). Karpathy didn't write the file or endorse it. The README has had a typo in the install command (andrej-karpthy-skills, missing the second "a") since launch. A second repo, multica-ai/andrej-karpathy-skills, is trending in parallel with the same content republished. mattpocock/skills (~115k stars). Matt Pocock's personal .claude/skills/ folder, published. About 10 small SKILL.md files: tdd, to-issues, to-prd, triage, zoom-out, setup-matt-pocock-skills. Each one is
Read the rest
a self-contained markdown prompt with YAML frontmatter declaring when it should auto-fire. Third-party writeups describe it as a reference implementation of Anthropic's SKILL.md format. affaan-m/everything-claude-code (~175k stars; plus a second repo affaan-m/ECC at ~205k stars which is the same project under a renamed identifier). 48 agent definitions, 182 SKILL.md files, 68 legacy slash-command shims, hooks, rules, MCP configurations, npm packages (ecc-universal, ecc-agentshield), a Tkinter desktop dashboard, and a security scanner (1282 tests, 102 static analysis rules). Includes per-harness adapters for Claude Code, Codex CLI, Codex macOS app, Cursor, OpenCode, Gemini CLI, and Antigravity. Anthropic hackathon winner. Three orders of magnitude in scope under one word. What's underneath is Anthropic's SKILL.md format: markdown with YAML frontmatter, auto-loaded at session start. The frontmatter declares when the skill should fire; the harness picks relevant skills based on the description and injects only those into context. It's RAG-over-prompts using model-based routing on descriptions rather than vector stores. The format works well enough that you can mix skills from different authors in the same .claude/ folder without the harness caring, which is the actual reason this took off. Trending packs ship per-harness adapters on top of that substrate so the same skill content installs into Codex, Cursor, OpenCode, etc., with per-harness rewrites. The trending list is measuring three different things under one label: small high-leverage CLAUDE.md edits (karpathy-skills, cost-to-try wins), curated personal reference sets (mattpocock, distribution-by-reputation wins), and full framework distributions (ECC, comprehensive-catalog-marketing wins). Stars are not telling us which of these are surviving on actual reuse. The defensibility implications are uncomfortable. When a startup pitches "our agent does X better because of our prompting and workflow," and the artifact is a folder of markdown files with YAML frontmatter, that's a Notion template, not a moat. Karpathy's four rules will be absorbed into the default behavior of the next Claude release. mattpocock's TDD skill is sharp but copyable. ECC's 182-skill catalog is impressive engineering, but the prompts inside can be diffed and ported in an afternoon. What does seem to hold value after reading these: harness ergonomics (install paths, hook plumbing, cross-tool sync scripts, MCP-server lifecycle), distribution (mattpocock-the-person is a moat, the markdown isn't), and security tooling around skill files specifically (AgentShield, ECC's scanner, is a real product even if the skills it scans aren't). None of those are the prompt. Repos: github.com/forrestchang/andrej-karpathy-skills, github.com/mattpocock/skills, github.com/affaan-m/everything-claude-code.
In What's inside the trending "skills" repos for Claude Code

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.