policy-author
Skill97 starsChanged 33 days agoApache-2.0View on GitHub
Draft or tighten a Runx operational policy from a governance brief, then validate the exact runx.operational_policy.v1 contract with the native policy engine. Use for repository/source/runner/owner policy design, fail-closed policy linting, or authority attenuation; never use this lane to widen an existing policy.
In this repository94 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- runxSkill
- adopt-skillSkill
- agencySkill
- answer-from-docsSkill
- attention-reviewSkill
- audit-receiptSkill
- brand-voiceSkill
- business-opsSkill
- chargeSkill
- chief-of-staffSkill
- cold-outreachSkill
- content-pipelineSkill
- contract-drafterSkill
- conversation-replySkill
- conversation-reviewSkill
- crm-cleanupSkill
- cve-auditSkill
- data-storeSkill
- data-subject-requestSkill
- deep-researchSkill
- diagnose-skill-runSkill
- dispute-respondSkill
- ecosystem-briefSkill
- extractSkill
- ghostwriteSkill
- github-pr-commentSkill
- github-pr-reviewSkill
- github-syncSkill
- google-analyticsSkill
- google-calendarSkill
- google-search-consoleSkill
- governed-outboundSkill
- helpdeskSkill
- incident-commanderSkill
- issue-intakeSkill
- issue-to-prSkill
- issue-triageSkill
- knowledge-routerSkill
- lead-enrichmentSkill
- lead-qualifySkill
- least-privilegeSkill
- ledgerSkill
- list-hygiene-judgeSkill
- marketplace-invokeSkill
- meeting-followupSkill
- mock-chargeSkill
- mock-paySkill
- mock-refundSkill
- moltbookSkill
- n8n-handoffSkill
- nitrosendSkill
- nws-weather-forecastSkill
- open-meteo-weather-forecastSkill
- operator-inboxSkill
- ops-deskSkill
- organic-growthSkill
- postmortem-makerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
When existing_policy is supplied, preserve its target/source/runner set and only attenuate authority.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Policy Author
Produce one reviewable operational-policy proposal. Let the agent translate
intent into policy fields; let the native policy.lint tool decide whether the
exact in-memory result is a valid Runx policy.
Workflow
- Require concrete target repositories, source locators, owner routes, and an
available runner. Return
needs_inputwhen any are unresolved. - Draft the smallest
runx.operational_policy.v1that admits the stated work. Unspecified work remains denied. - When
existing_policyis supplied, preserve its target/source/runner set and only attenuate authority. Do not add locators, actions, targets, sources, or runners; do not lower confidence or weaken human gates. - Pass the draft to the deterministic validation step. Never author or trust an agent-supplied lint verdict.
- Return
readyonly when native lint passes. A native failure or attempted widening returnsrejectwith structured findings.
Native policy contract
Draft the exact contract consumed by policy.lint and the Runx policy parser:
schema: runx.operational_policy.v1
schema_version: runx.operational_policy.v1
policy_id: string
sources:
- source_id: string
provider: string
allowed_locators: [string]
allowed_actions: [string]
source_thread:
required: boolean
publish_mode: reply | comment | none
missing_behavior: fail_closed
minimum_confidence: number # optional
runners:
- runner_id: string
kind: string
state: available | unavailable
allowed_actions: [string]
target_repos: [owner/repo]
scafld_required: boolean
owner_routes:
- route_id: string
owners: [string]
target_repos: [owner/repo]
targets:
- repo: owner/repo
runner_ids: [string]
allowed_actions: [string]
default_owner_route: string
scafld_required: boolean
base_branch: string # optional
dedupe:
strategy: source_fingerprint
key_fields: [string]
on_duplicate: reuse | comment | block
outcomes:
observe_provider: boolean
verification_required: boolean
close_source_issue: never | when_verified | always
publish_final_source_thread_update: boolean
permissions:
auto_merge: boolean
mutate_target_repo: boolean
require_human_merge_gate: booleanStop conditions
- Missing repository, locator, runner, or owner evidence:
needs_inputwithpolicy: null; native lint is not run. - Proposed widening of an existing policy:
rejectbefore lint and identify the widened path. - Native parse or validation failure:
reject; never relabel it as ready. - A request to widen authority: stop and route it to a separate explicit policy decision. This skill's existing-policy lane is attenuation-only.
Output
The final policy_proposal contains:
decision: ready | needs_input | reject
policy: object | null
validation:
status: pass | fail | not_run
engine: runx policy
findings: [{ code, path, message }]
readback: object | null
reason: string
rationale: string
blockers: [string]
needs_input: [string]
success_checkpoint: objectThe runtime receipt proves which draft was validated. It does not approve or install the policy.
Agent task contracts
policy-author-draft
Draft one policy proposal using the exact runx.operational_policy.v1 contract described by the
skill. Return decision, policy, rationale, blockers, needs_input, and success_checkpoint. Do not
author a lint verdict: the next deterministic step invokes native policy.lint. If required
repos, source locators, owners, or runner bindings are missing, return needs_input with policy
null. When existing_policy is supplied, never add authority, targets, sources, runners,
locators, or actions; only tighten permissions, confidence, routing, and outcomes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

