knowledge-synthesis-freshness
Sub-skill of knowledge-synthesis: Freshness (+3).
Best use case
knowledge-synthesis-freshness is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of knowledge-synthesis: Freshness (+3).
Teams using knowledge-synthesis-freshness should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/freshness/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How knowledge-synthesis-freshness Compares
| Feature / Agent | knowledge-synthesis-freshness | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of knowledge-synthesis: Freshness (+3).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Freshness (+3) ## Freshness | Recency | Confidence impact | |---------|------------------| | Today / yesterday | High confidence for current state | | This week | Good confidence | | This month | Moderate — things may have changed | | Older than a month | Lower confidence — flag as potentially outdated | For status queries, heavily weight freshness. For policy/factual queries, freshness matters less. ## Authority | Source type | Authority level | |-------------|----------------| | Official wiki / knowledge base | Highest — curated, maintained | | Shared documents (final versions) | High — intentionally published | | Email announcements | High — formal communication | | Meeting notes | Moderate-high — may be incomplete | | Chat messages (thread conclusions) | Moderate — informal but real-time | | Chat messages (mid-thread) | Lower — may not reflect final position | | Draft documents | Low — not finalized | | Task comments | Contextual — depends on commenter | ## Expressing Confidence When confidence is high (multiple fresh, authoritative sources agree): ``` The team decided to use REST for the API redesign. [direct statement] ``` When confidence is moderate (single source or somewhat dated): ``` Based on the discussion in #engineering last month, the team was leaning toward REST for the API redesign. This may have evolved since then. ``` When confidence is low (old data, informal source, or conflicting signals): ``` I found a reference to an API migration discussion from three months ago in ~~chat, but I couldn't find a formal decision document. The information may be outdated. You might want to check with the team for current status. ``` ## Conflicting Information When sources disagree: ``` I found conflicting information about the API approach: - The ~~chat discussion on Jan 10 suggested GraphQL - But Sarah's email on Jan 15 confirmed REST - The design doc (updated Jan 15) reflects REST The most recent sources indicate REST was the final decision, but the earlier ~~chat discussion explored GraphQL first. ``` Always surface conflicts rather than silently picking one version.
Related Skills
domain-knowledge-sweep
Systematic multi-source research of an engineering domain. Spawns parent issue → 6 research subissues (Standards, Academic, Industry, LinkedIn-marketing, Code-audit, Synthesis) → gap implementation subissues. Replaces LinkedIn-only extraction with defensible comprehensive sourcing.
public-knowledge-graph-governance
Maintain public-safe knowledge graph artifacts for llm-wiki and similar markdown knowledge bases. Use when changing graph generators, validators, schema docs, weekly freshness checks, or public/private source-scope boundaries.
llm-wiki-weekly-freshness
Class-level governance workflow for keeping llm-wiki-style markdown knowledge bases current, public-safe, graph/index-valid, and useful for code development. Use when reviewing llm-wiki architecture/content, scanning new LLM concepts, maintaining public knowledge graphs, producing an issue roadmap, or running recurring freshness cadence.
workspace-knowledge-doc-contracts
Class-level workspace knowledge, LLM-wiki, repo mission contracts, stale doc references, semantic taxonomy, and knowledge-source reconnaissance.
knowledge-pipeline
Workflow for maintaining workspace-hub knowledge and learning pipelines across scripts/knowledge, scripts/learning, and docs/superpowers, including indexing, archive synthesis, issue updates, and pipeline troubleshooting.
knowledge-base-builder
Build searchable knowledge bases from document collections (PDFs, Word, text files). Use for creating technical libraries, standards repositories, research databases, or any large document collection requiring full-text search.
knowledge-source-recon
Reconnaissance pattern to inventory all knowledge sources across the workspace-hub ecosystem's existing intelligence infrastructure. Maps raw sources for LLM Wiki ingestion planning. Leverages pre-built registries and indexes rather than re-scanning directories.
user-research-synthesis
Synthesize qualitative and quantitative user research into structured insights and opportunity areas
knowledge-synthesis
Combines search results from multiple sources into coherent, deduplicated answers with source attribution and confidence scoring.
knowledge-management
Create, organize, and maintain support knowledge base content to reduce ticket volume
document-rag-pipeline-build-knowledge-base
Sub-skill of document-rag-pipeline: Build Knowledge Base (+2).
competitive-analysis-strengths-to-acknowledge
Sub-skill of competitive-analysis: Strengths to Acknowledge.