From e57fc6dfdfeb2f888d1887495d200fd7f01c32d0 Mon Sep 17 00:00:00 2001 From: KeyInfo Bot Date: Wed, 10 Jun 2026 21:52:53 +0800 Subject: [PATCH] Publish karpathy-guidelines skill to marketplace Constraint: Public skills are published only by explicit administrator action unless they are tracked third-party market sources. Confidence: high Scope-risk: narrow Directive: Keep private/internal skills out of the public marketplace. Tested: Marketplace validation passed. --- .agents/plugins/marketplace.json | 12 ++++ .../codex/.agents/plugins/marketplace.json | 12 ++++ .../.codex-plugin/plugin.json | 37 ++++++++++ .../skills/karpathy-guidelines/SKILL.md | 67 +++++++++++++++++++ 4 files changed, 128 insertions(+) create mode 100644 plugins/codex/plugins/karpathy-guidelines/.codex-plugin/plugin.json create mode 100644 plugins/codex/plugins/karpathy-guidelines/skills/karpathy-guidelines/SKILL.md diff --git a/.agents/plugins/marketplace.json b/.agents/plugins/marketplace.json index 8dbadf55c..f5eebcdca 100644 --- a/.agents/plugins/marketplace.json +++ b/.agents/plugins/marketplace.json @@ -135,6 +135,18 @@ "authentication": "ON_INSTALL" }, "category": "工具" + }, + { + "name": "karpathy-guidelines", + "source": { + "source": "local", + "path": "./plugins/codex/plugins/karpathy-guidelines" + }, + "policy": { + "installation": "AVAILABLE", + "authentication": "ON_INSTALL" + }, + "category": "开发工具" } ] } diff --git a/plugins/codex/.agents/plugins/marketplace.json b/plugins/codex/.agents/plugins/marketplace.json index bd4e74795..1cd1bad21 100644 --- a/plugins/codex/.agents/plugins/marketplace.json +++ b/plugins/codex/.agents/plugins/marketplace.json @@ -135,6 +135,18 @@ "authentication": "ON_INSTALL" }, "category": "工具" + }, + { + "name": "karpathy-guidelines", + "source": { + "source": "local", + "path": "./plugins/karpathy-guidelines" + }, + "policy": { + "installation": "AVAILABLE", + "authentication": "ON_INSTALL" + }, + "category": "开发工具" } ] } diff --git a/plugins/codex/plugins/karpathy-guidelines/.codex-plugin/plugin.json b/plugins/codex/plugins/karpathy-guidelines/.codex-plugin/plugin.json new file mode 100644 index 000000000..9392ce90c --- /dev/null +++ b/plugins/codex/plugins/karpathy-guidelines/.codex-plugin/plugin.json @@ -0,0 +1,37 @@ +{ + "name": "karpathy-guidelines", + "version": "1.0.0", + "description": "andrej-karpathy-skills 是一个由社区开发者 forrestchang 整理的 Claude Code 最佳实践配置集，灵感来源于AI领域顶级大牛 Andrej Karpathy（前特斯拉AI总监、OpenAI联合创始人）在使用 AI 编程助手过程中分享的经验和技巧。", + "author": { + "name": "EAPIL", + "url": "https://git.playones.com/arechen/EapilSkillMarket" + }, + "homepage": "https://git.playones.com/arechen/EapilSkillMarket", + "repository": "https://git.playones.com/arechen/EapilSkillMarket", + "license": "Proprietary", + "keywords": [ + "eapil", + "codex-skill", + "karpathy-guidelines" + ], + "skills": "./skills/", + "interface": { + "displayName": "karpathy-guidelines", + "shortDescription": "andrej-karpathy-skills 是一个由社区开发者 forrestchang 整理的 Claude Code 最佳实践配置集，灵感来源于AI领域顶级大牛 Andrej Karpathy（前特斯拉AI总监、OpenAI联合创始人）在使用 AI 编程助手过程中分享的经验和技巧。", + "longDescription": "andrej-karpathy-skills 是一个由社区开发者 forrestchang 整理的 Claude Code 最佳实践配置集，灵感来源于AI领域顶级大牛 Andrej Karpathy（前特斯拉AI总监、OpenAI联合创始人）在使用 AI 编程助手过程中分享的经验和技巧。", + "developerName": "EAPIL", + "category": "开发工具", + "capabilities": [ + "Read", + "Write" + ], + "defaultPrompt": [ + "使用 karpathy-guidelines 帮我完成这个任务。" + ], + "websiteURL": "https://git.playones.com/arechen/EapilSkillMarket", + "privacyPolicyURL": "https://git.playones.com/arechen/EapilSkillMarket", + "termsOfServiceURL": "https://git.playones.com/arechen/EapilSkillMarket", + "brandColor": "#2563EB", + "screenshots": [] + } +} diff --git a/plugins/codex/plugins/karpathy-guidelines/skills/karpathy-guidelines/SKILL.md b/plugins/codex/plugins/karpathy-guidelines/skills/karpathy-guidelines/SKILL.md new file mode 100644 index 000000000..6a62d0441 --- /dev/null +++ b/plugins/codex/plugins/karpathy-guidelines/skills/karpathy-guidelines/SKILL.md @@ -0,0 +1,67 @@ +--- +name: karpathy-guidelines +description: Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria. +license: MIT +--- + +# Karpathy Guidelines + +Behavioral guidelines to reduce common LLM coding mistakes, derived from [Andrej Karpathy's observations](https://x.com/karpathy/status/2015883857489522876) on LLM coding pitfalls. + +**Tradeoff:** These guidelines bias toward caution over speed. For trivial tasks, use judgment. + +## 1. Think Before Coding + +**Don't assume. Don't hide confusion. Surface tradeoffs.** + +Before implementing: +- State your assumptions explicitly. If uncertain, ask. +- If multiple interpretations exist, present them - don't pick silently. +- If a simpler approach exists, say so. Push back when warranted. +- If something is unclear, stop. Name what's confusing. Ask. + +## 2. Simplicity First + +**Minimum code that solves the problem. Nothing speculative.** + +- No features beyond what was asked. +- No abstractions for single-use code. +- No "flexibility" or "configurability" that wasn't requested. +- No error handling for impossible scenarios. +- If you write 200 lines and it could be 50, rewrite it. + +Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify. + +## 3. Surgical Changes + +**Touch only what you must. Clean up only your own mess.** + +When editing existing code: +- Don't "improve" adjacent code, comments, or formatting. +- Don't refactor things that aren't broken. +- Match existing style, even if you'd do it differently. +- If you notice unrelated dead code, mention it - don't delete it. + +When your changes create orphans: +- Remove imports/variables/functions that YOUR changes made unused. +- Don't remove pre-existing dead code unless asked. + +The test: Every changed line should trace directly to the user's request. + +## 4. Goal-Driven Execution + +**Define success criteria. Loop until verified.** + +Transform tasks into verifiable goals: +- "Add validation" → "Write tests for invalid inputs, then make them pass" +- "Fix the bug" → "Write a test that reproduces it, then make it pass" +- "Refactor X" → "Ensure tests pass before and after" + +For multi-step tasks, state a brief plan: +``` +1. [Step] → verify: [check] +2. [Step] → verify: [check] +3. [Step] → verify: [check] +``` + +Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.