Agent skill

Agent Readiness Report

Evaluate how well a codebase supports autonomous AI-assisted development.

Install Agent Readiness Report

skills CLI

$ npx skills add OpenHands/extensions --skill agent-readiness-report -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install OpenHands/extensions agent-readiness-report --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/onboarding/skills/agent-readiness-report .claude/skills/agent-readiness-report && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "agent-readiness-report" agent skill from https://github.com/OpenHands/extensions/tree/main/plugins/onboarding/skills/agent-readiness-report into .claude/skills/agent-readiness-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-readiness-report", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/OpenHands/extensions/tree/main/plugins/onboarding/skills/agent-readiness-report

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add OpenHands/extensions --skill agent-readiness-report -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install OpenHands/extensions agent-readiness-report --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/onboarding/skills/agent-readiness-report .agents/skills/agent-readiness-report && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "agent-readiness-report" agent skill from https://github.com/OpenHands/extensions/tree/main/plugins/onboarding/skills/agent-readiness-report into .agents/skills/agent-readiness-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-readiness-report", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add OpenHands/extensions --skill agent-readiness-report -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install OpenHands/extensions agent-readiness-report --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/onboarding/skills/agent-readiness-report .cursor/skills/agent-readiness-report && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "agent-readiness-report" agent skill from https://github.com/OpenHands/extensions/tree/main/plugins/onboarding/skills/agent-readiness-report into .cursor/skills/agent-readiness-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-readiness-report", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/OpenHands/extensions.git --path plugins/onboarding/skills/agent-readiness-report

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add OpenHands/extensions --skill agent-readiness-report -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install OpenHands/extensions agent-readiness-report --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/onboarding/skills/agent-readiness-report .gemini/skills/agent-readiness-report && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "agent-readiness-report" agent skill from https://github.com/OpenHands/extensions/tree/main/plugins/onboarding/skills/agent-readiness-report into .gemini/skills/agent-readiness-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-readiness-report", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install OpenHands/extensions agent-readiness-report

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add OpenHands/extensions --skill agent-readiness-report -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/onboarding/skills/agent-readiness-report .github/skills/agent-readiness-report && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "agent-readiness-report" agent skill from https://github.com/OpenHands/extensions/tree/main/plugins/onboarding/skills/agent-readiness-report into .github/skills/agent-readiness-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-readiness-report", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add OpenHands/extensions --skill agent-readiness-report -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install OpenHands/extensions agent-readiness-report --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/onboarding/skills/agent-readiness-report .opencode/skills/agent-readiness-report && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "agent-readiness-report" agent skill from https://github.com/OpenHands/extensions/tree/main/plugins/onboarding/skills/agent-readiness-report into .opencode/skills/agent-readiness-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-readiness-report", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: agent-readiness-report
GitHub stars: 157
Token cost: ~1.1k tokens
SKILL.md length: 452 words
Files: 8 (incl. scripts, references)
Skills in repo: 78
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Evaluate how well a codebase supports autonomous AI-assisted development.

Works in 3 steps: Run the scanner scripts → Evaluate each feature → Write the report
Users want to assess how agent-ready a repository is
SKILL.md covers What this does, Five Pillars, How to run and What makes these features useful
Runs Shell scripts from its folder; calls bash

What it does

Agent Readiness Report is an agent skill from OpenHands/extensions. Evaluate how well a codebase supports autonomous AI-assisted development. Analyzes repositories across five pillars (Agent Instructions, Feedback Loops, Workflows & Automation, Policy & Governance, Build & Dev Environment) covering 74 features. Use when users want to assess how agent-ready a repository is.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts and reference files (for example `README.md`, `references/criteria.md` and `scripts/scan_agent_instructions.sh`).

It sits in Agent Workflows, covering Agent instruction files. The repository describes itself as: Public registry for OpenHands extensions. The licence is MIT.

When your agent uses it

Users want to assess how agent-ready a repository is
Tasks that involve Agent instruction files

Example prompts

“/agent-readiness-report”

Requirements

A Bash shell

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Run the scanner scripts
Evaluate each feature
Write the report

What it can do on your machine

Read from SKILL.md and the folder at commit d008b81. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 5 files in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
- bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Agent Readiness Report loads about 1.1k tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 452 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~83
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from OpenHands/extensions at commit d008b81, republished under its MIT licence (© OpenHands). 452 words, ~1,112 tokens.

Download SKILL.mdSave it as .claude/skills/agent-readiness-report/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.

name: agent-readiness-report
description: Evaluate how well a codebase supports autonomous AI-assisted development. Analyzes repositories across five pillars (Agent Instructions, Feedback Loops, Workflows & Automation, Policy & Governance, Build & Dev Environment) covering 74 features. Use when users want to assess how agent-ready a repository is.
triggers: agent-readiness-report, readiness report

Agent Readiness Report

Evaluate how well a repository supports autonomous AI-assisted development.

What this does

Assess a codebase across five pillars that determine whether an AI agent can work effectively in a repository. The output is a structured report identifying what's present and what's missing.

Five Pillars

