garrytan/gbrain

daily-task-prep

Morning preparation.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/garrytan/gbrain --skill daily-task-prep

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Daily Task Prep

Contract

This skill guarantees:

  • Calendar/meetings for today are loaded with brain context per attendee
  • Open threads from yesterday are surfaced
  • Active tasks reviewed with priority ordering
  • Prep briefing is actionable (not just informational)

Phases

  1. Load calendar. Check today's meetings. For each: load attendee brain pages, recent timeline, open threads.
  2. Check yesterday's threads. When google sources exist, gbrain waiting --json is the real data source for open threads and unanswered items — prefer it over prose heuristics (it carries loop rows with counterparty, due date, and evidence; see skills/google-loops/SKILL.md). Otherwise, search brain for yesterday's timeline entries. Flag anything unresolved.
  3. Review active tasks. Load ops/tasks from brain. Surface P0 and P1 items.
  4. Compile prep briefing. Per-meeting context cards + open threads + task priorities.

Output Format

Morning Prep — {date}
======================
Meetings today: {N}

## {Meeting 1 title} at {time}
Attendees: {names with brain context}
Context: {recent interactions, open threads}
Prep: {what to know before this meeting}

## Open Threads
- {thread from yesterday, with context}

## Tasks (P0-P1)
- {task with priority}

When it fails

Follow the agent operator protocol for any gbrain error code, exit code, [AGENT] block or notice block. Specific to this skill:

  • gbrain waiting refuses on stale data: run (or ask the user to run) the sync it names, then retry; do not prep from stale mail.
  • Meeting-context searches return nothing with a degraded notice: say the brain is searching keywords only right now, instead of "no prior context".

Anti-Patterns

  • Listing meetings without loading attendee context from brain
  • Ignoring yesterday's unresolved threads
  • Presenting tasks without priority ordering
du même dépôt

Autres Skills

Tous les Skills
garrytan
Communauté

academic-verify

Verify a research claim or academic citation by tracing it through publication → methodology → raw data → independent replication. Routes through perplexity-research for the actual web lookup, then formats results as a citation-checked brain page. Use when a book/article/conversation cites a study and you want to confirm the claim is real, replicated, and accurately characterized.

Installations / 1h
1
GitHub Stars
32,5 k
Mis à jour
11 nov.
garrytan
Communauté

ask-user

Reusable pattern for presenting the user with explicit choices and gating execution until they respond. Used by other skills when a decision point requires human input before proceeding. Platform-agnostic — works on Telegram (inline buttons), Discord, CLI, or any agent with a message tool.

Installations / 1h
1
GitHub Stars
32,5 k
Mis à jour
11 nov.
garrytan
Communauté

brain-ingest-gate

Pre-write quality gate for content entering the brain. No raw copies: a bare cp/mv into the brain repo is a bug. Before any new page lands, resolve named entities registry-first (a vector score is a floor for prose, never a gate for named things), then run the read-the-top-hit dedup decision tree (clear-dup / plausible-dup / clear). Owns dedup; delegates enrichment to the shipped ingestion skills. Routing convention, not an operation-boundary enforcement.

Installations / 1h
1
GitHub Stars
32,5 k
Mis à jour
11 nov.
garrytan
Communauté

brain-ops

Brain knowledge base operations. The core read/write cycle: brain-first lookup, read-enrich-write loop, source attribution, ambient enrichment, back-linking. Read this before any brain interaction.

Installations / 1h
1
GitHub Stars
32,5 k
Mis à jour
11 nov.