agentsclimarketplace

Orchestration policy enforcer

Skill alainlebret/claude-agents/higher-ed-teaching-agents/skills/orchestration-policy-enforcer

Modular skill and workflow ecosystems for AI coding assistants. Structured, multi-agent pipelines for specialized professional domains.

Install
npx -y skills add alainlebret/claude-agents --skill orchestration-policy-enforcer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Enforces workflow order, required artifacts, quality gates, and reproducibility rules for the orchestrator. Use when a workflow must be run in a disciplined, auditable, reproducible way.

SKILL.md

3.2 KB, 690 tokens by cl100k_base, as published. Nobody here has run it

Orchestration Policy Enforcer

Goal

Act as the final gatekeeper before a workflow's output is considered validated. Verify that all rules from shared/orchestration-policy/ and shared/reproducibility-policy/ have been applied, and emit a structured compliance report.

When to use

Run as the last step of any non-trivial workflow, after all skills have executed and all artefacts have been produced.

Inputs

  • workflow-spec.json — the authoritative list of required skills, artefacts, and quality gates
  • run-manifest.json — what was actually produced
  • quality-report.json — gate verification results
  • language-report.json — language compliance results
  • execution-plan.json — planned vs. actual skill execution

Output contract

FileDescription
orchestration-compliance-report.mdStructured report: one section per policy rule, with verdict and evidence

Report structure

# Orchestration Compliance Report — <workflow_id> — <run_id>

## Policy: Required artefacts
- mission.json: present ✓
- execution-plan.json: present ✓
- run-manifest.json: present ✓
- quality-report.json: present ✓
- [other expected artefacts]: present ✓ / MISSING ✗

## Policy: Quality gates
- QG1 mission-present: pass ✓ / fail ✗
- ...

## Policy: Language compliance
- overall_status: pass ✓ / review ✗

## Policy: Reproducibility
- run_id present: yes ✓
- created_at present: yes ✓
- skills_used matches execution_order: yes ✓ / MISMATCH ✗

## Overall verdict
COMPLIANT / NON-COMPLIANT — [summary of blocking issues]

Compliance rules (from shared policies)

RuleSourceCheck
mission.json must be presentorchestration-policy.mdrun-manifest.json → artifacts_out contains mission.json
execution-plan.json must be presentorchestration-policy.mdfile exists in run or example directory
run-manifest.json must be presentorchestration-policy.mdfile exists with valid run_id
At least one audit artefact must existorchestration-policy.mdquality-report.json or orchestration-compliance-report.md present
Launcher must not silently invent inputslauncher-policy.mdartifacts_in in manifest only lists files that actually existed
Quality gates must be stored as JSONlauncher-policy.mdquality-report.json exists and is valid JSON
run_id must be unique and timestampedreproducibility-policyrun_id matches pattern RUN-<WORKFLOW>-<ISO8601>
Language report must be emittedworkflow language_constraintslanguage-report.json exists if must_emit_language_report: true

Rules

  • Report all non-compliances, not just the first one found.
  • A workflow with any blocking non-compliance must have overall_status: fail.
  • A workflow with only warnings must have overall_status: review.
  • A fully compliant workflow must have overall_status: pass.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.