メニュー
Make sure the project has a README that is short, on-topic, and covers the instructions someone actually needs — no fluff. Use when the user asks to check, write, or tighten the project's README.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/Slikon/agent-skills --skill readme-checkコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Build a mental model of an unfamiliar codebase — architecture, subsystems, and where to look when changing something. Use when the user is new to a repo, is picking up a project they didn't write, or asks how a codebase is structured or where something lives.
Explain what a PR or branch actually does before you review it — the mental model, the execution path, and what to question. Use when the user needs to understand a change they didn't write, or an agent just produced a large diff or PR.
Restate the last message in plain human language, with no jargon.
| name | readme-check |
| description | Make sure the project has a README that is short, on-topic, and covers the instructions someone actually needs — no fluff. Use when the user asks to check, write, or tighten the project's README. |
Ensure the current project has a README that earns its length: short, on-topic, every instruction someone needs to use the project, and no fluff.
Look for README.md at the repo root (resolve root with git rev-parse --show-toplevel, else the current directory). If none exists, create one.
Read enough of the repo to know what it is, how to install/set it up, how to run it, and how to use it. Draw from package manifests, entry points, scripts, config, and existing docs — don't guess.
A reader should be able to install, run, and use the project from the README alone. Cover only what serves that:
Then cut the fluff: marketing lines, restated headings, obvious filler, padding. Every section must carry an instruction or a fact the reader needs.
Completion criterion: someone new could install, run, and use the project from this README alone, and there is no line you could delete without losing an instruction or a needed fact.