OpenParable
Skip to content
← Back to skills

Usecase Chief Of Staff Briefing

Productivity
usecase-chief-of-staff-briefing

Usecase Chief Of Staff Briefing is an Agent Skill for productivity published in the CoWork-OS/CoWork-OS repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CoWork-OS/CoWork-OS/blob/HEAD/resources/skills/usecase-chief-of-staff-briefing/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/usecase-chief-of-staff-briefing, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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

NameTypeRequiredDescription
timeframeselectNoTime horizon for the briefing
audience_styleselectNoHow executive vs detailed the brief should be
include_optional_signalsselectNoInclude weather/ops/revenue signals when connectors exist
delivery_styleselectNoFormatting style for final output

Runtime Prompt

  • Current runtime prompt length: 1219 characters.
  • Runtime prompt is defined directly in ../usecase-chief-of-staff-briefing.json.