loop-constraints

Enforce AutoResearch loop constraints before triage, edits, and remote execution.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/Kirrito-k423/AutoResearch --skill loop-constraints-kirrito-k423
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: loop-constraints
Source: https://github.com/Kirrito-k423/AutoResearch/tree/main/.codex/skills/loop-constraints
Command: npx skills add https://github.com/Kirrito-k423/AutoResearch --skill loop-constraints-kirrito-k423

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Autonomous loop work can violate safety boundaries, skip human approval gates, or act while the system is paused. This Skill loads and enforces the AutoResearch loop constraints before any triage, editing, remote execution, or external writes so every action respects role scope and denylists. ## Core Features & Use Cases - Constraint Loading: Reads loop-constraints.md, docs/safety.md, and LOOP.md before any loop work begins. - Pause Detection: Exits without action when a .loop-paused file exists or STATE.md reports a paused status. - Gate and Denylist Enforcement: Counts and reports active human gates and denylist categories, applying them to every subsequent action. - Escalation Handling: Returns ESCALATE_HUMAN with the blocked action and required approval when authority is missing. - Use Case: Before an agent edits code, pushes to GitHub, or runs commands on a remote NPU server, invoke this Skill to verify the action is within role scope and not on the denylist. ## Quick Start Ask the agent to load and enforce the loop constraints before performing any triage, code edits, remote execution, or Git and connector writes.

Frequently Asked Questions about loop-constraints

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce safety constraints before autonomous agent actions?▼

Load the loop constraints Skill before any triage, edit, or remote execution. It reads loop-constraints.md, docs/safety.md, and LOOP.md, then applies active human gates and denylists to every following action.

How does the loop pause mechanism work in AutoResearch?▼

The Skill checks for a .loop-paused file or a Status: paused entry in STATE.md before acting. If either indicates a paused state, it exits without performing any action.

What happens when an agent lacks authority for an action?▼

The Skill returns ESCALATE_HUMAN with the blocked action and the required approval. This applies before editing, remote execution, Git or GitHub writes, and connector writes when role scope or denylist checks fail.

What actions are never allowed by the loop constraints?▼

The Skill never auto-merges changes, weakens tests, exposes credentials, or lets a maker verify its own work. These prohibitions override triage priority in every workflow.

When should loop constraints be re-checked during a workflow?▼

Re-check the relevant role scope and denylist before each sensitive operation: editing files, executing commands remotely, writing to Git or GitHub, and writing through connectors. Constraints override triage priority at every step.