/usecase-chief-of-staff-briefing
Build a morning/evening executive brief from calendar, inbox, tasks, and optional ops signals.
$ npx -y skills add CoWork-OS/CoWork-OS --skill usecase-chief-of-staff-briefing --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/usecase-chief-of-staff-briefing
Context preview
The summary Claude sees to decide when to auto-load this skill.
Build a morning/evening executive brief from calendar, inbox, tasks, and optional ops signals.
SKILL.md
usecase-chief-of-staff-briefing.SKILL.mdname: usecase-chief-of-staff-briefing
description: "Build a morning/evening executive brief from calendar, inbox, tasks, and optional ops signals."
Chief of Staff Briefing
Purpose
Build a morning/evening executive brief from calendar, inbox, tasks, and optional ops signals.
Routing
- Use when: Use when the user asks to build a morning or daily executive brief from calendar, inbox, tasks, and optional ops signals.
- Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Outputs: Outcome from Chief of Staff Briefing: one high-signal brief plus prioritized next actions.
- Success criteria: Delivers a concise brief with explicit data availability boundaries and clear recommended actions.
Trigger Examples
Positive
- Use the usecase-chief-of-staff-briefing skill for this request.
- Help me with chief of staff briefing.
- Use when the user asks to build a morning or daily executive brief from calendar, inbox, tasks, and optional ops signals.
- Chief of Staff Briefing: provide an actionable result.
Negative
- Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Do not use usecase-chief-of-staff-briefing for unrelated requests.
- This request is outside chief of staff briefing scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | timeframe | select | No | Time horizon for the briefing | | audience_style | select | No | How executive vs detailed the brief should be | | include_optional_signals | select | No | Include weather/ops/revenue signals when connectors exist | | delivery_style | select | No | Formatting style for final output |
Runtime Prompt
- Current runtime prompt length: 1219 characters.
- Runtime prompt is defined directly in `../usecase-chief-of-staff-briefing.json`.
Read more
name: usecase-chief-of-staff-briefing description: "Build a morning/evening executive brief from calendar, inbox, tasks, and optional ops signals."
Chief of Staff Briefing
Purpose
Build a morning/evening executive brief from calendar, inbox, tasks, and optional ops signals.
Routing
- Use when: Use when the user asks to build a morning or daily executive brief from calendar, inbox, tasks, and optional ops signals.
- Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Outputs: Outcome from Chief of Staff Briefing: one high-signal brief plus prioritized next actions.
- Success criteria: Delivers a concise brief with explicit data availability boundaries and clear recommended actions.
Trigger Examples
Positive
- Use the usecase-chief-of-staff-briefing skill for this request.
- Help me with chief of staff briefing.
- Use when the user asks to build a morning or daily executive brief from calendar, inbox, tasks, and optional ops signals.
- Chief of Staff Briefing: provide an actionable result.
Negative
- Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Do not use usecase-chief-of-staff-briefing for unrelated requests.
- This request is outside chief of staff briefing scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | timeframe | select | No | Time horizon for the briefing | | audience_style | select | No | How executive vs detailed the brief should be | | include_optional_signals | select | No | Include weather/ops/revenue signals when connectors exist | | delivery_style | select | No | Formatting style for final output |
Runtime Prompt
- Current runtime prompt length: 1219 characters.
- Runtime prompt is defined directly in `../usecase-chief-of-staff-briefing.json`.
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
Other skills on cowork-os.
- /attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /deep-security-scan
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide discovery passes with worker-specific threat models, semantically merge candidates, synthesize one canonical validation
Open skill - /finding-discovery
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /fix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /security-diff-scan
Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed change set.
Open skill - /security-scan
Use when the user asks for a repository-wide or scoped-path security scan.
Open skill