Skill Market

acreadiness assess

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.

GitHub
githubcommunity
0.0
0 installs39.2K GitHub starsby github

Skill Introduction

Overview
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.

Core value

Turns reusable Development know-how into an installable skill, helping users complete github, community work faster.

Target users

  • Developers, testers, and maintainers who handle Development tasks in Focus Code.
  • Teams that already trust workflows or content from github.
  • Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

  • Read the skill content first to confirm required inputs, expected outputs, and dependencies.
  • Try it on a small task before relying on it for critical work.
  • Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
  • For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

  • Tasks related to github, community that need a reusable execution flow.
  • Converting a community repo, team convention, or personal workflow into day-to-day assistance.
  • Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

  • Results depend on the quality of the original skill content and may need human correction.
  • It does not replace code review, tests, security review, or professional judgment.
  • External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

  • Structured around Development, making it easier to discover and reuse than loose prompt snippets.
  • Marked as GitHub, which helps users judge trust and maintenance expectations.
  • Keeps the original source link available for repository, documentation, or discussion follow-up.
  • Tagged with github, community, so it can be filtered by concrete task intent.

Install and use

Install
Copy Install Command
focus install acreadiness-assess-cb8692
View source

Detail Preview

SKILL.md

Primary filemarkdown4 KB

name: acreadiness-assess description: '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.' argument-hint: "[--policy <path-or-pkg>] [--per-area] β€” e.g. /acreadiness-assess, /acreadiness-assess --policy ./policies/strict.json"

/acreadiness-assess β€” AI-readiness assessment

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.

Steps

  1. Confirm prerequisites. Node 20+ must be on PATH. If unsure, run node --version.

  2. Decide on a policy (optional but encouraged):

    • If the user provided --policy <source>, capture it.
    • Otherwise check agentrc.config.json for a policies array.
    • If neither, run with no policy (built-in defaults).
    • For a primer on policies, suggest the acreadiness-policy skill.
  3. 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.

  4. 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:

    • Reads the bundled report-template.html and substitutes placeholders with real data.
    • Inlines all CSS, ships a single static file (works under file://).
    • Renders maturity level, overall score, grade, pass-rate vs threshold.
    • Breaks down all 9 pillars across Repo Health (8) and AI Setup (1) with what it measures, why it matters for AI, current state, and a specific recommendation.
    • Tags every pillar with an AI relevance badge (High / Medium / Low).
    • Surfaces Extras separately (they never affect the score).
    • Shows the Active Policy including any disabled/overridden criteria and thresholds.
    • Produces a Prioritised Remediation Plan (πŸ”΄ Fix First / 🟑 Fix Next / πŸ”΅ Plan).
    • Embeds the raw AgentRC JSON for reuse.
  5. 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).

Notes

  • 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 than a metrics dump.
  • For CI gating, recommend agentrc readiness --fail-level <n> (1–5).
  • The skill never modifies repository files other than creating reports/index.html.

Reviews

Overall rating

0.0
0.0

0 comments

No reviews yet