Menü
Improve readiness criterion C1.1 (Codebase Accessibility) in the current project by creating or enhancing the agent context file (CLAUDE.md). Raises the fulfillment level by one step.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Assess the Agent Readiness level of the current project across all 11 criteria (C1.1–C8.2) and produce a structured report with the achieved level, per-criterion scores, gaps, and recommendations.
Verify readiness criterion C1.1 (Codebase Accessibility) in the current project. Reports fulfillment level 0–2.
Verify readiness criterion C2.1 (Setup Automation) in the current project. Reports fulfillment level 0–3.
Verify readiness criterion C3.1 (Architecture Depth) in the current project. Reports fulfillment level 0–3.
Verify readiness criterion C5.1 (Runnability) in the current project. Reports fulfillment level 0–2.
Verify readiness criterion C5.2 (Unit Test Coverage) in the current project. Reports fulfillment level 0–3.
| name | improve-c1-1 |
| description | Improve readiness criterion C1.1 (Codebase Accessibility) in the current project by creating or enhancing the agent context file (CLAUDE.md). Raises the fulfillment level by one step. |
| allowed-tools | Bash Read Write Edit |
Examine the project to understand its current state:
CLAUDE.md, AGENTS.md, or equivalent) and read their full content.README.md to assess its depth.Step 1 — Determine current level:
Step 2 — Implement the improvement:
If current level is 0 → raise to 1:
Create a README.md at the project root with at minimum:
If current level is 1 → raise to 2:
Create a CLAUDE.md at the project root. Base it on the evidence above (README content, detected language/framework, directory structure, build scripts). Include:
# CLAUDE.md
## Project Overview
[brief description of what this project does]
## Key Commands
[list the most important commands: build, test, run, lint — use the actual commands detected above]
## Project Structure
[describe the main directories and what lives in them]
## Coding Conventions
[list conventions: naming style, file organisation, patterns used — infer from the existing code structure]
## Important Notes
[any non-obvious constraints, environment variables required, external services, known gotchas]
Read enough of the actual codebase to write accurate, project-specific content. Do not write generic placeholder text.
If already at level 2: Report that C1.1 is already at its maximum level (2) and no improvement is needed.
Step 3 — Report: State what file was created or modified, what level it was at before, and what level it is now.