agentleFS
Sign inStart free
foliveirafoliveira/harmonia/skills/capture/SKILL.md

capture

Skill2 starsChanged 46 days agoMITView on GitHub

Harmonia capture stage - record learnings into the right memory tier, then ship structured commits. Use ONLY when explicitly invoked as /harmonia:capture.

57 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use weekly, ingest and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • gaiaaiagentSkill

    weekly

    Generate a weekly digest rolling up dailies into higher-level pattern analysis

    Also in 4 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 8 projects that use this

  • AnthropicSkill

    brief

    Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.

    Also in 6 projects that use this

  • QuixiAISkill

    weekly-review

    Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week

    Also in 5 projects that use this

  • dubwoahSkill

    ask

    Answer questions about the codebase without generating or modifying any code. Use when the user wants to understand how something works, find where something is defined, or explore the project structure. Invoked with /ask.

    Also in 4 projects that use this

  • AlexPEClubSkill

    refine

    Always use when the user wants to discuss an exsiting feature or specification. Open an existing feature spec to improve, extend, or fundamentally challenge it. Pass the feature ID as argument (e.g. /refine PROJ-2).

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 55 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Read the capture stage from ${CLAUDE_PLUGIN_ROOT}/core/lifecycle.yaml - its agent sequence ends with the committer by contract.

    line 8

“Common” is measured: kept by at least 6 in 10 of the 55 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

Your working contract is the rules; their digest is injected at session start - read ${CLAUDE_PLUGIN_ROOT}/core/RULES.md in full only if that digest is not in your context. Read the capture stage from ${CLAUDE_PLUGIN_ROOT}/core/lifecycle.yaml - its agent sequence ends with the committer by contract; do not hardcode.

  1. Workspace: bash ${CLAUDE_PLUGIN_ROOT}/bin/workspace.sh resolve --repo . (later stage: never mints; surface ambiguity or no-active-task and stop).
  2. Acceptance gate: capture requires the acceptance in-artifact (workspace:accepted), written only by the developer after they exercised the built behavior and it matches intent. Verify it: bash ${CLAUDE_PLUGIN_ROOT}/bin/workspace.sh verify-acceptance --repo .. Gate on the exit: any non-zero exit means refuse - surface the script's own message verbatim and stop, do not dispatch the curator; only a zero exit proceeds. The message states the remedy: no marker means the developer records acceptance via /harmonia:accept; a stale digest mismatch means the diff moved after acceptance, so the developer exercises the current behavior and re-accepts via /harmonia:accept (the marker must digest the diff it attests); a live rejection clears via /harmonia:accept or /harmonia:abandon. Never run accept on the developer's behalf - acceptance is a human act.
  3. Dispatch the knowledge curator with the verdict, scope, and diff-summary paths. It drafts learnings and writes each through bash ${CLAUDE_PLUGIN_ROOT}/bin/memory/capture.sh with an explicit --tier decision and --client flag where applicable - client content never reaches the global tier.
  4. Dispatch the committer with boundary.md, diff-summary.md, and the verdict: structured, single-concern commits whose messages communicate intent; nothing outside the boundary, never workspace files.
  5. Close the task: bash ${CLAUDE_PLUGIN_ROOT}/bin/workspace.sh complete --repo . (writes the completion marker so resolution skips this workspace).

Pass workspace paths, not prose recaps. Orchestrate only.

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