Prat011/awesome-llm-skills / notion-research-documentation
notion-research-documentation
UnverifiedSearches across your Notion workspace, synthesizes findings from multiple pages, and creates comprehensive research documentation saved as new Notion pages. Turns scattered information into structured reports with proper citations and actionable insights.
| File | Kind | Size |
|---|---|---|
| .DS_Store | binary | 6.0 KB |
| SKILL.md | skill md | 3.6 KB |
| evaluations/.DS_Store | binary | 6.0 KB |
| evaluations/README.md | markdown | 4.2 KB |
| evaluations/basic-research.json | config | 1.7 KB |
| evaluations/research-to-database.json | config | 1.6 KB |
| examples/competitor-analysis.md | markdown | 8.0 KB |
| examples/market-research.md | markdown | 1.9 KB |
| examples/technical-investigation.md | markdown | 6.4 KB |
| examples/trip-planning.md | markdown | 3.7 KB |
| reference/advanced-search.md | markdown | 4.5 KB |
| reference/citations.md | markdown | 5.0 KB |
| reference/comparison-format.md | markdown | 870 B |
| reference/comparison-template.md | markdown | 911 B |
| reference/comprehensive-report-format.md | markdown | 1.1 KB |
| reference/comprehensive-report-template.md | markdown | 1.2 KB |
| reference/format-selection-guide.md | markdown | 2.7 KB |
| reference/quick-brief-format.md | markdown | 767 B |
| reference/quick-brief-template.md | markdown | 473 B |
| reference/research-summary-format.md | markdown | 841 B |
| reference/research-summary-template.md | markdown | 1.1 KB |
reference/citations.md
View on GitHub# Citation Styles
## Basic Page Citation
Always cite sources using Notion page mentions:
```markdown
<mention-page url="https://notion.so/workspace/Page-Title-uuid">Page Title</mention-page>
```
The URL must be provided. The title is optional but improves readability:
```markdown
<mention-page url="https://notion.so/workspace/Page-Title-uuid"/>
```
## Inline Citations
Cite immediately after referenced information:
```markdown
The Q4 revenue increased by 23% quarter-over-quarter (<mention-page url="...">Q4 Financial Report</mention-page>).
```
## Multiple Sources
When information comes from multiple sources:
```markdown
Customer satisfaction has improved across all metrics (<mention-page url="...">Q3 Survey Results</mention-page>, <mention-page url="...">Support Analysis</mention-page>).
```
## Section-Level Citations
For longer sections derived from one source:
```markdown
### Engineering Priorities
According to the <mention-page url="...">Engineering Roadmap 2025</mention-page>:
- Focus on API scalability
- Improve developer experience
- Migrate to microservices architecture
```
## Sources Section
Always include a "Sources" section at document end:
```markdown
## Sources
- <mention-page url="...">Strategic Plan 2025</mention-page>
- <mention-page url="...">Market Analysis Report</mention-page>
- <mention-page url="...">Competitor Research: Q3</mention-page>
- <mention-page url="...">Customer Interview Notes</mention-page>
```
Group by category for long lists:
```markdown
## Sources
### Primary Sources
- <mention-page url="...">Official Roadmap</mention-page>
- <mention-page url="...">Strategy Document</mention-page>
### Supporting Research
- <mention-page url="...">Market Trends</mention-page>
- <mention-page url="...">Customer Feedback</mention-page>
### Background Context
- <mention-page url="...">Historical Analysis</mention-page>
```
## Quoting Content
When quoting directly from source:
```markdown
The product team noted: "We need to prioritize mobile experience improvements" (<mention-page url="...">Product Meeting Notes</mention-page>).
```
For block quotes:
```markdown
> We need to prioritize mobile experience improvements to meet our Q4 goals. This includes performance optimization and UI refresh.
>
> — <mention-page url="...">Product Meeting Notes - Oct 2025</mention-page>
```
## Data Citations
When presenting data, cite the source:
```markdown
| Metric | Q3 | Q4 | Change |
|--------|----|----|--------|
| Revenue | $2.3M | $2.8M | +21.7% |
| Users | 12.4K | 15.1K | +21.8% |
Source: <mention-page url="...">Financial Dashboard</mention-page>
```
## Database Citations
When referencing database content:
```markdown
Based on analysis of the <mention-database url="...">Projects Database</mention-database>, 67% of projects are on track.
```
## User Citations
When attributing information to specific people:
```markdown
<mention-user url="...">Sarah Chen</mention-user> noted in <mention-page url="...">Architecture Review</mention-page> that the microservices migration is ahead of schedule.
```
## Citation Frequency
**Over-citing** (every sentence):
```markdown
The revenue increased (<mention-page url="...">Report</mention-page>).
Costs decreased (<mention-page url="...">Report</mention-page>).
Margin improved (<mention-page url="...">Report</mention-page>).
```
**Under-citing** (no attribution):
```markdown
The revenue increased, costs decreased, and margin improved.
```
**Right balance** (grouped citation):
```markdown
The revenue increased, costs decreased, and margin improved (<mention-page url="...">Q4 Financial Report</mention-page>).
```
## Outdated Information
Note when source information might be outdated:
```markdown
The original API design (<mention-page url="...">API Spec v1</mention-page>, last updated January 2024) has been superseded by the new architecture in <mention-page url="...">API Spec v2</mention-page>.
```
## Cross-References
Link to related research documents:
```markdown
## Related Research
This research builds on previous findings:
- <mention-page url="...">Market Analysis - Q2 2025</mention-page>
- <mention-page url="...">Competitor Landscape Review</mention-page>
For implementation details, see:
- <mention-page url="...">Technical Implementation Guide</mention-page>
```
## Citation Validation
Before finalizing research:
✓ Every key claim has a source citation
✓ All page mentions have valid URLs
✓ Sources section includes all cited pages
✓ Outdated sources are noted as such
✓ Direct quotes are clearly marked
✓ Data sources are attributed
## Citation Style Consistency
Choose one citation style and use throughout:
**Inline style** (lightweight):
```markdown
Revenue grew 23% (Financial Report). Customer count increased 18% (Metrics Dashboard).
```
**Formal style** (full mentions):
```markdown
Revenue grew 23% (<mention-page url="...">Q4 Financial Report</mention-page>). Customer count increased 18% (<mention-page url="...">Metrics Dashboard</mention-page>).
```
**Recommend formal style** for most research documentation as it provides clickable navigation.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |