REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
A self-improving skill for AI coding agents (Claude Code, Cursor, AGENTS.md): recognize a hard-won golden path in a session and harvest it into a reusable skill/rule for next time.
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/kulaxyz-self-learning-skills)在同一工作中把 AI 连到服务的 MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
同类工作,排序与 Skill 列表相同
| 本项 self-learning-skills | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 作者 | Kulaxyz | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub 星标 | 972 | 467,235 | 234,125 | 149,873 | 144,332 |
| 最近代码更新 | 2026年9月15日 | 2026年11月18日 | 2026年4月20日 | 2026年11月18日 | 2026年11月18日 |
| 许可证 | MIT | MIT | – | Apache-2.0 | MIT |
Kulaxyz 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
Claude CodeCodexCursorGemini CLIOpenCode
依据开发者 README 和 repo 中的文件夹
GitHub account Kulaxyz (person), 7 years old
★ 972 stars · code last changed 2026年9月15日
No, plain text files the AI reads and follows
No scripts, so it does not go online by itself
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 1304fce (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
Uploading to claude.ai would fail: the description is over 200 characters (954). Use "Let the AI install it" instead
复制这句话,粘贴到 Claude Code 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
重新打开 Claude Code,输入 /self-learning,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
正在检查命令 · 通过后才会显示复制按钮
摘自开发者 README,会下载并运行开发者的代码
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
ChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
把 self-learning 文件夹放到 ~/.agents/skills/self-learning
~ 是你的主文件夹($HOME)
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
复制这句话,粘贴到 Cursor 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
在 Cursor 的 Agent 聊天中输入 / 并选择 self-learning
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
显示前 8,000 个字符 · 在 GitHub 打开完整文件
---
name: self-learning
description: >
Capture a hard-won "golden path" from the current session as a reusable Agent
Skill, so future sessions start already knowing it. Use it (1) right after
non-trivial debugging, after working out a multi-step operational workflow, or
after rediscovering project facts you didn't know up front — e.g. how to reach
the dev/prod database, where credentials and env vars live, how to deploy, run
migrations, or verify a change live; and (2) whenever the user says "remember
this", "save this as a skill", "make a skill for this", "don't make me
re-explain this next time", or otherwise wants a workflow preserved across
sessions. Proactively recognize the moment even when unprompted: if a task took
several attempts before it worked, used non-obvious tooling, or is likely to
recur, harvest it without asking first. Delegates to a subagent when your tool
supports one, or works inline, to extract the proven procedure into a new
project-local or global skill.
license: MIT
metadata:
author: kulaxyz
version: "1.0"
---
# Self-learning: harvest golden paths into skills
This skill turns something you just figured out the hard way into a reusable
Agent Skill, so the next session — yours or a teammate's — starts already
knowing the proven route instead of rediscovering it from scratch.
It is a *meta-skill*: it doesn't do the work, it captures **how** work got done.
It's tool-neutral — it works with any agent that reads the Agent Skills format
(e.g. Claude Code and Codex, which both load `SKILL.md` skills natively). Where a
step differs by tool, the generic version comes first and any tool-specific
detail is only an example.
## Recognize the moment
Watch for these signals during normal work. Any one of them is a cue to harvest:
- A task only worked **after several attempts**, wrong turns, or a correction
from the user. The successful path is worth more than the failures around it.
- You discovered **project-specific facts the agent didn't know up front**:
where creds/env vars live, which selector or backend talks to a service, a
non-obvious command, a required sequence, a gotcha that defies the obvious
assumption.
- It's an **operational workflow likely to recur**: reach the dev/prod DB,
deploy, run migrations, seed data, verify a change live, run one specific
test path, rotate a key, tail the right logs.
- The user **signals it explicitly**: "remember this", "save this as a skill",
"don't make me re-explain this next time".
**Act on the cue immediately — don't ask for permission first**, whether the
user requested it or you noticed it yourself. Harvest the skill, then tell the
user what you captured and where (step 5). They can always edit or delete it.
### Skill, memory, or skip?
Not every lesson deserves a whole skill — triage first, so you don't bloat the
skills list with one-liners:
- **A multi-step, reusable procedure or workflow** (how to deploy, reach the DB,
run the migration dance, verify live) → harvest it as a **skill** using the
procedure below.
- **A single standalone fact or one-line correction** (an env var name, a path,
one gotcha) → if your harness has a lightweight memory/notes facility (e.g. a
`MEMORY.md` index), record it **there** instead; a whole skill is overkill for
a one-liner. With no such facility, make a small skill.
- **A genuinely one-off thing** unlikely to recur → skip it.
When you do harvest, capture the **failures too**, not just the win: the
approaches you ruled out and *why* often save more time next session than the
golden path itself.
### Promotion rule: don't enshrine guesses
A skill is authoritative — the next session trusts it without re-deriving it —
so hold promotion to a high bar. Only write a skill when **all three** hold:
1. **A passing check.** The path was actually verified — a test passed, the
command exited clean, the repro reproduced, the build went green. Record what
the check was. "Seemed to work" is not a passing check.
2. **A named failure pattern.** You can name the failure this path avoids or
diagnoses (e.g. "stale build cache → phantom type errors"), not a vague
"sometimes it breaks".
3. **At least one ruled-out dead-end.** A concrete approach you tried and
eliminated, with the reason.
If any is missing, it isn't a skill yet — leave a tentative note in memory
(marked unverified) or skip it. This keeps confident guesses out of the skill
set.
## Harvest procedure
- [ ] 1. **Apply the promotion rule** (above). Passing check + named failure
pattern + one ruled-out dead-end — or it isn't a skill: note it in memory
or skip. Don't proceed on a confident guess.
- [ ] 2. **Choose scope and name yourself** using the heuristics below — don't
stop to ask. Default to project scope; pick a clear, specific `name`.
- [ ] 3. **Dedupe.** Look for an existing skill to UPDATE rather than duplicate.
List your agent's skills directories — the project one and the user-level
one (e.g. Claude Code `.claude/skills` + `~/.claude/skills`, Codex
`.codex/skills` + `~/.codex/skills`, or your tool's equivalent). Also
glance at any memory/notes index — a fact already there may just need a
pointer.
- [ ] 4. **Distill the golden path from THIS conversation** before delegating —
while it's fresh in your head: the exact working commands, file paths, env
var names, the required order, and (just as important) the dead-ends to
avoid. This is the raw material for the write.
- [ ] 5. **Delegate the write** to a subagent that inherits this conversation if
your tool supports one, or do it inline otherwise — see below. The
conversation is the only place the golden path lives, so whoever writes it
must have that context.
- [ ] 6. When the write is done, **relay the new skill's path** to the user
and, in one line, what it captured.
### Scope: project vs global
- **Project** (the repo's skills directory — e.g. `.claude/skills/`,
`.codex/skills/`): the path is specific to THIS codebase — its env vars, its
build/release steps, its schema, its quirks. Most harvested operational skills
are project-scoped, and they ship to the team via git.
- **Global** (your user-level skills directory — e.g. `~/.claude/skills/`,
`~/.codex/skills/`): the path generalizes across projects — a personal tool, a
cross-repo habit, or a workflow tied to your machine rather than to one repo.
When unsure, prefer **project** — an over-shared global skill triggers in repos
where its commands don't apply.
## Delegate the write (subagent, or inline)
Whoever writes the skill needs THIS conversation's context — it's the only place
the golden path lives. Two equally valid ways to run it:
- **Inline** — do the steps yourself in the main loop. Always works.
- **Subagent** — if your tool can delegate to a subagent that **inherits this
conversation**, use it to keep the harvesting work out of your main context.
(Claude Code: a skill with `context: fork`. Codex and others spawn subagents
their own way.) Don't hand it to a *fresh* agent with no context — it would
start blank with nothing to extract.
Either way it over-reaches by default, so box it in tightly. Follow this brief
(fill in the bracketed parts) — hand it to the subagent, or work through it
yourself inline:
> You are harvesting a skill. Your ONLY job is to write a new Agent Skill
> capturing the golden path we just worked out in this conversation:
> **[one-line description of the workflow]**.
>
> Hard rules:
> - Write ONLY under `[skills dir]/[skill-name]/`. Do NOT modify project
> source, run builds, install anything, or resume the original task.
> - First read `[this-skill-dir]/references/skill-authoring.md` and
> `[this-skill-dir]/assets/SKILL.template.md`, then author `SKILL.md` to that
> spec, plus any `references/` or `assets/` files the procedure warrants.
> - Capture the PROCEDURE — commands, pa提问、分享技巧或报告无法使用。按“有帮助”数量排序。