Index of every page on this site: llms.txt
All skills
github avatar

/acreadiness-policy

@f10fdb8 official
by githubgithub/awesome-copilot41k stars
5,399
Run it yourself

Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/acreadiness-policy

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈92 tokens for metadata: the name and description. ≈815 when used: this file.

Description uses 4.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈367 characters, or 4.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

/acreadiness-policy — AgentRC policies

Use this skill when the user asks about policies, strict mode, custom scoring, disabling checks, org standards, or CI gating of readiness.

A policy is a small JSON file with three optional sections — criteria, extras, thresholds — that customise how AgentRC scores readiness.

Built-in examples

AgentRC ships with three example policies in examples/policies/:

Policy What it does
strict.json 100% pass rate, raises impact on key criteria
ai-only.json Disables all repo-health checks, focuses on AI tooling
repo-health-only.json Disables AI checks, focuses on traditional quality

Recommend these as starting points before writing a custom policy.

Policy schema

{
  "name": "my-policy",
  "criteria": {
    "disable":  ["env-example", "observability", "dependabot"],
    "override": {
      "readme":      { "impact": "high", "level": 2 },
      "lint-config": { "title": "Linter required" }
    }
  },
  "extras": {
    "disable": ["pre-commit"]
  },
  "thresholds": {
    "passRate": 0.9
  }
}

Impact weights

Impact Weight
critical 5
high 4
medium 3
low 2
info 0

Score = 1 − (deductions / max possible weight). Grades: A ≥ 0.9, B ≥ 0.8, C ≥ 0.7, D ≥ 0.6, F < 0.6.

Sub-commands

show

List policies currently in effect (from agentrc.config.json policies array, or none).

new <name>

Scaffold policies/<name>.json with sensible defaults. Walk the user through:

  1. What to disable — irrelevant pillars or extras for their stack (e.g. disable observability for a static site).
  2. What to raise — override impact to high or critical for must-haves (e.g. readme, codeowners).
  3. Pass-rate threshold — typical org baselines: 0.7 (lenient), 0.85 (standard), 1.0 (strict).
  4. Reference the policy from agentrc.config.json:
    { "policies": ["./policies/<name>.json"] }

apply <path-or-pkg>

Run agentrc readiness --json --policy <source> and re-render the report by handing off to the assess skill / ai-readiness-reporter agent. Supports chaining:

npx -y github:microsoft/agentrc readiness --json --policy ./org-baseline.json,./team-frontend.json

CI gating

Combine policies with --fail-level to enforce a minimum maturity level in CI:

- run: npx -y github:microsoft/agentrc readiness --policy ./policies/strict.json --fail-level 3

Advanced

JSON policies can disable, override, and set thresholds — but cannot add new criteria. For new detection logic, point users at AgentRC's TypeScript plugin system (docs/dev/plugins.md).

Operating rules

  • Never silently disable a pillar. If the user wants to disable observability, confirm and explain the trade-off.
  • Prefer overriding impact over disabling. Disabling hides the gap entirely; overriding lets it still appear in the report.
  • Recommend extras stay enabled. They cost nothing — they don't affect the score.
  • Suggest layering — most orgs want a baseline policy + per-team overrides chained with --policy a.json,b.json.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The acreadiness-policy skill assists users in managing AgentRC policies for scoring AI readiness. It facilitates creating, viewing, and applying policies using the official Microsoft agentrc CLI tool via npx. The skill handles JSON configuration files and integrates with other readiness assessment tools.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at f10fdb8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 6 months ago
Other metadata
argument-hint
[show | new <name> | apply <path-or-pkg>] — e.g. /acreadiness-policy show, /acreadiness-policy new strict-frontend
  • agentrc
  • readiness
  • policy
  • ci
  • scoring
  • json
  • standards
  • configuration

README badge

README badge for github/awesome-copilot/acreadiness-policy

Skill for picking, writing, or applying AgentRC readiness policies — JSON files that customize scoring by disabling irrelevant checks, overriding impact weights, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when standardizing readiness assessment across teams or enforcing maturity gates in CI.

Generated from the current SKILL.md.

Can I disable specific readiness checks like observability or dependabot?
Yes. Use the `criteria.disable` array in a policy JSON to turn off irrelevant checks. The skill will walk you through which pillars to disable based on your stack.
How do I enforce a minimum readiness grade in CI?
Combine a policy with the `--fail-level` flag in your CI workflow, e.g. `agentrc readiness --policy ./policies/strict.json --fail-level 3`, to gate on a specific maturity level.
Can I layer policies for org baseline plus team overrides?
Yes. Chain multiple policies with `--policy baseline.json,team-frontend.json`. AgentRC applies them in order, with later policies overriding earlier ones.
What are the built-in example policies?
AgentRC ships with `strict.json` (100% pass rate), `ai-only.json` (AI tooling focus), and `repo-health-only.json` (traditional quality focus) in `examples/policies/`.
Can I add new readiness criteria to a policy?
No. Policies can only disable, override impact/title, and set thresholds. For new detection logic, you need AgentRC's TypeScript plugin system.

Generated from the current SKILL.md. These answers refresh after source changes.