research-management
Manage research documentation in workspace platforms. Structures research findings, sources, and analysis in organized research databases.
What this skill does
# Research & Documentation Enables comprehensive research workflows: search for information across your Notion workspace, fetch and analyze relevant pages, synthesize findings, and create well-structured documentation. ## Quick Start When asked to research and document a topic: 1. **Search for relevant content**: Use `Notion:notion-search` to find pages 2. **Fetch detailed information**: Use `Notion:notion-fetch` to read full page content 3. **Synthesize findings**: Analyze and combine information from multiple sources 4. **Create structured output**: Use `Notion:notion-create-pages` to write documentation ## Research Workflow ### Step 1: Search for relevant information ``` Use Notion:notion-search with the research topic Filter by teamspace if scope is known Review search results to identify most relevant pages ``` ### Step 2: Fetch page content ``` Use Notion:notion-fetch for each relevant page URL Collect content from all relevant sources Note key findings, quotes, and data points ``` ### Step 3: Synthesize findings Analyze the collected information: - Identify key themes and patterns - Connect related concepts across sources - Note gaps or conflicting information - Organize findings logically ### Step 4: Create structured documentation Use the appropriate documentation template (see [reference/format-selection-guide.md](reference/format-selection-guide.md)) to structure output: - Clear title and executive summary - Well-organized sections with headings - Citations linking back to source pages - Actionable conclusions or next steps ## Output Formats Choose the appropriate format based on request: **Research Summary**: See [reference/research-summary-format.md](reference/research-summary-format.md) **Comprehensive Report**: See [reference/comprehensive-report-format.md](reference/comprehensive-report-format.md) **Quick Brief**: See [reference/quick-brief-format.md](reference/quick-brief-format.md) ## Best Practices 1. **Cast a wide net first**: Start with broad searches, then narrow down 2. **Cite sources**: Always link back to source pages using mentions 3. **Verify recency**: Check page last-edited dates for current information 4. **Cross-reference**: Validate findings across multiple sources 5. **Structure clearly**: Use headings, bullets, and formatting for readability ## Page Placement By default, create research documents as standalone pages. If the user specifies: - A parent page → use `page_id` parent - A database → fetch the database first, then use appropriate `data_source_id` - A teamspace → create in that context ## Advanced Features **Search filtering**: See [reference/advanced-search.md](reference/advanced-search.md) **Citation styles**: See [reference/citations.md](reference/citations.md) ## Common Issues **"No results found"**: Try broader search terms or different teamspaces **"Too many results"**: Add filters or search within specific pages **"Can't access page"**: User may lack permissions, ask them to verify access ## Examples See [examples/](examples/) for complete workflow demonstrations: - [examples/market-research.md](examples/market-research.md) - Researching market trends - [examples/technical-investigation.md](examples/technical-investigation.md) - Technical deep-dive - [examples/competitor-analysis.md](examples/competitor-analysis.md) - Multi-source synthesis
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.