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…
Triage Inbox Agent Today lanes, search mailbox evidence, prepare manual or AI-assisted replies, and suggest cleanup automations with strict confirmation gates.
$ npx -y skills add CoWork-OS/CoWork-OS --skill usecase-inbox-manager --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/usecase-inbox-managerContext preview
The summary Claude sees to decide when to auto-load this skill.
Triage Inbox Agent Today lanes, search mailbox evidence, prepare manual or AI-assisted replies, and suggest cleanup automations with strict confirmation gates.
name: usecase-inbox-manager description: "Triage Inbox Agent Today lanes, search mailbox evidence, prepare manual or AI-assisted replies, and suggest cleanup automations with strict confirmation gates." version: "1.0.0" metadata: author: CoWork OS Contributors <info@coworkosapp.com>
Triage Inbox Agent Today lanes, search mailbox evidence, prepare manual or AI-assisted replies, and suggest cleanup automations with strict confirmation gates.
| Name | Type | Required | Description | |---|---|---|---| | mode | select | No | Inbox manager mode | | message_limit | number | No | Maximum number of messages to inspect | | time_window | string | No | Lookback window (e.g., "24h", "3d") | | output_format | select | No | How to format the final report |
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
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…
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide…
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…
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,…
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.
Use when the user asks for a repository-wide or scoped-path security scan.