Files
gbrain/skills/briefing/SKILL.md
Garry Tan 1e6d7e3737 feat: battle-tested skill patterns from production deployment
Backport production-learned brain-operations patterns:
- Iron Law of Back-Linking (mandatory bidirectional linking)
- Brain filing rules (file by primary subject, not format)
- Enrichment protocol (7-step pipeline, 3-tier system, person/company templates)
- Media ingest workflows (articles, videos, podcasts, PDFs, screenshots)
- Citation requirements (mandatory [Source: ...] on every fact)
- Test Before Bulk operating principle
- Voice recipe: unicode crash fix, PII scrub, identity-first prompt, DIY STT+LLM+TTS
- X-to-Brain recipe: image OCR, Filtered Stream, tweet rating rubric, cron stagger
2026-04-11 17:07:19 -10:00

3.3 KiB

Briefing Skill

Compile a daily briefing from brain context.

Filing rule: When the briefing creates or updates brain pages, follow skills/_brain-filing-rules.md.

Workflow

  1. Today's meetings. For each meeting on the calendar:
    • Search gbrain for each participant by name
    • Read their pages from gbrain for compiled_truth context
    • Summarize: who they are, recent timeline, relationship to you
  2. Active deals. List deal pages in gbrain filtered to active status:
    • Deadlines approaching in the next 7 days
    • Recent timeline entries (last 7 days)
  3. Time-sensitive threads. Open items from timeline entries:
    • Items with deadlines in the next 48 hours
    • Follow-ups that are overdue
  4. Recent changes. Pages updated in the last 24 hours:
    • What changed and why (read timeline entries from gbrain)
  5. People in play. List person pages in gbrain sorted by recency:
    • Updated in last 7 days
    • Have high activity (many recent timeline entries)
  6. Stale alerts. From gbrain health check:
    • Pages flagged as stale that are relevant to today's meetings

GBrain-Native Context Loading

Before generating any briefing, load context from gbrain systematically.

Before a meeting

For every attendee on the calendar invite:

  • gbrain search "<attendee name>" -- find their brain page
  • gbrain get <slug> -- load compiled truth, recent timeline, relationship context
  • If no page exists, note the gap ("No brain page for Sarah Chen -- consider enrichment")

Before an email reply

Before drafting or triaging any email:

  • gbrain search "<sender name>" -- load sender context
  • Read their compiled truth to understand who they are, what they care about, and your relationship history. This turns a cold reply into an informed one.

Daily briefing queries

Run these queries to populate the briefing sections:

  • gbrain query "active deals status" -- deal pipeline snapshot
  • gbrain query "meetings this week" -- recent meeting pages with insights
  • gbrain query "pending commitments follow-ups" -- open threads and action items
  • gbrain search --type person --sort updated --limit 10 -- people in play

Output Format

DAILY 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]

Back-Linking During Briefing

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.

Citation in Briefings

When presenting facts from brain pages, include inline citations:

  • "Jane is CTO of Acme [Source: people/jane-doe, updated 2026-04-01]"
  • This lets the user trace any claim back to the brain page and assess freshness

Tools Used

  • Search gbrain by name (query)
  • Read a page from gbrain (get_page)
  • List pages in gbrain by type (list_pages)
  • Check gbrain health (get_health)
  • View timeline entries in gbrain (get_timeline)