REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Agent Skill that analyzes your repo and generates the AI-ready configuration coding agents need — AGENTS.md, copilot-instructions, CI, issue templates, and more. Works in Claude Code, GitHub Copilot, Codex, and Cursor.
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/johnpapa-ai-ready)在同一工作中把 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 列表相同
| 本项 ai-ready | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 作者 | johnpapa | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub 星标 | 239 | 467,235 | 234,125 | 149,873 | 144,332 |
| 最近代码更新 | 2026年9月28日 | 2026年11月18日 | 2026年4月20日 | 2026年11月18日 | 2026年11月18日 |
| 许可证 | MIT | MIT | – | Apache-2.0 | MIT |
johnpapa 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
Claude CodeCodexCursorGitHub Copilot
依据开发者 README 和 repo 中的文件夹
GitHub account johnpapa (person), 15 years old
★ 239 stars, few users so far · code last changed 2026年9月28日
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 c251292 (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 (473). 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,输入 /ai-ready,或直接提出相关任务,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
把 ai-ready 文件夹放到 ~/.agents/skills/ai-ready
~ 是你的主文件夹($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 聊天中输入 / 并选择 ai-ready
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: ai-ready
license: MIT
metadata:
version: "1.4.0"
description: "**ANALYSIS SKILL** — Analyze any repository and generate AI-ready configuration — a canonical AGENTS.md, thin per-tool pointer files, skills, CI workflows, issue templates. WHEN: \"make this repo ai-ready\", \"set up AI config\", \"add copilot instructions\", \"prepare this repo for AI contributions\", \"generate AGENTS.md\". INVOKES: glob, grep, view, create, edit for repo analysis and file generation. FOR SINGLE OPERATIONS: use create/edit directly for individual config files."
---
# AI-Ready Repo Skill
## Persona
Adopt the perspective of an experienced repo maintainer. Prioritize what **reduces review burden and contributor friction**. Every file you generate should earn its place — generic boilerplate creates noise.
---
Follow these steps in order to analyze the current repository and generate all missing AI-ready configuration assets.
**First run vs. re-run:** On the first run, most assets will be missing — the skill creates them. On re-runs, it **audits** existing assets against the current codebase, checking for drift, stale content, and new conventions from recent PR reviews.
**Skipping assets:** If the user's prompt mentions skipping specific assets, respect those exclusions. Still run the full analysis, but skip generation for the excluded assets.
**Report-only mode:** If the user asks for a report without generating files (e.g., "how ai-ready is this repo?", "score this repo"), run the full analysis (Steps 0–1) and display the report (Step 11) — but skip all generation steps (Steps 2–10).
### The 11 tracked assets
Assets are grouped into three categories. Count assets with **Nailed It** status for the score.
**🤖 AI Context** — what AI agents read to understand your repo
| # | Asset | Generated in |
|---|-------|-------------|
| 1 | `AGENTS.md` | Step 2 |
| 2 | Per-tool pointer files (`.github/copilot-instructions.md`, `CLAUDE.md`, …) | Step 3 |
| 3 | Maintenance matrix (in `AGENTS.md`) | Step 2 |
| 4 | Reviewer agents (`.github/agents/`) | Step 4c |
| 5 | Starter skill (`.github/skills/`) | Step 4d |
| 6 | Security skill (`.github/skills/`, when there is surface) | Step 4e |
**🔧 Dev Workflow** — what keeps PRs clean and contributors on track
| # | Asset | Generated in |
|---|-------|-------------|
| 7 | CI workflow (`.github/workflows/ci.yml`) | Step 5 |
| 8 | Issue templates (`.github/ISSUE_TEMPLATE/`) | Step 6 |
| 9 | PR template (`.github/PULL_REQUEST_TEMPLATE.md`) | Step 6 |
**📖 Onboarding** — what helps new contributors get started
| # | Asset | Generated in |
|---|-------|-------------|
| 10 | Changelog (`CHANGELOG.md`) | Step 9 |
| 11 | Documentation (or explicit "not needed" note) | Step 10 |
**Scoring:** 🟩 Nailed It (counted) · 🟨 Could Be Better (not counted) · ⬜ Missing (not counted).
Medals, the two prerequisites that cap them, and what the score may never claim are in
[references/report-template.md](references/report-template.md) — read it in Step 11.
---
## Step 0 — Detect GitHub context automatically
The skill is GitHub-native — it discovers everything from GitHub's tools.
### 0a. Identify the repo
Run `git remote -v` to extract the GitHub `owner/repo`. If not GitHub, fall back to local-only analysis.
### 0b–0d. Fetch metadata, mine PR reviews, check community health
Use GitHub MCP tools or `gh` CLI to auto-discover repo metadata, PR review patterns, and community health gaps. See [references/github-discovery.md](references/github-discovery.md) for the full API table, PR mining technique, and health gap mapping.
Repeated reviewer feedback — from humans *and* from review agents — becomes conventions in `AGENTS.md`. Weight recent patterns more heavily, and flag an abandoned one rather than resurrecting it as a current rule.
---
## Step 1 — Analyze the codebase
GitHub context tells you *what* the repo is. Local analysis tells you *how* it works. Use glob, grep, and view combined with GitHub context from Step 0.
### 1a. Detect languages, frameworks, and repo type
Find manifest files and extract details. See [references/detection-tables.md](references/detection-tables.md) for the full manifest table, VS Code extension detection, multi-app collections, demo app patterns, and course/tutorial repo detection.
**Course repos** (3+ signals: numbered folders, lesson keywords, no primary app) adapt Steps 2–5. See detection-tables.md for the full signal list and step adaptations.
### 1b–1c. Detect test setup and CI
**Community workflows (stale, welcome, labeler) are valid automation, not missing CI.** Do not report a repo
as having no CI because its only workflow is a stale-bot.
### 1d. Check existing AI configuration
Check for: `AGENTS.md`, `.github/copilot-instructions.md`, `CLAUDE.md`, `.cursorrules`, `.cursor/rules/`,
`.github/skills/`, `.github/agents/`, `.github/extensions/`, `.devcontainer/`.
**Two failure modes, and the second is the common one.** `AGENTS.md` is canonical; every other instruction
file should be a short pointer to it.
1. **Duplication** — a tool file restates conventions that also live in `AGENTS.md`. Flag as
**Could Be Better**: duplicated guidance drifts silently, and then two agents work from two versions of the
same standard.
2. **Split** — each file holds *different* content and neither is complete. This is what most repos actually
have, and it is worse than duplication because nothing looks wrong. A tool reading only `AGENTS.md` never
sees the conventions; a tool reading only the Copilot file never sees the build and test commands.
For a split, list specifically **which sections exist in the tool file but not in `AGENTS.md`** — those are
what Step 2 needs to absorb. Do not rewrite the tool file here; propose the move and let the user decide.
### 1e–1h. Check configuration, changelog, docs, and structure
Detect `CODEOWNERS`, `dependabot.yml`, issue and PR templates, `LICENSE`, a README Contributing section,
changelog health, and docs setup. Two judgments that are not obvious: a changelog may live in a docs site
rather than `CHANGELOG.md`, so **follow pointer files before reporting one missing**; and freshness is measured
against the latest git tag, not the file's date.
### 1i. Compile findings
Produce a structured findings table combining GitHub context and codebase analysis with file-path evidence. See [references/detection-tables.md](references/detection-tables.md) for the full findings table template.
List which of the 11 assets are missing. For existing assets, compare against analysis and flag drift as "Could Be Better."
### 1j. Detect monorepo areas
If workspace config found, list areas with name, path glob, and primary stack. For large library monorepos, map cross-package dependencies. See [references/detection-tables.md](references/detection-tables.md) for details.
---
## Step 2 — Generate AGENTS.md
If missing, create `AGENTS.md` at the repo root. If it exists, compare against analysis and flag drift.
`AGENTS.md` is the **canonical entry point** for how this repo works — the one file every tool reads, and the
one place a given convention is stated. That is not the same as putting everything in it. Read
[references/agents-md.md](references/agents-md.md) before generating: what belongs, what does not, and where
the rest goes.
Two rules govern everything below.
**1. The discoverability test.** Before writing any section, ask: *can the agent find this by reading the
code?* If yes, do not write it down. `AGENTS.md` is loaded before **every** task, so every line is paid for on
every run and competes for attention with the actual work. Directory trees, tech-stack inventories and
architecture summaries all fail this test — generate them only for what is genuinely **surprising** about this
repo, and skip them entirely when the layout is conventional.
**2. Put it at the narrowest scope that fits.** Needed on every task → root `AGENTS.md`. Needed only in one
area → a **n提问、分享技巧或报告无法使用。按“有帮助”数量排序。