Best for
- Use when asked to assess, audit, or score the AI readiness of a repo.
github/awesome-copilot/skills/acreadiness-assess/SKILL.md
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
Decision brief
Use this skill whenever the user asks for an AI-readiness assessment, a readiness check, an audit, or wants to see how AI-ready their repository is.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/github/awesome-copilot --skill "skills/acreadiness-assess"Inspect the Agent Skill "acreadiness-assess" from https://github.com/github/awesome-copilot/blob/9933dcad5be5caeb288cebcd370eeeb2fc2f1685/skills/acreadiness-assess/SKILL.md at commit 9933dcad5be5caeb288cebcd370eeeb2fc2f1685. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
1. Confirm prerequisites. Node 20+ must be on PATH. If unsure, run node --version.
AgentRC also has a built-in HTML renderer (--visual / --output report.html) but its output is intentionally generic. This skill produces a tailored, opinionated dashboard via the custom agent — closer to a code review t…
Permission review
The documentation asks the agent to read local files, directories, or repositories.
This skill is the *Measure* step in AgentRC's **Measure → Generate → Maintain** loop. The result is a self-contained HTML dashboard the user can open with `file://` or commit to the repo.The documentation asks the agent to read local files, directories, or repositories.
**Run the readiness scan** in the repo root with structured output:The documentation asks the agent to run terminal commands or scripts.
npx -y github:microsoft/agentrc readiness --json [--policy <source>] [--per-area]Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 74/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 37,126 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Use this skill whenever the user asks for an AI-readiness assessment, a readiness check, an audit, or wants to see how AI-ready their repository is.
This skill is the Measure step in AgentRC's Measure → Generate → Maintain loop. The result is a self-contained HTML dashboard the user can open with file:// or commit to the repo.
Confirm prerequisites. Node 20+ must be on PATH. If unsure, run node --version.
Decide on a policy (optional but encouraged):
--policy <source>, capture it.agentrc.config.json for a policies array.acreadiness-policy skill.Run the readiness scan in the repo root with structured output:
npx -y github:microsoft/agentrc readiness --json [--policy <source>] [--per-area]
The CommandResult<T> JSON envelope is your input for the next step.
Hand off to the ai-readiness-reporter custom agent to interpret the JSON and produce reports/index.html. The agent renders via the bundled template report-template.html (shipped alongside this skill) so every report has an identical look & feel. The agent:
report-template.html and substitutes placeholders with real data.file://).Tell the user where the report lives (reports/index.html) and how to open it. Summarise in chat: maturity level, overall score, top three lowest pillars, and the single highest-leverage next action (almost always: run the acreadiness-generate-instructions skill).
--visual / --output report.html) but its output is intentionally generic. This skill produces a tailored, opinionated dashboard via the custom agent — closer to a code review than a metrics dump.agentrc readiness --fail-level <n> (1–5).reports/index.html.