agentleFS
wrg32786wrg32786/aigent-os/skills/reconcile/SKILL.md

reconcile

Skill25 starsChanged 7 days agoMITView on GitHub

Compare seven-day project attention in daily notes with explicit Tier-1 intended shares. Use when reconciling attention or checking priority drift. Read-only.

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use grill, debug and 3 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.
  • renatorozasSkill

    grill

    Adversarial code review. Don't let me ship until the changes pass your scrutiny.

    Also in 3 projects that use this

  • AnthropicSkill

    debug

    Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

    Also in 4 projects that use this

  • nicolasestremSkill

    brainstorm

    Structured idea generation and solution exploration with systematic analysis.

    Also in 3 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 2

    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. Distinctive:

    Use literal output and exit status as the checkpoint evidence.

    line 25
  2. Very specific:

    Read vault/memory/ACTIVE_PRIORITIES.md and locate explicit Tier-1 projects with intended percentages.

    line 29
  3. Distinctive:

    No intended shares returns nonzero:

    line 47

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

/reconcile - attention reconciliation

This measurement leg reports attention drift. It never edits priorities, daily notes, goals, or runtime state.

Run:

node daemons/nightly-reconcile.mjs --root <aigent-root> --as-of <fire-date>

Use literal output and exit status as the checkpoint evidence.

Required intended-share input

Read vault/memory/ACTIVE_PRIORITIES.md and locate explicit Tier-1 projects with intended percentages. Accepted forms:

| Tier | Project | Intended share |
| 1 | [[Project Name]] | 40% |

or:

Tier 1 - [[Project Name]] - intended 40%

Shares are integers from 1 through 100 and the Tier-1 total must be at most 100. Names or aliases must resolve to a project note or an explicit canonical name in the priorities file.

No intended shares returns nonzero:

RECONCILE FAIL reason=intended-share-input-absent projects=0

This is a configuration failure, never permission to invent shares.

Seven-day measurement

  1. Select valid vault/daily/YYYY-MM-DD.md notes inside the exact calendar window as_of-6d .. as_of. A missing day contributes no mentions.
  2. Per project and note, count at most:
    • 3 points for a heading or heading wikilink;
    • 2 points for a body wikilink to a canonical note or alias;
    • 1 point for an exact plain-text name.
  3. One occurrence receives only its highest applicable weight.
  4. Track project references outside Tier 1 as non-Tier-1 attention.
  5. Compute actual = project points / all project points * 100, rounded to one decimal.

A zero denominator returns RECONCILE FAIL reason=no-measurable-project-attention.

Drift predicates

  • Tier-1 drift: actual < 0.40 * intended.
  • Combined non-Tier-1 drift: actual share over 25 percent.

Output raw points, actual share, intended share, thresholds, drift decisions, and source paths so the arithmetic is reproducible:

RECONCILE PASS window=YYYY-MM-DD..YYYY-MM-DD notes=<N>
project=<name> points=<N> actual=<N.N>% intended=<N>% threshold=<N.N>% drift=<yes|no>
non_tier_1 points=<N> actual=<N.N>% drift=<yes|no>

Missing notes, shares, measurable attention, or parseable dates are not green.

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.