Skill

sage-knowledge-hygiene

Evaluate and maintain knowledge freshness - detect and fix stale knowledge

Install

npx claudepluginhub joshuarweaver/cascade-ai-ml-engineering --plugin b17z-sage

Tool Access

This skill uses the workspace's default tool permissions.

Preview

When knowledge is recalled, evaluate its freshness. Stale knowledge injects wrong context.

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.2k

mcp-builder

9 files

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

anthropics-skills-13

124.2k

canvas-design

20 files

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

anthropics-skills-13

124.2k

Stats

Stars1

Forks1

Last CommitFeb 1, 2026

Actions

View Source View Plugin View on GitHub View README

Knowledge Hygiene

When knowledge is recalled, evaluate its freshness. Stale knowledge injects wrong context.

Staleness Signals

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"

Type-Specific Evaluation

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

When to Evaluate

On recall - Quick scan when knowledge is surfaced
Session start - Review proactively recalled items
After version bump - Check for version-specific knowledge
Explicit request - User asks to review knowledge

Remediation Actions

If content is wrong/outdated:

sage_update_knowledge(
    knowledge_id="the-id",
    content="Updated accurate content",
)

If superseded but worth keeping for history:

sage_deprecate_knowledge(
    knowledge_id="the-id",
    reason="Superseded by v2.6 skills architecture",
    replacement_id="new-knowledge-id",  # optional
)

If no longer relevant:

sage_archive_knowledge(knowledge_id="the-id")

If still valid (bump freshness):

sage_update_knowledge(
    knowledge_id="the-id",
    content=None,  # Keep content
    # Just accessing it updates last_recalled internally
)

Quick Hygiene Check

When you see recalled knowledge, ask:

Version check: Does it reference an old version?
Completion check: Does it list something as TODO that's done?
Contradiction check: Does it conflict with what we know now?

If any answer is yes -> remediate immediately.

Example: Stale Feature List

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...",
)