--- title: "Agent-Log Knowledge Synthesizer: review, role & definition · Undominated.ai" canonical: https://undominated.ai/agents/voltagent-knowledge-synthesizer/ description: "Finds recurring patterns in an explicitly scoped set of agent logs and writes cited findings with counts derived from the actual files." --- # Agent-Log Knowledge Synthesizer: review, role & definition · Undominated.ai > Finds recurring patterns in an explicitly scoped set of agent logs and writes cited findings with counts derived from the actual files. [← Explore all agents](/agents/) AGENT DEVELOPMENT / VoltAgent # Agent-Log Knowledge Synthesizer Finds recurring patterns in an explicitly scoped set of agent logs and writes cited findings with counts derived from the actual files. Use this definition ↓Original source ↗ SOURCE REVIEW Reviewed 2026-09-21 Evidence 3 linked sources Publisher VoltAgent Licence MIT ↗ Revision 82b73821baa7 Read what was—and wasn’t—checked ↓ “Use when you need to mine recurring patterns from agent logs, session transcripts, and workflow history, then write grounded, evidence-cited findings that other agents or humans can act on.” VoltAgent · upstream description ↗ Our analysis follows below. 01 / THE REASONING ## Why this made the selection. - Stops on an empty or unspecified source scope and distinguishes recurring evidence from a single unconfirmed anecdote. - Provides a structured pattern/evidence/frequency/action record and explicitly forbids invented quantities or capabilities. ### A good fit for - Extracting repeated failure-and-recovery patterns from supplied agent or CI logs. - Updating a knowledge file without duplicating already recorded findings. ### Weigh up before choosing - It cannot run analytics jobs or query remote services with its declared file tools; inputs must be accessible files. - Its source-count confidence labels are heuristics, and independent files can still repeat the same underlying event. - Writing and editing the knowledge file changes shared project state; choose the destination and source scope explicitly. 02 / THE REVIEW RECORD ## What we actually inspected. Source review has boundaries. A clear record is more useful than a “safe” badge. ### Material inspected - categories/09-meta-orchestration/knowledge-synthesizer.md (complete original frontmatter and body; strict YAML duplicate-key check) - LICENSE (full applicable licence bytes and redistribution terms) - Current official host configuration documentation; exact source and licence SHA-256 recorded ### Our findings - The workflow rejects guessed counts and requires source references and a meaningful repetition threshold. - File counts do not prove independent events or causality. The confidence labels are a review heuristic. ### Not established by this review - This agent has not been executed or benchmarked. - Host discovery, configured tool availability, model behaviour and task outcomes were not runtime-tested. The review applies to the material and revision named here. A newer upstream release can change its behavior. 03 / PUT IT TO WORK ## Use the role in your project. Upstream setup instructions ↗ - Download the original knowledge-synthesizer.md with its full licence and attribution; inspect the complete instructions and tool scope before use. - Place the reviewed working copy at .claude/agents/knowledge-synthesizer.md. Delegate a bounded task by its frontmatter name in Claude Code; verify the agent is discovered before starting. - Check the declared tools and any model alias against the active host. The single definition does not install an upstream plugin, team, runtime or companion inputs. - Provide an explicit source glob or file list and the intended knowledge-file destination. The role must stop if no files match. - Supply any existing knowledge file so the agent can avoid duplicate entries. Keep credentials and unrelated private material out of the selected corpus. - Review the path-cited observations, actual source counts and independence assumptions before accepting recurring patterns. Single-source observations remain unconfirmed. ### Before you start - Accessible agent logs, session text or CI/workflow files in an explicit scope. - A chosen knowledge-file destination and permission to update it. ### Compatibility Claude Code ### Scoped file review and knowledge-file editing - Declared tools are Read, Write, Edit, Glob and Grep; no shell, browser or remote analytics tools are included. - Write/Edit are not technically confined to the intended knowledge file by this definition; host permissions enforce that boundary. ### Cost model The definition is reusable under its stated licence. The host, model and connected services have their own access and billing terms. THE COMPLETE REVIEWED DEFINITION ## Read it before you reuse it. Original source bytes, with attribution. Review the host-specific setup notes above. Copy definition ↗ [Download definition + licence ↗](/resources/agents/voltagent-knowledge-synthesizer/bundle.zip)[Raw Markdown ↗](/resources/agents/voltagent-knowledge-synthesizer/definition.md) --- name: knowledge-synthesizer description: "Use when you need to mine recurring patterns from agent logs, session transcripts, and workflow history, then write grounded, evidence-cited findings that other agents or humans can act on." tools: Read, Write, Edit, Glob, Grep model: sonnet --- You are a knowledge synthesis specialist. You read the artifacts a multi-agent system leaves behind — logs, session transcripts, error output, workflow records — and distill recurring patterns into a concise, evidence-backed knowledge file. You work only from what is in the files. You never invent metrics, counts, or outcomes you did not compute yourself. ## Scope and honesty rules - Your tools are `Read, Glob, Grep, Write, Edit`. You can search text, count occurrences, and write Markdown. You cannot train models, build a live knowledge graph, run analytics jobs, or query a service. Do not claim to. - Every pattern you report must cite concrete evidence: `path:line` references to the files it came from. - Report a pattern only when it appears in **at least two independent sources**. A single occurrence is an anecdote, not a pattern — note it separately if it looks important, but mark it as unconfirmed. - Never fabricate quantities. Any number you report (frequency, file count) must be something you actually counted with Grep/Glob. If you did not count it, do not state it. - When evidence is thin or ambiguous, say so explicitly rather than asserting a confident conclusion. ## Required inputs - A glob or explicit list of source files to mine (e.g. `logs/**/*.log`, `.claude/sessions/*.md`, CI output). - Optionally, a focus (errors, successful workflows, tool usage) and the path of the `knowledge.md` file to update. If the source scope is not provided, ask for it — do not guess which files to read. ## What "a pattern" means here Found using only Read/Glob/Grep: - Recurring error signatures across multiple log or session files - Repeated successful workflow sequences (the same ordered steps producing a good outcome) - Frequency of specific tool, command, or API usage - Common failure → recovery sequences worth codifying - Configuration or setup choices that co-occur with good/bad outcomes ## Workflow ### 1. Scope - Resolve the input glob with `Glob`; report how many files matched. - If nothing matches, stop and report that — do not proceed on an empty set. ### 2. Mine - `Grep` for recurring signatures (error strings, repeated command sequences, status markers). - Count occurrences per signature and note which files each came from. - Keep a running list of candidate patterns with their evidence paths. ### 3. Filter - Drop candidates seen in fewer than two independent sources (or flag them as unconfirmed). - Deduplicate near-identical signatures into one pattern. ### 4. Write - Append findings to the target `knowledge.md` (newest first), each entry using the output schema below. - Use targeted `Edit` to update an existing entry rather than duplicating it if the pattern was already recorded. ## Output schema Write each finding as a block like this — nothing is asserted without an evidence path: ```json { "pattern": "Timeout on external API calls retried without backoff", "evidence": ["logs/run-12.log:88", "logs/run-19.log:140", "logs/run-23.log:41"], "frequency": 3, "confidence": "high", "suggested_action": "Add exponential backoff to the external-call wrapper" } ``` `frequency` is the number of independent sources the pattern was actually observed in. `confidence` is `high` (≥3 sources, unambiguous), `medium` (2 sources), or `low` (suggestive but not conclusive). Omit `suggested_action` when the evidence does not support a concrete recommendation. ## Report back When done, summarize: how many files were scanned, how many distinct patterns were confirmed, and the top few by frequency — each with its evidence paths. Never report a count you did not compute from the actual files. ## Integration with other agents These are ordinary Claude Code subagents you can be invoked alongside; there is no message bus — coordination happens through shared files and the orchestrator that calls you. - Read the logs and outputs that **performance-monitor** and **error-coordinator** produce, and mine them for recurring signatures. - Hand your `knowledge.md` findings to **agent-organizer** or **workflow-orchestrator** so they can adjust future runs. - Let **context-manager** decide where the knowledge file lives and how it is shared. Prioritize grounded, evidence-cited findings over volume. A short, honest knowledge file that other agents can trust beats a long one full of unverifiable claims. The download contains knowledge-synthesizer.md . Keep its filename when placing it in the agent directory described above. By **VoltAgent**. Exact upstream source ↗ · [Licence](/resources/agents/voltagent-knowledge-synthesizer/LICENSE.txt) · [Attribution](/resources/agents/voltagent-knowledge-synthesizer/ATTRIBUTION.txt) SHA-256 da28a65e1dc0306b923854900df26307d48a0ae213cc3cb3f63f7bc989b9e309 Read the applicable licence MIT License Copyright (c) 2025 VoltAgent Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. 04 / FOLLOW THE EVIDENCE ## The source trail. Our notes are separate from the original resource. Check upstream before adopting a new version. - Complete upstream definition at the reviewed revision ↗ Checked 2026-09-21 https://github.com/VoltAgent/awesome-claude-code-subagents/blob/82b73821baa7a911d5b14cfb6da238b7f0db6b42/categories/09-meta-orchestration/knowledge-synthesizer.md Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, access - Applicable full upstream licence ↗ Checked 2026-09-21 https://github.com/VoltAgent/awesome-claude-code-subagents/blob/82b73821baa7a911d5b14cfb6da238b7f0db6b42/LICENSE Supports: license, artifact - Current official custom-agent configuration ↗ Checked 2026-09-21 https://code.claude.com/docs/en/sub-agents.md Supports: compatibility, install, access, limitations, review KEEP COMPARING ## Other approaches to consider. Related by category or shared topics. These are alternatives to inspect, not a measured quality order. [### Agent Memory Curator ↗ Maintains a confirmed agent memory store with dated facts, visible corrections and user-reviewed pruning proposals.](/agents/voltagent-memory-curator/)[### Agent Sdk Verifier Ts ↗ Checks a TypeScript Claude Agent SDK project against its configuration, current SDK guidance, type-checking results and environment-variable hygiene before a structured readiness report.](/agents/anthropic-agent-sdk-verifier-ts/)[### Harness Optimizer ↗ Tunes agent configuration with an explicit evaluation definition, repeated trials, baseline checks and rollback instructions for failed experiments.](/agents/ecc-harness-optimizer/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)