メニュー
Assists with writing and improving project documentation including READMEs, architecture docs, API references, and user guides. Use when the user wants to write docs, update a README, document an API, or create a user guide.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Process a meeting transcript to extract action items (with owners and due dates), risks, follow-up questions, and a concise summary. Optionally record decisions and ingest the output into the vault.
Search and synthesize knowledge from SecondBrain vault. Use when the user asks about their projects, past decisions, meetings, people, goals, or anything that might be in their personal knowledge base. Triggers on questions like "what do I know about X", "find notes on Y", "what did we decide about Z", "remind me about", "what's the status of".
Answer data and analytics questions using SecondBrain DataAgent — SQL execution, workflow runs, and LLM synthesis over the knowledge database. Use for questions about metrics, counts, trends, comparisons, or anything that sounds like "how many", "show me the data", "analyse", "what are the trends in".
Extract decisions from a markdown file and help record them in the SecondBrain decision catalog with proper namespace keys.
Answer a research question using closed-corpus grounded reasoning with evidence chains and citations. Use for deep research questions that need traceable evidence, cross-document synthesis, or when the user asks to "research", "investigate", or "dig into" something thoroughly.
Ingest a file or directory into SecondBrain vault — parse, chunk, embed, and index it for future retrieval. Use when the user wants to add content to their knowledge base.
| name | doc-writer |
| description | Assists with writing and improving project documentation including READMEs, architecture docs, API references, and user guides. Use when the user wants to write docs, update a README, document an API, or create a user guide. |
| version | 1.0.0 |
| triggers | ["write documentation","update the README","document this","create a user guide","write API docs","improve the docs"] |
| negative_triggers | ["delete docs","remove documentation"] |
| allowed_tools | [] |
| required_tools | [] |
| examples | ["Write or improve a README, API reference, user guide, architecture note, or changelog."] |
| tests | ["sb skills validate --path skills --strict"] |
| performance | {"notes":"Best for documentation drafting, structure review, and stale reference cleanup."} |
Help the user produce clear, well-structured project documentation that follows best practices.
# Project Name
One-line description.
## Quick Start
Installation and first-run instructions.
## Usage
Core commands and workflows.
## Configuration
Key settings and environment variables.
## Architecture
High-level design overview.
## Contributing
How to contribute.
# API Reference
## `function_name(param1, param2)`
Description of what it does.
**Parameters:**
- `param1` (type): Description
- `param2` (type): Description
**Returns:** Description of return value
**Example:**
(code block)
| Symptom | Cause | Fix |
|---|---|---|
| Docs feel too long | No clear structure | Add table of contents, use headings |
| Examples don't work | Outdated code | Test examples against current codebase |
| Missing context | Assumed knowledge | Add prerequisites section |