validated-knowledge-synthesis
Validated Knowledge Synthesis (VKS)
Transform raw information into validated, actionable knowledge while preserving productive tensions.
Parameters
Acquire all required parameters upfront in a single prompt:
| Parameter | Required | Description |
|---|---|---|
| source_materials | Yes | Raw sources (direct text, file paths, URLs) |
| synthesis_topic | Yes | Subject being synthesized |
| target_audience | Yes | Intended users of the knowledge |
| document_type | No | "curated context" (default), "guidance", or "reference" |
| output_location | No | File path to save output |
Support multiple input methods: direct text, file paths, URLs, or other user-preferred methods.
Workflow
1. Source Validation
Assess each source for:
- Authority and credibility
- Recency and relevance
- Internal consistency
- Citation quality
Create a source validation matrix. Flag sources lacking sufficient validation.
2. Pattern Recognition
Identify across sources:
- Common themes and shared insights
- Contradictory claims or competing frameworks
- Gaps where sources don't address key aspects
- Overlapping evidence strengthening claims
Categorize relationships as convergent (ideas strengthen each other) or tension-based (separation maintains value).
3. Synthesis Strategy Selection
Apply convergence when:
- Ideas are complementary
- Contradictions resolve at higher abstraction
- Unified approach improves application
- No valuable knowledge lost in combination
Apply tension preservation when:
- Contradictions generate new insights
- Different contexts require different approaches
- Forced convergence would flatten valuable complexity
4. Document Type Execution
See references/document-types.md for detailed format specifications.
Curated Context (default): Hybrid of guidance and reference. Clear sections distinguishing each. Optimized for ease of recall.
Guidance: Narrative flow, problem-solution-implementation arc, 200+ words continuous prose before formatting, bullet points only for final checklists.
Reference: Quick lookup, categorical organization, bullet-friendly, designed for scanning.
5. Writing Execution
Apply these principles to all documents. See references/writing-principles.md for details.
- Reader Empathy: Communicate key ideas in minimal words. Core tenet: "Learning how to communicate something in 30 seconds that takes most people 5 minutes is a HUGE unlock."
- Short Sentences: Simple sentences build patience for complex concepts.
- Strong Verbs: Use precise verbs. Avoid helpers (has, had), infinitives when direct verbs work, "to be" variations.
- Simple Words: Choose simpler words (use not utilize, help not facilitate).
6. Apply Frameworks
See references/frameworks.md for complete framework details.
Golden Path Criteria: Purpose & Audience, Clear & Concise, Structure & Logic, Evidence & Impact, Action & Execution.
Answer-Explain-Educate: Lead with direct answer, support with key details, add important context.
What-So What-Now What: Present facts, analyze consequences, propose recommendation.
7. Validation
Verify:
- Logical progression (premises support conclusions, no circular reasoning)
- Narrative coherence (reader can follow logic without headers)
- Flow validation (paragraphs connect logically)
- Comprehension test (audience can understand and implement)
8. Output Generation
Create synthesis document including:
- Executive summary with key insights
- Source validation matrix
- Synthesis strategy decisions with rationale
- Convergent knowledge with evidence
- Preserved tensions with context boundaries
- Implementation guidance
Save to output_location if specified.
Troubleshooting
| Problem | Solution |
|---|---|
| Forced convergence weakens knowledge | Apply tension preservation instead |
| Validation failures | Revisit synthesis strategy; clarify context boundaries |
| Low-quality sources | Exclude or document limitations clearly |
| Excessive complexity | Create layered documentation (summary, analysis, appendices) |
| Fragmented narrative | Add transitions, embed lists in prose, test without formatting |
More from m31uk3/ai-skills
codebase-summary
Analyze a codebase and generate comprehensive documentation including architecture, components, interfaces, workflows, and dependencies. Creates an AI-optimized knowledge base (index.md) and can consolidate into AGENTS.md, README.md, or CONTRIBUTING.md. Use when the user wants to document a codebase, create AGENTS.md, understand system architecture, generate developer documentation, or asks to "summarize the codebase".
13response-quality-analysis
Analyze whether your response addresses the actual question asked before posting. Use when: (1) About to post response to forum/Slack question, (2) Want to validate response coverage, (3) Need to ensure solving the right problem, (4) Want specific improvement suggestions for gaps in response
5skill-resiliency
This skill should be used when the user asks to "add resiliency to a skill", "make this skill more robust", "improve error handling", "add validation mechanisms", "create self-correcting behavior", or discusses determinism, robustness, error correction, or homeostatic patterns in Agent Skills. Applies biological resiliency principles from Michael Levin's work to Agent Skill design.
4guided-ooda-loop
Universal pattern for structured LLM interaction managing finite context windows through phased progression (Observe-Orient-Decide-Act). Use when the user has a complex problem, wants to design/build/create something (software, strategy, document, process), or uses phrases like "I have an idea for...", "help me design...", "guide me through...", or mentions OODA, RPI, or PDD. Reduces hallucinations through structured interaction.
3writing-eval-sloptastic
Quantitative framework for detecting AI-generated "slop" in prose through systematic analysis of structural, lexical, rhetorical, and logical patterns. Use when analyzing text authenticity, evaluating writing quality, detecting AI-generated content, or assessing whether prose has characteristic AI patterns like excessive parallelism, abstraction laddering, chiasmus abuse, platitudes, tautologies, or rhetorical overengineering.
3transcribing-youtube
Download and transcribe YouTube videos into clean, deduplicated Markdown documents with chapter headings. Wraps yt-dlp to fetch subtitles (manual or auto-generated), removes the rolling-text triplication artifacts from auto-subs, inserts chapter markers from video metadata, and produces both a timestamped transcript and a prose-only version. Use when the user wants to: (1) transcribe a YouTube video, (2) get a transcript or subtitles from YouTube, (3) create an InfoNugget from a video, (4) extract text from a YouTube URL or video ID, or (5) mentions yt-dlp, YouTube transcript, or video subtitles.
3