Menu
Compile daily briefing with meeting context, active deals, and citation tracking
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/praxstack/skills-and-personas --skill briefingThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| name | briefing |
| version | 1.3.0 |
| description | Compile daily briefing with meeting context, active deals, and citation tracking |
| triggers | ["daily briefing","morning briefing","what's happening today","brain pulse","pre-briefing pull"] |
| tools | ["search","query","get_page","list_pages","get_timeline"] |
| mutating | false |
| upstream | briefing@fc834ee |
Compile a daily briefing from brain context.
Filing rule: When the briefing creates or updates brain pages, follow
skills/_brain-filing-rules.md.
[Source: slug, updated DATE] citation.Run these BEFORE composing the briefing sections. All four pulls are read-only.
0a. Salience scan. Surface pages with high emotional or activity salience:
gbrain salience --days 7
Returns pages ranked by emotional weight and recent activity. Fold the top 5-10 into the briefing under a "High-Salience Pages" section — these are the entities and topics that are emotionally or operationally hot right now. Use this to prioritize which meetings/deals/people get the most briefing depth.
0b. Anomaly detection. Surface statistical anomalies in the brain:
gbrain anomalies
Defaults to today against a 30-day baseline; widen with
--lookback-days N or lower the threshold with --sigma 2. Flags cohorts
(by tag, by type) whose activity broke from their normal cadence — sudden
spikes in mentions or pages updating far off their usual rhythm. Add hits to
an "Anomalies" section after the brain pulse.
0c. Personal recall. Check stored personal facts and preferences before composing:
gbrain recall --query "current priorities and preferences" --json
Use recall to pull personal context — dietary preferences, communication preferences, prior commitments or promises made. This prevents the briefing from contradicting things the user has previously stated or decided.
0d. Hot memory pulse (v0.32). Before composing anything else, run:
gbrain recall --since-last-run --supersessions --pending --rollup --json
Fold the result into the briefing under a "Brain pulse" section at the top:
--supersessions output. Lead
with these because they're new corrections to your model of the world.top_entities from --rollup (top 5 entity slugs by
fact count in the window).facts array under each
entity from the rollup; include kind, notability, and confidence.pending_consolidation_count > 0,
note N facts await dream-cycle consolidation so the operator can decide
whether to run gbrain dream before reading further.The --since-last-run flag advances ~/.gbrain/recall-cursors/<source>.json
so the next briefing picks up exactly where this one left off. If you're
running this as a cron job, pass --source <slug> or set GBRAIN_SOURCE
explicitly — cron doesn't start in your repo-root cwd, so dotfile resolution
may miss the right source. Thin-client installs (gbrain init --mcp-only)
route through the remote brain transparently.
Before generating any briefing, load context from gbrain systematically.
For every attendee on the calendar invite:
gbrain search "<attendee name>" -- find their brain pagegbrain get <slug> -- load compiled truth, recent timeline, relationship contextBefore drafting or triaging any email:
gbrain search "<sender name>" -- load sender contextRun these queries to populate the briefing sections:
gbrain query "active deals status" -- deal pipeline snapshotgbrain query "meetings this week" -- recent meeting pages with insightsgbrain query "pending commitments follow-ups" -- open threads and action itemsgbrain list --type person --sort updated_desc --limit 10 -- people in playDAILY BRIEFING -- [date]
========================
MEETINGS TODAY
- [time] [meeting name]
Participants: [name] (slug: people/name, [key context])
ACTIVE DEALS
- [deal name] -- [status], deadline: [date]
Recent: [latest timeline entry]
ACTION ITEMS
- [item] -- due [date], related to [slug]
RECENT CHANGES (24h)
- [slug] -- [what changed]
PEOPLE IN PLAY
- [name] -- [why they're active]
If the briefing creates or updates any brain pages (e.g., new meeting prep
pages, updated entity pages), the back-linking iron law applies: every entity
mentioned must have a back-link from their page. See skills/_brain-filing-rules.md.
When presenting facts from brain pages, include inline citations:
[Source: slug, updated DATE]. A fact without a citation is unverifiable.