From b17z-sage
Evaluate and maintain knowledge freshness - detect and fix stale knowledge
npx claudepluginhub joshuarweaver/cascade-ai-ml-engineering --plugin b17z-sageThis skill uses the workspace's default tool permissions.
When knowledge is recalled, evaluate its freshness. Stale knowledge injects wrong context.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
When knowledge is recalled, evaluate its freshness. Stale knowledge injects wrong context.
| Signal | How to Detect | Example |
|---|---|---|
| Version mismatch | Knowledge mentions old version | "Post v2.4" when we're on v2.6 |
| Temporal markers | "TODO", "planned", "upcoming", "will be" | Feature listed as TODO but shipped |
| Contradiction | Recalled content conflicts with current facts | "Not implemented" but we just used it |
| Date references | Specific dates in the past | "Q1 2025 roadmap" |
Different knowledge types decay differently:
| Type | Decay Rate | Evaluate For |
|---|---|---|
knowledge | Medium | Version refs, temporal markers, contradictions |
preference | Very slow | Only explicit user contradiction |
todo | Fast | Completion, age without action (30+ days) |
reference | Slow | Source validity, version refs |
sage_update_knowledge(
knowledge_id="the-id",
content="Updated accurate content",
)
sage_deprecate_knowledge(
knowledge_id="the-id",
reason="Superseded by v2.6 skills architecture",
replacement_id="new-knowledge-id", # optional
)
sage_archive_knowledge(knowledge_id="the-id")
sage_update_knowledge(
knowledge_id="the-id",
content=None, # Keep content
# Just accessing it updates last_recalled internally
)
When you see recalled knowledge, ask:
If any answer is yes -> remediate immediately.
Recalled knowledge says:
"Post v2.4.0 - TODO: Proactive recall on session start"
But we're on v2.6 and proactive recall shipped in v2.5.
Action:
sage_update_knowledge(
knowledge_id="feature-ideas",
content="Updated content marking proactive recall as shipped...",
)