← ClaudeAtlas

agent-forgelisted

Design an agent only when a durable autonomy boundary is justified; compile it only when a Foundry runtime is available. Use for persistent decision rights, distinct memory, constrained tools, ownership transfer, or an ongoing schedule, channel, or API trigger.
frankxai/Starlight-Intelligence-System · ★ 9 · AI & Automation · score 72
Install: claude install-skill frankxai/Starlight-Intelligence-System
# Agent Forge ## Outcome Design the smallest justified persistent actor, or deliberately downgrade the request to a skill or temporary worker. Compile it only when a Foundry runtime is present. ## Agent necessity gate An agent must own at least one durable boundary: - stable decision rights; - a distinct memory scope; - a constrained tool or permission boundary; - genuine ownership transfer or handoff authority; - an ongoing schedule, channel, or API trigger. If none applies, stop and route to `$skill-forge`. A name, persona, or desire for “more intelligence” is not an agent boundary. ## Procedure 1. Build the Task Envelope. - Record the objective, deliverables, stakes, autonomy, permissions, evidence policy, and termination tests. 2. Prove necessity. - Mark each necessity-gate field true or false. - Explain the persistent boundary in operational language. - Compare the proposed agent against a skill, deterministic tool, and temporary task worker. 3. Define decision rights. - State what the agent may decide, what it may recommend, and what requires operator approval. - Exclude public release, financial commitment, destructive action, permission expansion, and substrate change unless explicitly authorized. 4. Define memory and tools. - Name readable and writable scopes separately. - Choose turn, session, or durable retention. - Allow only the minimum tools needed; list denied tools explicitly. 5. Define handoffs and termination. - Give eve