# Briefing

> Compila una briefing diaria con contexto de reuniones, deals activos y seguimiento de citas de fuente.

Fuente: https://skillsagentes.com/skills/garrytan/gbrain/briefing
Markdown: https://skillsagentes.com/skills/garrytan/gbrain/briefing.md

Repositorio: https://github.com/garrytan/gbrain
Autor: garrytan
Licencia: MIT
Actualizado: hace 9 días
Coste de contexto: 20 tok instalada, 1.9k tok al activarse, 2.2k tok con todos los archivos del bundle
Bundle: 2 archivos, 9 KB
Permisos que pide: search, query, get_page, list_pages, get_timeline

## Instalación

Un skill son archivos markdown: los mismos archivos valen para cualquier agente y lo único que cambia es el directorio de destino, es decir la bandera `--agent`. Añade `-g` para instalarlo en todos los proyectos de la máquina.

```bash
# Claude Code
npx -y skills add garrytan/gbrain --skill briefing --agent claude-code
# Cursor
npx -y skills add garrytan/gbrain --skill briefing --agent cursor
# Codex
npx -y skills add garrytan/gbrain --skill briefing --agent codex
# Gemini CLI
npx -y skills add garrytan/gbrain --skill briefing --agent gemini
# Windsurf
npx -y skills add garrytan/gbrain --skill briefing --agent windsurf
# Cline
npx -y skills add garrytan/gbrain --skill briefing --agent cline
```

## Qué hace

- Compila una briefing diaria a partir de gbrain: reuniones, deals activos, hilos pendientes y cambios recientes
- Ejecuta pulls previos de solo lectura: salience scan, detección de anomalías, recall personal y pulso de memoria caliente
- Añade citación inline `[Source: slug, updated DATE]` a cada dato presentado
- Resuelve participantes de reuniones contra el brain y marca explícitamente los huecos de cobertura
- Señala páginas obsoletas (30+ días) relevantes al contexto del día en vez de presentarlas como actuales

## Cuándo usarla

- Al pedir una 'daily briefing' o 'morning briefing'
- Antes de una reunión, para cargar contexto de cada asistente
- Antes de responder un email, para cargar contexto del remitente
- Cuando se quiere un pulso general ('brain pulse') del estado del brain

## Qué la activa

- "Dame la briefing diaria de hoy"
- "¿Qué está pasando hoy? Necesito el brain pulse"
- "Prepárame el contexto antes de mi reunión con Jane"
- "Hazme un pre-briefing pull antes de responder este email"

## Antes de instalar

- Requiere el CLI `gbrain` configurado con acceso al brain (search, query, get_page, list_pages, get_timeline).

## Archivos

- SKILL.md — 7 KB
- routing-eval.jsonl — 1 KB

## SKILL.md

Reproducido tal cual desde garrytan/gbrain bajo MIT. Esta sección es el documento original y está en inglés.

# 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`.

## Contract

- Every fact in the briefing includes an inline `[Source: slug, updated DATE]` citation.
- Meeting participants are resolved against the brain; gaps are explicitly flagged.
- Active deals and action items include deadlines and recency context.
- The briefing is read-only: no brain pages are created or modified unless the user explicitly requests it.
- Stale alerts surface pages relevant to today's context, not just all stale pages.

## Pre-Briefing Context Pull

Run these BEFORE composing the briefing sections. All four pulls are read-only.

0a. **Salience scan.** Surface pages with high emotional or activity salience:

   ```bash
   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:

   ```bash
   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:

   ```bash
   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:

   ```bash
   gbrain recall --since-last-run --supersessions --pending --rollup --json
   ```

   Fold the result into the briefing under a "Brain pulse" section at the top:
   1. **Contradictions resolved overnight** — the `--supersessions` output. Lead
      with these because they're new corrections to your model of the world.
   2. **Top mentions** — `top_entities` from `--rollup` (top 5 entity slugs by
      fact count in the window).
   3. **New facts since last briefing** — group the `facts` array under each
      entity from the rollup; include `kind`, `notability`, and `confidence`.
   4. **Pending consolidation footer** — when `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.

## Phases

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 alice-example -- 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 list --type person --sort updated_desc --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

## Anti-Patterns

- **Briefing without brain queries.** Never generate a briefing from memory alone; always query gbrain for current data.
- **Uncited facts.** Every claim must include `[Source: slug, updated DATE]`. A fact without a citation is unverifiable.
- **Stale context presented as current.** If a page hasn't been updated in 30+ days, flag the staleness explicitly rather than presenting it as fresh.
- **Modifying brain pages unprompted.** The briefing is read-only by default. Do not create or update pages unless the user explicitly requests it.
- **Ignoring coverage gaps.** When a meeting participant has no brain page, say so. Silence about gaps hides ignorance.

## 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)

## Dónde encaja

- Categoría: [Productividad](https://skillsagentes.com/categorias/productividad.md) — Planificación, toma de notas y automatización de flujos personales.
- Creador: [garrytan](https://skillsagentes.com/creators/garrytan.md) — 134 skills en el directorio
- [Todas las skills](https://skillsagentes.com/skills.md)
- [Ranking de instalaciones](https://skillsagentes.com/ranking.md)

## Otras skills del mismo repositorio

- [Setup](https://skillsagentes.com/skills/garrytan/gbrain/setup.md): Configura GBrain con auto-aprovisionamiento de Supabase o PGLite, inyección en AGENTS.md y primera importación.
- [Maintain](https://skillsagentes.com/skills/garrytan/gbrain/maintain.md): Chequeos de salud del brain: aplicación de back-links, auditoría de citas, validación de filing, detección de info obsoleta, páginas huérfanas y benchmarks.
- [Schema Unify](https://skillsagentes.com/skills/garrytan/gbrain/schema-unify.md): Migra un brain de gbrain-base a la taxonomía de 14 tipos canónicos de gbrain-base-v2 usando gbrain onboard --check y el handler Minion unify-types.
- [Retrieval Reflex](https://skillsagentes.com/skills/garrytan/gbrain/retrieval-reflex.md): Cuándo y qué recuperar: abre la página del brain de una entidad relevante antes de responder desde memoria.
- [Minion Orchestrator](https://skillsagentes.com/skills/garrytan/gbrain/minion-orchestrator.md): Skill unificado de Minions para jobs deterministas de shell y orquestación de subagentes LLM: cola durable, observable y controlable, más la doctrina de ejecución durable para operaciones largas.

---

Skills Agentes · [Índice de páginas en markdown](https://skillsagentes.com/sitemap.md) · [Inicio](https://skillsagentes.com/index.md)