メニュー
Run the full repository compatibility pass: scanner score, startup path, validation loop, and docs reliability.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/cursor/plugins --skill check-agent-compatibilityコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | check-agent-compatibility |
| description | Run the full repository compatibility pass: scanner score, startup path, validation loop, and docs reliability. |
Use when the user wants the full compatibility pass for a repo.
compatibility-scan-review to run the CLI and capture the raw repository score and main issues.startup-review to verify whether the repo can actually be booted by an agent.validation-review to check whether an agent can verify a small change without an unnecessarily heavy loop.docs-reliability-review to see whether the documented setup and run paths reliably match reality.Startup Compatibility ScoreValidation Loop ScoreDocs Reliability ScoreAgent Compatibility Score as:
round((deterministic_score * 0.7) + (workflow_score * 0.3))When scoring internally, use specific non-round workflow scores for the behavioral checks rather than coarse round buckets. If startup, validation, or docs mostly work, treat them as good-with-friction rather than defaulting to the mid-60s. Do not create a low workflow score just because logs are noisy or the error text is rough.
Respond in markdown, but keep it minimal. Do not use fenced code blocks.
Show only one score, as a level-two heading: ## Agent Compatibility Score: N/100. Do not show how it was computed, including weights, formula, deterministic score, workflow score, per-check scores, or arithmetic, unless the user explicitly asks for a breakdown.
Then a flat, prioritized list labeled Top fixes with one issue per line, each line starting with - .
If the deterministic scanner cannot be run because of tool environment issues, say that separately and do not treat it as a repo defect or penalize the repo. Fold deterministic and behavioral findings into that one list instead of separate sections. Focus on the fixes that would most improve real agent workflows. Do not include a separate summary unless the user asks for more detail.
Example shape:
Top fixes