Pillar	Question	Features
Agent Instructions	Does the agent know what to do?	18
Feedback Loops	Does the agent know if it's right?	16
Workflows & Automation	Does the process support agent work?	15
Policy & Governance	Does the agent know the rules?	13
Build & Dev Environment	Can the agent build and run the project?	12

74 features total. See references/criteria.md for the full list with descriptions and evidence examples.

How to run

Step 1: Run the scanner scripts

Five shell scripts gather filesystem signals — file existence, config patterns, directory structures. They surface what's present so you don't have to run dozens of find commands manually.

bash

bash scripts/scan_agent_instructions.sh /path/to/repo
bash scripts/scan_feedback_loops.sh /path/to/repo
bash scripts/scan_workflows.sh /path/to/repo
bash scripts/scan_policy.sh /path/to/repo
bash scripts/scan_build_env.sh /path/to/repo

Or scan all five at once:

bash

for s in scripts/scan_*.sh; do bash "$s" /path/to/repo; echo; done

On Windows, run these .sh helpers from Git Bash or WSL and pass a path that environment can read. Native PowerShell cannot execute the shell scripts directly.

Important: The scripts are helpers, not scorers. They find files and patterns but do not evaluate quality. Many features require judgment that only reading the actual files can provide — for example, whether a README includes real build commands or just badges, whether inline documentation is systematic or scattered, whether an AI usage policy has meaningful boundaries.

Show full SKILL.md (213 more words)Show less

Step 2: Evaluate each feature

Walk through references/criteria.md pillar by pillar. For each feature:

Check the scanner output for relevant signals
For features the scanner can't fully evaluate, inspect the files yourself
Mark each feature: ✓ (present), ✗ (missing), or — (not applicable)

Features that require judgment (not fully covered by scanners):

Does the README actually contain build/run/test commands? (not just that it exists)
Is inline documentation systematic across the public API?
Are examples actually runnable?
Does the contributing guide include code standards?
Is there a meaningful AI usage policy?
Is the architecture documentation current?
Are tests documented well enough for an agent to run them?

Step 3: Write the report

Structure the output as:

# Agent Readiness Report: {repo name}

## Summary
- Features present: X / 74
- Strongest pillar: {pillar}
- Weakest pillar: {pillar}

## Pillar 1 · Agent Instructions (X / 18)
✓ Agent instruction file — AGENTS.md at root
✓ AI IDE configuration — .cursor/rules/ with 3 rule files
✗ Multi-model support — only Cursor configured
...

## Pillar 2 · Feedback Loops (X / 16)
...

## Pillar 3 · Workflows & Automation (X / 15)
...

## Pillar 4 · Policy & Governance (X / 13)
...

## Pillar 5 · Build & Dev Environment (X / 12)
...

For each passing feature, briefly note what evidence you found. For each failing feature, note what's missing.

What makes these features useful

Every feature answers: if this is missing, what goes wrong for the AI agent? Features like "agent instruction file" and "tool server configuration" exist because agents need them. Features like "linter" and "CI pipeline" exist because agents need fast, clear feedback on whether their changes are correct — not because they're general best practices.

The criteria were derived from analysis of 123 real repositories across five AI-readiness categories, then filtered for features that actually affect agent effectiveness.

Files

SKILL.md and 7 other files (scripts, references) in plugins/onboarding/skills/agent-readiness-report of OpenHands/extensions.

SKILL.md
README.md
references/criteria.md
scripts/scan_agent_instructions.sh
scripts/scan_build_env.sh
scripts/scan_feedback_loops.sh
scripts/scan_policy.sh
scripts/scan_workflows.sh

Open the folder on GitHubat commit d008b81

Compare with similar skills

Agent Readiness Report next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Agent Readiness Report compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Agent Readiness Report this skillOpenHands/extensions	157	—	~1.1k	Automated safety check: Pass	MIT	yesterday
Using Agent Skillsaddyosmani/agent-skills	102k	4 repos	~2.4k	Automated safety check: Pass	MIT	4 days ago
Claude ReflectBayramAnnakov/claude-reflect	1.7k	2 repos	~627	Automated safety check: Pass	MIT	4 days ago
Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills	21k	—	~1.9k	Automated safety check: Pass	MIT	6 days ago
Task Observerrebelytics/one-skill-to-rule-them-all	3.2k	1 repos	~12k	Automated safety check: Pass	CC-BY-4.0	5 days ago
Writing For Agentsbestofjs/bestofjs	3.1k	17 repos	~2.7k	Automated safety check: Pass	MIT	3 days ago

Similar skills

