agentleFS
anthonysuherlianthonysuherli/br8n/skills/notes/SKILL.md

notes

Skill1 starsChanged 3 months agoMITView on GitHub

Dictate what kind of session notes br8n takes for this repo+branch — show the current note policy (section template + steer), edit it inline with free-text guidance, or launch a guided wizard to co-design it. Use when the user wants to control what end-of-session notes capture ("focus on architecture", "skip dep bumps"), review the policy, or set it up from scratch with `--wizard`.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 1

    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:

    No prior tap needed — policy read/write is independent of KB coverage.

    line 27
  2. Very specific:

    Keep its sections exactly as-is.

    line 57

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

br8n — Notes (steer the session-note policy)

br8n writes a session note at the end of every conversation (see ../_shared/session-note.md — fired by the Stop hook, best-effort, never blocking). What goes into that note is governed by a per-KB policy: a section template (## Decisions, ## Changes, …) plus a free-text steer ("emphasize architecture, skip dependency bumps"). This skill is how you read and shape that policy. It does not write a note itself — it only changes the rules the next session note follows.

Step 0 — Resolve target

project = git repo basename, kb = git branch, project_path = repo root (see ../_shared/preamble-first.md):

basename "$(git rev-parse --show-toplevel)"   # project
git branch --show-current                     # kb
git rev-parse --show-toplevel                 # project_path

No prior tap needed — policy read/write is independent of KB coverage.

Mode select — branch on the args

InvocationModeDo
/br8n:notes (no args)ShowStep A — print the current policy
/br8n:notes <free text>SteerStep B — set the steer to that text
/br8n:notes --wizardWizardStep C — run the guided co-design

Step A — Show the current policy

Call mcp__plugin_br8n_br8n__br8n_notes_policy_get(project, kb, project_path). It returns {policy: {sections: [{name, enabled}], steer}, project, kb} (the default policy if none is set yet). Render it readably:

Note policy — <project> / <kb> Sections the next note will use:

  • <name> — enabled / disabled Steer: <steer, or "(none)">

Then mention the two ways to change it: pass free text to set a steer, or --wizard to redesign the section template.

Step B — Set the steer from free text

The args are the new steer (e.g. /br8n:notes focus on architecture, skip dep bumps).

  1. br8n_notes_policy_get(project, kb, project_path) — fetch the current policy.
  2. Keep its sections exactly as-is; replace steer with the user's text.
  3. mcp__plugin_br8n_br8n__br8n_notes_policy_set(project, kb, project_path, policy=<updated>). On {ok: false, errors} show the errors, fix, and retry — nothing is saved until valid. On {ok: true} confirm: echo the new steer and the (unchanged) section list so the user sees exactly what the next session note will honor.

Step C — Run the guided wizard

Hand off to ../_shared/notes-policy-wizard.md — the one-question-at-a-time loop that co-designs the section template + steer and persists via br8n_notes_policy_set at a turn boundary. The wizard only runs on an explicit --wizard (the user opts in); it is never auto-launched.

Download now (ZIP)

  • Other versions20 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 20

    1. blogminhquy/javis-os★ 505same name
    2. howells/fiction★ 19same name
    3. microsoft/PilotSwarm★ 14same name
    4. DaniilBrusnikUa/claude-code-handoff★ 9same name
    5. adeonir/agent-skills★ 8same name
    6. phanghonghao/THU-Awesome-Skills★ 8same name
    7. baney75/myelinate★ 4same name
    8. DoKu67/claude-code-skils★ 4same name
    9. jholhewres/devclaw-skills★ 4same name
    10. TTflysky/sirenhuisuo★ 4same name

    10 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use brainstorm.

    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.
    • nicolasestremSkill

      brainstorm

      Structured idea generation and solution exploration with systematic analysis.

      Also in 3 projects that use this

  • In this repository11 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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.