agentsclimarketplace

Loopify governance

Skill AndreRatzenberger/loopify/plugins/loopify/skills/loopify-governance

Loop yes. Prompt no. Agent skills that turn specs into checked agent loops with receipts.

Install
npx -y skills add AndreRatzenberger/loopify --skill loopify-governance

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

  • 1 stars1 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

Use when adding budgets, approvals, rollback plans, data/privacy limits, dependency policy, authority boundaries, and harness-change contracts to higher-risk loops.

SKILL.md

1.6 KB, as published. Nobody here has run it

loopify-governance

Add governance to higher-risk loops.

When To Use

  • A loop can affect production, security, money, data, migrations, dependencies, public content, or external accounts.
  • A loop can mutate its own harness, checks, prompts, tools, or agent configuration.
  • A loop needs budgets, approvals, rollback, or stronger authority boundaries.

Do Not Use

  • Do not slow down low-risk loops with unnecessary ceremony.
  • Do not let an agent silently widen its own authority.
  • Do not treat approval as durable unless it is recorded.

Workflow

  1. Read the Loop Contract.
  2. Identify risk class with references/risk-classes.md.
  3. Add allowed paths, denied paths, budgets, approvals, rollback, data/privacy constraints, and dependency policy.
  4. Use references/authority-boundaries.md for boundary language.
  5. Add a harness-change contract if prompts, checks, tools, context builders, memory, or permissions can change.
  6. Update stop and escalation rules.
  7. Add review gates.

Output

Governance addendum, updated Loop Contract, or harness-change contract.

Validation

  • High-risk actions require explicit approval.
  • Rollback is named where mutation is possible.
  • Harness mutations are reviewed as future-behavior changes.

Example

Use loopify-governance to add budgets, denied paths, and a harness-change contract to .loopify/loops/001-papertrail/loop-contract.md.

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.