Prat011/awesome-llm-skills / notion-knowledge-capture
notion-knowledge-capture
VerifiedTransforms 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.1 KB |
| evaluations/README.md | markdown | 3.4 KB |
| evaluations/conversation-to-wiki.json | config | 2.0 KB |
| evaluations/decision-record.json | config | 2.2 KB |
| examples/conversation-to-faq.md | markdown | 15.9 KB |
| examples/decision-capture.md | markdown | 3.5 KB |
| examples/how-to-guide.md | markdown | 2.8 KB |
| reference/database-best-practices.md | markdown | 2.8 KB |
| reference/decision-log-database.md | markdown | 2.0 KB |
| reference/documentation-database.md | markdown | 2.7 KB |
| reference/faq-database.md | markdown | 2.0 KB |
| reference/how-to-guide-database.md | markdown | 1.2 KB |
| reference/learning-database.md | markdown | 1.3 KB |
| reference/team-wiki-database.md | markdown | 927 B |
reference/database-best-practices.md
View on GitHub# Database Best Practices
General guidance for creating and maintaining knowledge capture databases.
## Core Principles
### 1. Keep It Simple
- Start with core properties
- Add more only when needed
- Don't over-engineer
### 2. Use Consistent Naming
- Title property for main identifier
- Status for lifecycle tracking
- Tags for flexible categorization
- Owner for accountability
### 3. Include Metadata
- Created/Updated timestamps
- Owner or maintainer
- Last reviewed dates
- Status indicators
### 4. Enable Discovery
- Use tags liberally
- Create helpful views
- Link related content
- Use clear titles
### 5. Plan for Scale
- Consider filters early
- Use relations for connections
- Think about search
- Organize with categories
## Creating a Database
### Using `Notion:notion-create-database`
Example for documentation database:
```javascript
{
"parent": {"page_id": "wiki-page-id"},
"title": [{"text": {"content": "Team Documentation"}}],
"properties": {
"Type": {
"select": {
"options": [
{"name": "How-To", "color": "blue"},
{"name": "Concept", "color": "green"},
{"name": "Reference", "color": "gray"},
{"name": "FAQ", "color": "yellow"}
]
}
},
"Category": {
"select": {
"options": [
{"name": "Engineering", "color": "red"},
{"name": "Product", "color": "purple"},
{"name": "Design", "color": "pink"}
]
}
},
"Tags": {"multi_select": {"options": []}},
"Owner": {"people": {}},
"Status": {
"select": {
"options": [
{"name": "Draft", "color": "gray"},
{"name": "Final", "color": "green"},
{"name": "Deprecated", "color": "red"}
]
}
}
}
}
```
### Fetching Database Schema
Before creating pages, always fetch database to get schema:
```
Notion:notion-fetch
id: "database-url-or-id"
```
This returns the exact property names and types to use.
## Database Selection Guide
| Need | Use This Database |
|------|-------------------|
| General documentation | [Documentation Database](documentation-database.md) |
| Track decisions | [Decision Log](decision-log-database.md) |
| Q&A knowledge base | [FAQ Database](faq-database.md) |
| Team-specific content | [Team Wiki](team-wiki-database.md) |
| Step-by-step guides | [How-To Guide Database](how-to-guide-database.md) |
| Incident/project learnings | [Learning Database](learning-database.md) |
## Tips
1. **Start with general documentation database** - most flexible
2. **Add specialized databases** as needs emerge (FAQ, Decisions)
3. **Use relations** to connect related docs
4. **Create views** for common use cases
5. **Review properties** quarterly - remove unused ones
6. **Document the schema** in database description
7. **Train team** on property usage and conventions
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |