Daily briefing — board, ecosystem activity, tracker sync, goals. Parallel 4-stream collection. Modes: --quick, --html. Trigger: "/briefing", "briefing", "good morning", "daily standup", "checkin", "morning briefing". (Bare "status" → bridge-status; bare "what is up" → dashboard.)
Scanned 9/5/2026
Install to Claude Code
npx -y skills add bks-lab/open-bridge --skill briefing --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Briefing?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/bks-lab-briefing)More formats (shields.io, HTML) on the badges page.
---
name: briefing
description: 'Daily briefing — board, ecosystem activity, tracker sync, goals. Parallel 4-stream collection. Modes: --quick, --html. Trigger: "/briefing", "briefing", "good morning", "daily standup", "checkin", "morning briefing". (Bare "status" → bridge-status; bare "what is up" → dashboard.)'
metadata:
scope: core
---
# Briefing
Daily and on-demand briefing. Read the referenced file ONLY when triggered.
## Arguments
| Argument | Effect | Default |
|----------|--------|---------|
| `(none)` | Full briefing — all 4 streams + Phase 2 board.md sync | — |
| `--quick` | Focus box + Stream A only; **skips** trackers, companion data, channels, Phase 2 | false |
| `--skip-trackers` | All streams except Stream B (offline-friendly); Phase 2 still runs | false |
| `--commits YYYY-MM-DD` | Detailed commit analysis for one day (sessions, time est., types) — see `references/commit-analysis.md` | — |
| `--html` | After terminal output, delegate to `/bridge-dashboard` to render the operational HTML dashboard | false |
### Mode × Phase matrix
| Phase | default | `--quick` | `--skip-trackers` |
|-------|---------|-----------|-------------------|
| Phase 0 (smart detection + day block) | ✅ | ✅ | ✅ |
| Stream A (local state) | ✅ | ✅ | ✅ |
| Stream B (trackers fan-out) | ✅ | ❌ | ❌ |
| Stream C (companion: calendar, imports) | ✅ | ❌ | ✅ |
| Stream D (channels) | ✅ | ❌ | ✅ |
| Phase 2 (board.md sync) | ✅ | ❌ | ✅ |
| Phase 3 (log entry) | ✅ | ✅ | ✅ |
| Phase 4 (terminal output) | ✅ | ✅ | ✅ |
## Prerequisites
- `bridge-config.yaml` with `work.enabled: true`. If not: offer setup.
- Standing orders are loaded at session start (per CLAUDE.md). If `/briefing`
is invoked **standalone** (e.g. via cron or a long-running session), manually
load `protocols/standing-orders/*.md` **and `protocols/standing-orders/user/*.md`**
before Phase 1 — the `applications` surface logic in Stream C depends on them, and
an applications order is user-tier (a `*.md` glob alone does not reach `user/`).
## Decision Tree
```
User wants to...
├── Full daily briefing → Read references/workflow.md
├── Quick local-only briefing → Read references/workflow.md (--quick path)
├── Detailed commit analysis → Read references/commit-analysis.md
├── Are we behind on anything? → Read references/upstream-summary.md
│ (covers BOTH inbound channels: CORE from
│ the `role: oss-core` upstream, and every
│ subscribed org overlay. Needs an
│ `upstreams:` list in bridge-config.yaml;
│ a Bridge with none skips)
└── Questions about briefing → Answer from this file
```
## Sister skills (don't duplicate)
| For… | Use |
|------|-----|
| Memory drift, doc-link health, branch/config sanity | `/bridge-status` |
| Live service status of channels/remotes (launchd, processes, ports) | `/remote` |
| Detailed GitHub/ADO board view (per-project) | `/dashboard` |
| Visual ops dashboard (Fleet + Board + Calendar + Channels) | `/bridge-dashboard` (also the target of `--html`) |
| Weekly archive | `/archive` |
`/briefing` is a **daily** rollup. The skills above are deeper dives into
a single dimension; cross-link rather than re-implement.
## Activity Types (log entries)
These describe **what kind of work** happened — used as the `Type` column
in `work/log.md` activity-log tables.
| Symbol | Name |
|--------|------|
| 🧪 | Testing |
| 💻 | Development |
| 🔬 | Analysis |
| 📋 | Planning |
| 📝 | Documentation |
| 🔧 | DevOps |
| 📅 | Meeting |
| 📧 | Communication |
| 📁 | Documents |
| 🐛 | Bug / Incident |
| 🎓 | Talk / Teaching |
| 🧠 | Insight / Sequential-thinking |
Distinct from the **commit-message classification** taxonomy in
`references/commit-analysis.md` — that one is for analyzing git history
(🐛 Bug Fixing, 🎯 Feature, 🔧 Code Refactoring, …). The taxonomies overlap
on a few icons but address different artefacts; don't try to unify them.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!