- name
- acreadiness-policy
- description
- 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.
- argument-hint
- [show | new <name> | apply <path-or-pkg>] — e.g. /acreadiness-policy show, /acreadiness-policy new strict-frontend
/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/:
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
Score = 1 − (deductions / max possible weight). Grades: A ≥ 0.9, B ≥ 0.8, ≥ 0.7, ≥ 0.6, < 0.6.