Agent skill
notion-research-documentation
Research across Notion and synthesize into structured documentation; use when gathering info from multiple Notion sources to produce briefs, comparisons, or reports with citations.
Install this agent skill to your Project
npx add-skill https://github.com/yurake/skills/tree/main/.curated/notion-research-documentation
Metadata
Additional technical details for this skill
- short description
- Research Notion content and produce briefs/reports
SKILL.md
Research & Documentation
Pull relevant Notion pages, synthesize findings, and publish clear briefs or reports (with citations and links to sources).
Quick start
- Find sources with
Notion:notion-searchusing targeted queries; confirm scope with the user. - Fetch pages via
Notion:notion-fetch; note key sections and capture citations (reference/citations.md). - Choose output format (brief, summary, comparison, comprehensive report) using
reference/format-selection-guide.md. - Draft in Notion with
Notion:notion-create-pagesusing the matching template (quick, summary, comparison, comprehensive). - Link sources and add a references/citations section; update as new info arrives with
Notion:notion-update-page.
Workflow
0) If any MCP call fails because Notion MCP is not connected, pause and set it up:
- Add the Notion MCP:
codex mcp add notion --url https://mcp.notion.com/mcp
- Enable remote MCP client:
- Set
[features].rmcp_client = trueinconfig.tomlor runcodex --enable rmcp_client
- Set
- Log in with OAuth:
codex mcp login notion
After successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.
1) Gather sources
- Search first (
Notion:notion-search); refine queries, and ask the user to confirm if multiple results appear. - Fetch relevant pages (
Notion:notion-fetch), skim for facts, metrics, claims, constraints, and dates. - Track each source URL/ID for later citation; prefer direct quotes for critical facts.
2) Select the format
- Quick readout → quick brief.
- Single-topic dive → research summary.
- Option tradeoffs → comparison.
- Deep dive / exec-ready → comprehensive report.
- See
reference/format-selection-guide.mdfor when to pick each.
3) Synthesize
- Outline before writing; group findings by themes/questions.
- Note evidence with source IDs; flag gaps or contradictions.
- Keep user goal in view (decision, summary, plan, recommendation).
4) Create the doc
- Pick the matching template in
reference/(brief, summary, comparison, comprehensive) and adapt it. - Create the page with
Notion:notion-create-pages; include title, summary, key findings, supporting evidence, and recommendations/next steps when relevant. - Add citations inline and a references section; link back to source pages.
5) Finalize & handoff
- Add highlights, risks, and open questions.
- If the user needs follow-ups, create tasks or a checklist in the page; link any task database entries if applicable.
- Share a short changelog or status using
Notion:notion-update-pagewhen updating.
References and examples
reference/— search tactics, format selection, templates, and citation rules (e.g.,advanced-search.md,format-selection-guide.md,research-summary-template.md,comparison-template.md,citations.md).examples/— end-to-end walkthroughs (e.g.,competitor-analysis.md,technical-investigation.md,market-research.md,trip-planning.md).
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
issue-create
GitHub Issue を作成する手順。依頼を受けたとき、.github/ISSUE_TEMPLATE の内容に応じてテンプレを選び、必須項目を埋めて GitHub MCP(issue_write/create)で Issue を作成する。
ci-fail-followup
PR 作成後に .github/workflows/ci.yml が失敗したときの対応手順。ローカルで pytest 全ケースを実行し、エラー有無で分岐。エラーがあれば修正して commit-push スキルでコミット・プッシュ、無ければ GitHub Actions のログを確認して原因を特定する。
review-rules
セッションの会話から恒久的な振る舞いルールを抽出し、AGENTS.md と突き合わせて追加すべきものを提示する。出力は rules と agents_md_patch の二部構成。
pr-create
PR 作成手順を自動化するためのガイド。依頼を受けたとき、または 参照しているTODOファイル の「PR 作成」以外が完了したタイミングでタイトル・本文整形、テンプレ適用、MCP での PR 作成を行う。
architecture-patterns
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
test-risk-analyzer
あらゆる言語/スタックで潜在バグリスクを洗い出し、追加すべきテストケースを提案する。未テストのエッジケース探索や安全性確認、カバレッジ強化のテスト案提示を求められたときに使用する。
Didn't find tool you were looking for?