Using Agent Skills
addyosmani/agent-skills
Meta-skill for choosing which workflow skill fits the task at hand, plus always-on habits: surface assumptions, stop on confusion, push back, keep it simple and stay in scope.
102k GitHub starsUsed in 4 repos~2.4k tokens
Agent WorkflowsAuto-check passed
Claude Reflect
BayramAnnakov/claude-reflect
Self-learning system that captures corrections during sessions and reminds users to run /reflect to update CLAUDE.md.
1.7k GitHub starsUsed in 2 repos~627 tokens
Agent WorkflowsAuto-check passed
Neat-Freak Knowledge Closeout
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
21k GitHub stars~1.9k tokensUpdated 6 days ago
Agent WorkflowsAuto-check passed
Task Observer
rebelytics/one-skill-to-rule-them-all
Monitors task execution for skill improvement opportunities.
3.2k GitHub starsUsed in 1 repo~12k tokens
Agent WorkflowsAuto-check passed
Writing For Agents
bestofjs/bestofjs
Writing documents for agents. An agent skill from bestofjs/bestofjs.
3.1k GitHub starsUsed in 17 repos~2.7k tokens
Agent WorkflowsAuto-check passed
SkillOpt Sleep Cycle
microsoft/SkillOpt
Official
Runs an on-demand or nightly sleep cycle that reviews past Claude Code sessions and proposes validated updates to CLAUDE.md and skills.
18k GitHub stars~2.3k tokensUpdated yesterday
Agent WorkflowsAuto-check passed

More from OpenHands/extensions

All 78 skills in this repo

Discord
OpenHands/extensions
Build and automate Discord integrations (bots, webhooks, slash commands, and REST API workflows).
157 GitHub stars~1.1k tokensUpdated yesterday
Auto-check passed
GitHub
OpenHands/extensions
Interact with GitHub repositories, pull requests, issues, and workflows using the GITHUBTOKEN environment variable and GitHub CLI.
157 GitHub stars~1.7k tokensUpdated yesterday
Auto-check passed
GitHub Issue To PR
OpenHands/extensions
Create an automation that implements GitHub issues when a configurable trigger label is applied.
157 GitHub stars~4.4k tokensUpdated yesterday
Auto-check passed
GitHub Repo Monitor
OpenHands/extensions
This skill should be used when the user asks to "monitor a GitHub repository", "watch GitHub for issues or PRs", "respond to @OpenHands mentions on GitHub", "set up an OpenHands GitHub integration"…
157 GitHub stars~3.1k tokensUpdated yesterday
Auto-check passed
GitLab Issue To Mr
OpenHands/extensions
Create an automation that implements GitLab issues when a configurable trigger label is applied.
157 GitHub stars~4.9k tokensUpdated yesterday
Auto-check passed
Jira Issue To PR
OpenHands/extensions
This skill should be used when the user asks to "set up a Jira automation to create pull requests", "poll Jira for create-pr issues", "automatically create GitHub PRs from Jira tickets", "deploy a…
157 GitHub stars~4.1k tokensUpdated yesterday
Auto-check passed

Questions about Agent Readiness Report

What does Agent Readiness Report do?

Evaluate how well a codebase supports autonomous AI-assisted development. Agent Readiness Report is an agent skill from OpenHands/extensions. Evaluate how well a codebase supports autonomous AI-assisted development.

When should I use Agent Readiness Report?

Agent Readiness Report fits situations like: users want to assess how agent-ready a repository is; tasks that involve Agent instruction files.

How do I install Agent Readiness Report in Claude Code?

Run `npx skills add OpenHands/extensions --skill agent-readiness-report -a claude-code`. Or copy the skill folder (plugins/onboarding/skills/agent-readiness-report in OpenHands/extensions) into .claude/skills/agent-readiness-report in your project. Claude Code loads it when a task matches its description.

How do I install Agent Readiness Report in Codex?

Run `npx skills add OpenHands/extensions --skill agent-readiness-report -a codex`. Or copy the skill folder (plugins/onboarding/skills/agent-readiness-report in OpenHands/extensions) into .agents/skills/agent-readiness-report in your project. Codex loads it when a task matches its description.

Can I use Agent Readiness Report in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OpenHands/extensions --skill agent-readiness-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-readiness-report, .gemini/skills/agent-readiness-report, .github/skills/agent-readiness-report and .opencode/skills/agent-readiness-report in your project.

What does Agent Readiness Report need to run?

Going by SKILL.md and its folder, Agent Readiness Report needs a shell for the scripts in its folder and the command-line tools its instructions call (bash). Our summary lists: A Bash shell.

Does Agent Readiness Report access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Agent Readiness Report safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Agent Readiness Report use?

Agent Readiness Report is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Agent Readiness Report use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8 tokens, read only when the agent opens those files.

What are the alternatives to Agent Readiness Report?

Skills that share tags, products or a category with Agent Readiness Report: Using Agent Skills (addyosmani/agent-skills, 102k stars), Claude Reflect (BayramAnnakov/claude-reflect, 1.7k stars), Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars) and Task Observer (rebelytics/one-skill-to-rule-them-all, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agent Readiness Report?

OpenHands (a GitHub organization) maintains it in OpenHands/extensions, which has 157 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 6, 2026.

Source: OpenHands/extensions on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Agent Readiness Report

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Agent Readiness Report

What this does

Five Pillars

How to run

Step 1: Run the scanner scripts

Step 2: Evaluate each feature

Step 3: Write the report

What makes these features useful

Files

Compare with similar skills

Similar skills

More from OpenHands/extensions

Related

Questions about Agent Readiness Report