agentleFS
DeepExtremaDeepExtrema/Tesseract/skills/digest/SKILL.md

digest

Skill4 starsChanged 14 days agoMITView on GitHub

Use when Taimoor asks for his digest, review, "what's new in the vault", or a morning/weekly catch-up. Composes a review note from the Tesseract vault — recent changes, captures, tasks, librarian health, suggested questions — and files it to Claude/Digests/.

37 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use aeon-update, auto-workflow and 10 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.
  • aaronjmarsSkill

    aeon-update

    Pull framework updates from the upstream Aeon repo into this instance - 3-way merges canon's new commits into a PR, never clobbering operator config.

    Also in 4 projects that use this

  • aaronjmarsSkill

    auto-workflow

    Two-mode aeon.yml workflow builder - analyze inspects URLs and emits a tiered, signal-verified skill-enablement plan plus an aeon.yml diff; enable flips slugs to enabled:true and opens a PR.

    Also in 4 projects that use this

  • +10 more from aaronjmars

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 33 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:

    Write the note with write_note to Claude/Digests/YYYY-MM-DD.md (today's date), overwrite=True — rerunning the same day replaces that day's …

    line 57

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

Digest — the vault review ritual

Requires the tesseract MCP server.

Steps

  1. Find the newest note in Claude/Digests/ (query_notes with folder="Claude/Digests", or list the folder). Its date (from the filename YYYY-MM-DD.md) is since. If the folder is empty, omit since — the bundle defaults to 7 days back.
  2. recall_bundle(mode="digest", since="<YYYY-MM-DD>").
  3. Compose the digest with EXACTLY these sections in this order. An empty section says "none" rather than disappearing — the eye learns the layout. A bundle section with status: "error" renders as ⚠ <section>: unavailable (<error>) — never silently dropped.

    ## Health — Librarian last-sweep timestamp and a one-line health summary from the librarian section. If the last sweep is older than 48 hours, open the line with ⚠ stale sweep.

    ## Captures to triage — inbox_captures notes, each [[wikilinked]].

    ## Tasks — open tasks (count, then list), then done_recently.

    ## Recent changes — recent_notes grouped by top-level folder, [[wikilinked]]. Skip the digest/answer notes this harness itself wrote if they dominate the list.

    ## Proposals pending — the proposals count plus a pointer to [[Organizer]] and [[Librarian]].

    ## New graph activity — new_entities notes (entity names are the filename stems), [[wikilinked]].

    ## Follow-ups due — job pipeline actions overdue today: sheet_query("jobs", {"next_follow_up": {"lte": "<today>"}, "status": {"nin": ["Rejected", "Ghosted", "Withdrawn"]}}), each row rendered as [[<note>]] — <company> <role> (<status>, due <next_follow_up>). Degrade gracefully: if the jobs sheet or the sheet_query tool is unavailable, render ⚠ Follow-ups: unavailable — never fail the digest.

    ## Discipline meter — sessions vs. logs, last 7 days: count Claude/Sessions/ notes whose filename date falls in the window and state it plainly ("N session logs filed this week"). If zero, nudge: "no session logs this week — the vault only compounds when work is filed." Omit judgment beyond that one line.

    ## Suggested questions — 2–3 questions the vault is NEWLY equipped to answer, inferred from recent changes and new entities. Write each as a one-liner Taimoor can paste straight into /recall.

  4. Write the note with write_note to Claude/Digests/YYYY-MM-DD.md (today's date), overwrite=True — rerunning the same day replaces that day's digest. Frontmatter: created: YYYY-MM-DD HH:MM, agent: claude, project: "", tags: [digest], type: digest.
  5. Show the digest in chat too.

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.