agentleFS
vpeetla-aivpeetla-ai/react-agent-pattern/.cursor/skills/loop-engineering/SKILL.md

loop-engineering

Skill2 starsChanged 4 months agoMITView on GitHub

Implement ODAEU harness loops, RAG evolve tuning, and procedural memory in LoopForge or similar systems. Use when building self-improving agents, eval gates, MCP tool bridges, or RAG version trees.

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never give agents raw shell without allowlist

    line 36

“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Loop Engineering

ODAEU outer loop

PhaseAction
ObserveLoad RAG config vN, memory hints, corpus context
DecidePlan ReAct steps or orchestrator decomposition
ActMCP tools (read_file, search_docs) or repo patches
EvaluateRecall, faithfulness, pytest, review score
UpdateTune RAG (top_k, hybrid_alpha) + write lesson

RAG evolve signals

FailureTune
low_recall↑ top_k, ↑ hybrid_alpha
low_faithfulness↑ rerank_threshold, ↓ hybrid_alpha

Memory

  • Lesson(failure_mode, lesson, rag_version) → JSON store (v1)
  • Hints injected on next run via hints_for_query

MCP bridge

  • Local adapters in mcp/bridge.py; extensible to stdio MCP servers
  • Never give agents raw shell without allowlist

Reference

  • loop-engine-agent-platform/src/loop_engine/harness/
  • loops/support-intelligence.yaml
  • ADR-001 in LoopForge repo

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.