agentleFS
Sign inStart free
Fei2-LabsFei2-Labs/skill-genie/skills/close-loop/SKILL.md

close-loop

Skill12 starsChanged 49 days agoMITView on GitHub

End-of-session workflow for shipping changes, consolidating memory, applying self-improvements, and preparing publishable outputs with safety gates.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when the user says "close loop", "close-loop", "wrap up the session", "close session", "end session", "end of day", or …

    line 10
  2. Distinctive:

    Run four phases in order and return one consolidated inline report.

    line 12
  3. Distinctive:

    Follow these components in order.

    line 23
  4. Very specific:

    Run improvements + publish queue + output contract (04-phase-3-4-and-output.md)

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Close Loop

Use this skill when the user says "close loop", "close-loop", "wrap up the session", "close session", "end session", "end of day", or invokes /close-loop. This is the full end-of-session controller (ship + memory + self-improve + publish); for archiving a single Trellis task use finish-work instead.

Run four phases in order and return one consolidated inline report.

Modular structure

This skill is split into components for maintainability:

  1. components/01-design-principles.md
  2. components/02-phase-1-ship-state.md
  3. components/03-phase-2-memory.md
  4. components/04-phase-3-4-and-output.md

Follow these components in order.

Quick run order

  1. Apply execution policy and action gates (01-design-principles.md)
  2. Execute Ship State (02-phase-1-ship-state.md)
  3. Consolidate Memory (03-phase-2-memory.md)
  4. Run improvements + publish queue + output contract (04-phase-3-4-and-output.md)

Required output

Return:

  • Artifact A: human-readable report sections exactly as defined in component 04
  • Artifact B: machine-readable JSON block exactly as defined in component 04

Resources

  • references/memory-frameworks.md
  • assets/templates/wrap-report-template.md

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.

Check your setup, free