loop-engineering

Evolves Agent Skills from real-use postmortems and deduplicated feedback issues.

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/franklinbaldo/skills --skill loop-engineering-franklinbaldo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: loop-engineering
Source: https://github.com/franklinbaldo/skills/tree/main/loop-engineering
Command: npx skills add https://github.com/franklinbaldo/skills --skill loop-engineering-franklinbaldo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agent Skills often fail silently in production: workarounds go unrecorded, routing mistakes repeat, and quality regressions are never traced back to the skill contract. This Skill turns real-use evidence into durable improvements instead of relying on synthetic benchmarks. ## Core Features & Use Cases - Mandatory postmortems: After every material skill use, assess routing, outcome, quality delta, friction, and workarounds with a compact structured record. - Gated feedback issues: Open or update deduplicated GitHub issues only when actionable learning exists, with privacy sanitization rules. - Evidence-driven evolution: Diagnose feedback, apply the smallest justified change, add regression evals only when they protect a learned boundary, and decide between improving, branching, handing off, or creating a sibling skill. - Use Case: After three real tasks required the same workaround with a skill, use this Skill to consolidate the evidence into one feedback issue, diagnose the cause, and apply the minimal instruction fix. ## Quick Start Use the loop-engineering skill to turn the postmortem from my last skill use into a deduplicated feedback issue and the smallest justified change.

Frequently Asked Questions about loop-engineering

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

FAQPage Schema
How do I improve an Agent Skill based on real usage?▼

Run a structured postmortem after each material use covering routing, outcome, quality delta, friction, and workarounds. Persist only actionable learning as a deduplicated feedback issue, then apply the smallest change justified by the evidence.

When should I open a feedback issue for a skill?▼

Open an issue when routing was wrong, quality degraded, a workaround was required, instructions were ambiguous, a capability was missing, or a positive behavior is worth protecting. Routine success with no learning stays ephemeral.

Should every skill feedback issue become a regression eval?▼

No. Static evals are regression memory, not observability. Add an eval only after diagnosis when it protects a learned behavioral boundary; tool outages and one-off failures may not warrant fixtures.

How do I avoid duplicate skill feedback issues?▼

Search existing open and recently closed feedback issues before creating a new one. Add your independent observation as evidence to a matching issue, since multiple real uses on one issue are stronger than near-duplicates.

When should I create a new sibling skill instead of editing one?▼

Create a sibling skill only when repeated real-use evidence shows a distinct job with its own trigger and definition of done. Prefer the smallest option: improve the existing skill, add a reference, or clarify a handoff first.

What privacy rules apply to skill feedback reports?▼

Sanitize all feedback before publishing. Never include credentials, private case facts, personal data, confidential documents, or full private conversations; a redacted task summary plus a safe artifact reference is usually enough.