Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Transforms conversations and discussions into structured documentation pages in Notion.
AGPL-3.0Auto-check passed
Install Notion Knowledge Capture
$ npx skills add rongxinzy/RongxinAI --skill notion-knowledge-capture -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rongxinzy/RongxinAI notion-knowledge-capture --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .claude/skills && cp -r skills-src/MCPs/notion/skills/knowledge-capture .claude/skills/notion-knowledge-capture && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "notion-knowledge-capture" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/notion/skills/knowledge-capture into .claude/skills/notion-knowledge-capture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-knowledge-capture", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/notion/skills/knowledge-captureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add rongxinzy/RongxinAI --skill notion-knowledge-capture -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rongxinzy/RongxinAI notion-knowledge-capture --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .agents/skills && cp -r skills-src/MCPs/notion/skills/knowledge-capture .agents/skills/notion-knowledge-capture && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "notion-knowledge-capture" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/notion/skills/knowledge-capture into .agents/skills/notion-knowledge-capture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-knowledge-capture", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rongxinzy/RongxinAI --skill notion-knowledge-capture -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rongxinzy/RongxinAI notion-knowledge-capture --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/MCPs/notion/skills/knowledge-capture .cursor/skills/notion-knowledge-capture && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "notion-knowledge-capture" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/notion/skills/knowledge-capture into .cursor/skills/notion-knowledge-capture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-knowledge-capture", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/rongxinzy/RongxinAI.git --path MCPs/notion/skills/knowledge-capture--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add rongxinzy/RongxinAI --skill notion-knowledge-capture -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rongxinzy/RongxinAI notion-knowledge-capture --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/MCPs/notion/skills/knowledge-capture .gemini/skills/notion-knowledge-capture && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "notion-knowledge-capture" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/notion/skills/knowledge-capture into .gemini/skills/notion-knowledge-capture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-knowledge-capture", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install rongxinzy/RongxinAI notion-knowledge-captureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add rongxinzy/RongxinAI --skill notion-knowledge-capture -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .github/skills && cp -r skills-src/MCPs/notion/skills/knowledge-capture .github/skills/notion-knowledge-capture && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "notion-knowledge-capture" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/notion/skills/knowledge-capture into .github/skills/notion-knowledge-capture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-knowledge-capture", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rongxinzy/RongxinAI --skill notion-knowledge-capture -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rongxinzy/RongxinAI notion-knowledge-capture --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/MCPs/notion/skills/knowledge-capture .opencode/skills/notion-knowledge-capture && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "notion-knowledge-capture" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/MCPs/notion/skills/knowledge-capture into .opencode/skills/notion-knowledge-capture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-knowledge-capture", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
notion-knowledge-capture- GitHub stars
- 154
- Used in
- 2 other repos
- Token cost
- ~1.8k tokens
- SKILL.md length
- 580 words
- Files
- 14
- Skills in repo
- 94
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Transforms conversations and discussions into structured documentation pages in Notion.
- Works in 6 steps: Identify content to capture → Determine content type → Structure the content → …
- SKILL.md covers Quick Start, Knowledge Capture Workflow, Content Types and Destination Patterns, plus 8 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Notion Knowledge Capture is an agent skill from rongxinzy/RongxinAI. Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 16 other files (for example `evaluations/README.md`, `evaluations/conversation-to-wiki.json` and `evaluations/decision-record.json`).
It works with Notion. The repository describes itself as: An all-in-one local AI Agent workspace with a fully self-developed stack. The licence is AGPL-3.0.
Example prompts
- “Use the notion-knowledge-capture skill to transform conversations and discussions into structured documentation pages in Notion”
- “/notion-knowledge-capture”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9c64865. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Notion Knowledge Capture loads about 1.8k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 580 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from rongxinzy/RongxinAI at commit 9c64865, republished under its AGPL-3.0 licence (© rongxinzy). 580 words, ~1,794 tokens.
Download SKILL.mdSave it as
.claude/skills/notion-knowledge-capture/SKILL.md (or your agent's skills folder). This skill also uses 13 other files; get the full folder from GitHub.- name
- notion-knowledge-capture
- description
- Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.
Knowledge Capture
Transforms conversations, discussions, and insights into structured documentation in your Notion workspace. Captures knowledge from chat context, formats it appropriately, and saves it to the right location with proper organization and linking.
Quick Start
When asked to save information to Notion:
- Extract content: Identify key information from conversation context
- Structure information: Organize into appropriate documentation format
- Determine location: Use
Notion:notion-searchto find appropriate wiki page/database - Create page: Use
Notion:notion-create-pagesto save content - Make discoverable: Link from relevant hub pages, add to databases, or update wiki navigation so others can find it
Knowledge Capture Workflow
Step 1: Identify content to capture
From conversation context, extract:
- Key concepts and definitions
- Decisions made and rationale
- How-to information and procedures
- Important insights or learnings
- Q&A pairs
- Examples and use casesStep 2: Determine content type
Classify the knowledge:
- Concept/Definition
- How-to Guide
- Decision Record
- FAQ Entry
- Meeting Summary
- Learning/Post-mortem
- Reference DocumentationStep 3: Structure the content
Format appropriately based on content type:
- Use templates for consistency
- Add clear headings and sections
- Include examples where helpful
- Add relevant metadata
- Link to related pagesStep 4: Determine destination
Where to save:
- Wiki page (general knowledge base)
- Specific project page (project-specific knowledge)
- Documentation database (structured docs)
- FAQ database (questions and answers)
- Decision log (architecture/product decisions)
- Team wiki (team-specific knowledge)Step 5: Create the page
Use Notion:notion-create-pages:
- Set appropriate title
- Use structured content from template
- Set properties if in database
- Add tags/categories
- Link to related pagesStep 6: Make content discoverable
Link the new page so others can find it:
1. Update hub/index pages:
- Add link to wiki table of contents page
- Add link from relevant project page
- Add link from category/topic page (e.g., "Engineering Docs")
2. If page is in a database:
- Set appropriate tags/categories
- Set status (e.g., "Published")
- Add to relevant views
3. Optionally update parent page:
- If saved under a project, add to project's "Documentation" section
- If in team wiki, ensure it's linked from team homepage
Example:
Notion:notion-update-page
page_id: "team-wiki-homepage-id"
command: "insert_content_after"
selection_with_ellipsis: "## How-To Guides..."
new_str: "- <mention-page url='...'>How to Deploy to Production</mention-page>"This step ensures the knowledge doesn't become "orphaned" - it's properly connected to your workspace's navigation structure.
Content Types
Choose appropriate structure based on content:
Concept: Overview → Definition → Characteristics → Examples → Use Cases → Related How-To: Overview → Prerequisites → Steps (numbered) → Verification → Troubleshooting → Related Decision: Context → Decision → Rationale → Options Considered → Consequences → Implementation FAQ: Short Answer → Detailed Explanation → Examples → When to Use → Related Questions Learning: What Happened → What Went Well → What Didn't → Root Causes → Learnings → Actions
Destination Patterns
General Wiki: Standalone page → add to index → tag → link from related pages
Project Wiki: Child of project page → link from project overview → tag with project name
Documentation Database: Use properties (Title, Type, Category, Tags, Last Updated, Owner)
Decision Log Database: Use properties (Decision, Date, Status, Domain, Deciders, Impact)
FAQ Database: Use properties (Question, Category, Tags, Last Reviewed, Useful Count)
See reference/database-best-practices.md for database selection guide and individual schema files.
Content Extraction from Conversations
Chat Discussion: Key points, conclusions, resources, action items, Q&A
Problem-Solving: Problem statement, approaches tried, solution, why it worked, future considerations
Knowledge Sharing: Concept explained, examples, best practices, common pitfalls, resources
Decision Discussion: Question, options, trade-offs, decision, rationale, next steps
Formatting Best Practices
Structure: Use # (title), ## (sections), ### (subsections) consistently
Writing: Start with overview, use bullets, keep paragraphs short, add examples
Linking: Link related pages, mention people, reference resources, create bidirectional links
Metadata: Include date, author, tags, status
Searchability: Clear titles, natural keywords, common search tags, image alt-text
Show full SKILL.md (217 more words)Show less
Indexing and Organization
Wiki Index: Organize by sections (Getting Started, How-To Guides, Reference, FAQs, Decisions) with page links
Category Pages: Create landing pages with overview, doc links, and recent updates
Tagging Strategy: Use consistent tags for technology/tools, topics, audience, and status
Update Management
Create New: Content is substantive (>2 paragraphs), will be referenced multiple times, part of knowledge base, needs independent discovery
Update Existing: Adding to existing topic, correcting info, expanding concept, updating for changes
Versioning: Add update history section for significant changes (date, author, what changed, why)
Best Practices
- Capture promptly: Document while context is fresh
- Structure consistently: Use templates for similar content
- Link extensively: Connect related knowledge
- Write for discovery: Use searchable titles and tags
- Include context: Why this matters, when to use
- Add examples: Concrete examples aid understanding
- Maintain: Review and update periodically
- Get feedback: Ask if documentation is helpful
Advanced Features
Documentation databases: See reference/database-best-practices.md for database schema patterns.
Common Issues
"Not sure where to save": Default to general wiki, can move later "Content is fragmentary": Group related fragments into cohesive doc "Already exists": Search first, update existing if appropriate "Too informal": Clean up language while preserving insights
Examples
See examples/ for complete workflows:
- examples/conversation-to-faq.md - FAQ from Q&A
- examples/decision-capture.md - Decision record
- examples/how-to-guide.md - How-to from discussion
© rongxinzy, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 13 other files in MCPs/notion/skills/knowledge-capture of rongxinzy/RongxinAI.
- SKILL.md
- evaluations/README.md
- evaluations/conversation-to-wiki.json
- evaluations/decision-record.json
- examples/conversation-to-faq.md
- examples/decision-capture.md
- examples/how-to-guide.md
- reference/database-best-practices.md
- reference/decision-log-database.md
- reference/documentation-database.md
- reference/faq-database.md
- reference/how-to-guide-database.md
- reference/learning-database.md
- reference/team-wiki-database.md
Open the folder on GitHubat commit 9c64865
Used in 2 other repositories
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in rongxinzy/RongxinAI, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Notion Knowledge Capture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Notion Knowledge Capture this skillrongxinzy/RongxinAI | 154 | 2 repos | ~1.8k | Automated safety check: Pass | AGPL-3.0 | |
| Code Design Rationale Investigatorcursor/plugins | 11k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Xiaohei Chinese Article Illustrationshelloianneo/ian-xiaohei-illustrations | 12k | 3 repos | ~470 | Automated safety check: Warn | MIT | |
| ComposioComposioHQ/composio | 30k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Debug SkillTypeCellOS/BlockNote | 10k | — | ~1.8k | Automated safety check: Pass | Custom licence | |
| Marketing PlanNexus-JPF/note-companion | 870 | 5 repos | ~5.2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Xiaohei Chinese Article Illustrations
helloianneo/ian-xiaohei-illustrations
Plans and generates 16:9 hand-drawn illustrations for Chinese articles on a white background, with a recurring black character and a few red, orange and blue handwritten notes.
Composio
ComposioHQ/composio
Route and complete Composio work across Composio For You and Composio Platform.
Debug Skill
TypeCellOS/BlockNote
Instructions for navigating and debugging BlockNote in a browser.
Marketing Plan
Nexus-JPF/note-companion
When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.
Docs Skill
TypeCellOS/BlockNote
Conventions and verification workflow for writing and restructuring the documentation site (docs/content).
More from rongxinzy/RongxinAI
All 94 skills in this repoSaaS Metrics Coach
rongxinzy/RongxinAI
SaaS financial health advisor. An agent skill from rongxinzy/RongxinAI.
Churn Prevention
rongxinzy/RongxinAI
Reduce voluntary and involuntary churn through cancel flow design, save offers, exit surveys, and dunning sequences.
Presentation Studio
rongxinzy/RongxinAI
The only skill for creating a new PowerPoint deck. An agent skill from rongxinzy/RongxinAI.
Zhiyuan Expert Manager
rongxinzy/RongxinAI
ZhiYuan Agent expert package lifecycle manager for the pi engine.
Ziwei Doushu
rongxinzy/RongxinAI
Professional Ziwei Doushu consultation skill with an offline calculation engine.
Lark Mail
rongxinzy/RongxinAI
飞书邮箱：Use when user mentions 起草邮件、写邮件、草稿、发送/回复/转发邮件、查阅邮件、看邮件、搜索邮件、邮件文件夹、邮件标签、邮件联系人、监听新邮件、邮件收信规则等；use for mail/email intent only.
Related
Works with
Questions about Notion Knowledge Capture
What does Notion Knowledge Capture do?
Transforms conversations and discussions into structured documentation pages in Notion. Notion Knowledge Capture is an agent skill from rongxinzy/RongxinAI. Transforms conversations and discussions into structured documentation pages in Notion.
How do I install Notion Knowledge Capture in Claude Code?
Run `npx skills add rongxinzy/RongxinAI --skill notion-knowledge-capture -a claude-code`. Or copy the skill folder (MCPs/notion/skills/knowledge-capture in rongxinzy/RongxinAI) into .claude/skills/notion-knowledge-capture in your project. Claude Code loads it when a task matches its description.
How do I install Notion Knowledge Capture in Codex?
Run `npx skills add rongxinzy/RongxinAI --skill notion-knowledge-capture -a codex`. Or copy the skill folder (MCPs/notion/skills/knowledge-capture in rongxinzy/RongxinAI) into .agents/skills/notion-knowledge-capture in your project. Codex loads it when a task matches its description.
Can I use Notion Knowledge Capture in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rongxinzy/RongxinAI --skill notion-knowledge-capture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/notion-knowledge-capture, .gemini/skills/notion-knowledge-capture, .github/skills/notion-knowledge-capture and .opencode/skills/notion-knowledge-capture in your project.
What does Notion Knowledge Capture need to run?
SKILL.md names no scripts, command-line tools or credentials: Notion Knowledge Capture is instructions for the agent only.
Does Notion Knowledge Capture access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Notion Knowledge Capture safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Notion Knowledge Capture use?
Notion Knowledge Capture is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Notion Knowledge Capture use?
About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Notion Knowledge Capture?
Skills that share tags, products or a category with Notion Knowledge Capture: Code Design Rationale Investigator (cursor/plugins, 11k stars), Xiaohei Chinese Article Illustrations (helloianneo/ian-xiaohei-illustrations, 12k stars), Composio (ComposioHQ/composio, 30k stars) and Debug Skill (TypeCellOS/BlockNote, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Notion Knowledge Capture?
rongxinzy (a GitHub organization) maintains it in rongxinzy/RongxinAI, which has 154 GitHub stars. The repository holds 94 skills in this directory. The repository was last updated on October 10, 2026.
Source: rongxinzy/RongxinAI on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.