メニュー
Use when the operator asks for a written report, briefing, executive summary, customer deliverable, engagement write-up, or PoC findings doc. Produces PANW Cortex-style two-section output (executive + technical) with consistent formatting.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when … (one-line trigger: name the task, its inputs, and the situation it applies to). This sentence is what the model reads to decide whether to load the skill.
Project-aware sync between a GitHub repo, its Things 3 project, and its Obsidian vault subdirectory. The repo NAME is the common key across all three surfaces. Use whenever an agent needs to create Things 3 todos tied to a repo, onboard a repo, or mirror a repo's key markdown into the vault. Replaces ad-hoc add_todo calls that silently land in the Inbox. Trigger on "docsync", "sync this repo to Things", "create a todo for {repo}", sprint planning that emits tasks, or any repo-scoped task capture.
Analyze an Obsidian vault note and suggest enrichment — improved/missing frontmatter, 3-5 wikilinks to related vault notes, the right MOC to file it under, and a 1-sentence MOC summary. Use when the user asks to "enrich this note", wants frontmatter/tag/link/MOC suggestions for a note, or is triaging a _wip/ note. Suggests only; never overwrites frontmatter without confirmation.
Generate a concise session-handoff summary — TL;DR, what changed, decisions taken, open items, and context for the next session — and optionally save it to the Obsidian vault _wip/ inbox via the capture skill. Use at the end of a working session, when switching context, or when the user says "handoff", "hand this off", "wrap up", "session summary", or "/handoff". Never include raw credentials or PII; use surrogates.
Capture research findings, slash-command output, decisions, or other substantive session output as a structured Obsidian note in Henry's vault. Use this skill automatically whenever a session produces output with lasting reference value — research conclusions, comparison/evaluation results, command output worth keeping, architecture decisions, or notable findings — even if the user does not explicitly say "save this to my vault." Trigger on phrases like "capture this," "save to my vault," "note this," "vault this," and as the default RECORD/REFLECT step in autonomous loops. This is the canonical way to write vault notes; do not hand-roll frontmatter or write notes ad hoc when this skill applies.
Onboard a GitHub repo as a vault dev-project — resolve (or create, with confirmation) its Things 3 project, then scaffold Github-Projects/<repo>/ with the _MOC <repo>.md binding anchor via the vault-os MCP tools. Use when starting work on a new repo, or when the user says "onboard <repo>", "project-init <repo>", "set up docsync for <repo>", or before the first /sync-docs on a repo. One-time per repo; afterward docsync and /sync-docs take the deterministic binding path automatically.
| name | report-writeup |
| description | Use when the operator asks for a written report, briefing, executive summary, customer deliverable, engagement write-up, or PoC findings doc. Produces PANW Cortex-style two-section output (executive + technical) with consistent formatting. |
Default deliverable shape. Used for engagement reports, PoC writeups, customer briefings, internal handoffs.
iocs-extract skill output.### Detection: <short name>
**ATT&CK:** Txxxx (Technique name)
**Severity:** High
**Confidence:** Medium
```xql
dataset = <source>
| filter <condition>
| comp count() as hits by <dimension>
| filter hits > <threshold>
False-positive risks: Tuning notes:
## Defaults
- **Length:** technical section as long as needed; executive ≤ 150 words.
- **Naming:** filename `engagement-<id>-report-YYYY-MM-DD.md`.
- **Storage:** lands in `$OBSIDIAN_VAULT/40-Findings/` via `/handoff` slash command (Phase 8).
- **Sanitization for cloud delivery:** when generating via Claude Code with sensitive data, route through `safeclaude` (DontFeedTheAI proxy, Phase 7).