Skip to content
Productivity
Skill

/usecase-chief-of-staff-briefing

Build a morning/evening executive brief from calendar, inbox, tasks, and optional ops signals.

From plugin
cowork-os
452155 skills
Install
$ npx -y skills add CoWork-OS/CoWork-OS --skill usecase-chief-of-staff-briefing --agent claude-code

How 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.md
name: usecase-chief-of-staff-briefing
description: "Build a morning/evening executive brief from calendar, inbox, tasks, and optional ops signals."
version: "1.0.0"
metadata:
  author: CoWork OS Contributors <info@coworkosapp.com>

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
Ships withcowork-os

Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.

Get the whole plugin
Stats
450
Stars
77
Forks
Active
Maintenance
TypeScript
Language
MIT
License
6d ago
Last commit
7mo ago
Created

Repo: CoWork-OS/CoWork-OS

Other skills on cowork-os.