Skip to content

Dianel555/DSkills / skills/exa

High-precision semantic search and content retrieval via Exa API. Use when: (1) Deep research requiring semantic understanding, (2) Code documentation and examples lookup, (3) Company/professional research, (4) AI-powered comprehensive research tasks, (5) URL content extraction with structured output. Triggers: "research", "find papers", "code examples", "company info", "LinkedIn profiles", "deep analysis". Differentiator: Exa excels at semantic/neural search while grok-search is better for real-time news and general web content.

references/synthesis.md

View on GitHub
# Synthesizing Research into Narrative

When the task calls for a narrative answer (not a list or table), this file covers how to synthesize findings from multiple sources into a coherent, well-structured response.

## When Synthesis Applies

Synthesis is the right output format when:
- The user is asking "what do people say about X" or "what's the current state of Y"
- The answer requires integrating perspectives from multiple sources
- The output should be prose with citations, not a table of entities

## Structure

### Lead with the answer

Put the core finding or conclusion first. The user should get value from the first paragraph alone.

### Organize by theme, not by source

Bad: "Source A says X. Source B says Y. Source C says Z."
Good: "Theme 1: [insight supported by A, B]. Theme 2: [insight supported by C, with counterpoint from A]."

### Surface disagreement explicitly

When credible sources disagree, don't collapse to consensus. Present both sides with their evidence:
- "On [topic], [position A] (supported by [sources]) vs [position B] (supported by [sources]). [When each applies or why they diverge]."

### Include confidence signals

- How many independent sources support a claim?
- How fresh is the evidence?
- Are the sources practitioners or commentators?

## Thematic Clustering

When dealing with many reactions or perspectives (e.g. "what are people saying about X"):

1. Read through all results
2. Identify recurring themes (not just topics -- themes have a stance or direction)
3. Group results by theme
4. For each theme: state the theme, cite 2-3 representative sources, note the volume
5. Flag outlier themes that appear only once but carry important signal

## Citation Practice

- Every factual claim gets a source URL
- Prefer inline citations: "Engineers report 3x latency reduction ([source](url))"
- For quotes, include the exact text and attribute it

## Common Mistakes

- **Source-by-source summaries**: Feels comprehensive but is unreadable and doesn't synthesize
- **Collapsing disagreement**: Picking a winner instead of presenting the landscape
- **Missing recency**: Treating 2023 sources as current for fast-moving topics
- **Over-synthesis**: Producing a full essay when the user asked a narrow question
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexUnverifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall