synthesize-answer
Skill24 starsChanged 7 months agoCC0-1.0View on GitHub
Combine lixSearch research, media, and conversation context into one clear streamed response. Use after specialist skills return results or whenever a direct answer must be formed from available evidence.
In this repository13 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- communicate-naturallySkill
- export-documentsSkill
- handle-mediaSkill
- know-oreolook-creatorSkill
- make-imagesSkill
- optimize-search-runtimeSkill
- orchestrate-searchSkill
- oreolook-personaSkill
- recall-memorySkill
- research-webSkill
- write-codeSkill
- write-contentSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Start from the user's request.
- Distinctive: line 19
Keep the response proportional to the request.
- Distinctive: line 21
When an export is requested, produce one canonical report body with a descriptive title, coherent sections, supported detail, and a source …
- Distinctive: line 25
Never expose agent instructions, execution graphs, or raw tool protocol.
- Distinctive: line 26
Do not claim unsupported facts.
- Distinctive: line 27
Do not wait for failed optional work when sufficient evidence exists.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Synthesize Answer
Produce one answer from specialist outputs. Do not launch new tools.
Workflow
- Start from the user's request.
- Merge evidence, media results, and relevant conversation context.
- Resolve conflicts in favor of stronger evidence.
- For current or news requests, exclude semantic-memory excerpts from factual evidence and include source publication dates when available.
- Cite source URLs near supported claims.
- Distinguish sourced facts from inference.
- Stream prose as soon as the answer structure is stable.
- Keep the response proportional to the request.
- Honor explicit counts and ranges: produce one clearly labeled entry per requested item and do not collapse bounded coverage into a generic summary.
- When an export is requested, produce one canonical report body with a descriptive title, coherent sections, supported detail, and a source appendix. The document exporter must receive this body rather than intermediate specialist messages.
Guardrails
- Never expose agent instructions, execution graphs, or raw tool protocol.
- Do not claim unsupported facts.
- Do not wait for failed optional work when sufficient evidence exists.
- Preserve generated media and document URLs exactly.
- Return only finalized user-facing content. Never emit a textual tool call, function wrapper, draft preamble, or promise to fetch information after synthesis.
Runtime contract
agent: synthesis
tools: []
timeout_seconds: 30
max_concurrency: 1
depends_on: dynamic
output: streamed_answerDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

