Skills

Skill 4 of 200

Acreadiness Policy

Help the user pick, write, or apply an AgentRC policy.

1 minute · 301 words · 11 sections

Install

$ npx skills add github/awesome-copilot --skill acreadiness-policy

$ npx skills add github/awesome-copilot

» /plugin marketplace add github/awesome-copilot

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

/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:

What to disable — irrelevant pillars or extras for their stack (e.g. disable observability for a static site).
What to raise — override impact to high or critical for must-haves (e.g. readme, codeowners).
Pass-rate threshold — typical org baselines: 0.7 (lenient), 0.85 (standard), 1.0 (strict).
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.

About this skill

Trigger

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.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/github/awesome-copilot, branch main, last pushed 24 September 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

200 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 2 distinct layouts observed: .github/skills/*/SKILL.md, skills/*/SKILL.md.

Authorship

3 of 200 skills are installed into the repository rather than published from it. They are shelved in the closing “Credited skills” part and remain the work of their own authors. A skill counts as credited when its only copy lives under one agent’s dot directory; visible directories, per-agent mirror sets, and skills installable from this repository on skills.sh all count as published.

Issue colours

Resolved from a curated brand profile — hue 295°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “11 headings” from h1 to h2 so the skill title is the only h1.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .github/plugin/marketplace.json by GitHub, declaring 162 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /github/awesome-copilot.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

/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:

What to disable — irrelevant pillars or extras for their stack (e.g. disable observability for a static site).
What to raise — override impact to high or critical for must-haves (e.g. readme, codeowners).
Pass-rate threshold — typical org baselines: 0.7 (lenient), 0.85 (standard), 1.0 (strict).
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.