skills.rest
0xHoneyJar
0xHoneyJarOFFICIAL
Explore all skills by this author →
WebsiteGitHub

detecting-staleness

Compute confidence-based freshness scores from frontmatter, git history, and configuration.

Updated Feb 17, 2026
Search Tags:#scoring#confidence#staleness#frontmatter#artifact#freshness#git-history
One-click install
npx skills add https://github.com/0xHoneyJar/construct-observer --skill detecting-staleness
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: detecting-staleness
Source: https://github.com/0xHoneyJar/construct-observer/tree/main/skills/detecting-staleness
Command: npx skills add https://github.com/0xHoneyJar/construct-observer --skill detecting-staleness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Artifacts in research pipelines often go unmonitored for freshness, risking stale insights. This Skill derives a confidence score from immutable inputs (frontmatter + git history + config) to highlight artifacts that warrant review.

Core Features & Use Cases

  • Lightweight health checks across all grimoires artifacts (canvas, journeys, reality, taste).
  • Per-artifact staleness classification with actionable recommendations for refresh or retention.
  • Integrates with existing governance by respecting decay constants and boost factors.

Quick Start

Run the staleness scan across the grimoires tree to generate a health report and suggested actions.

Frequently Asked Questions about detecting-staleness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check artifact freshness and detect staleness in a research pipeline?▼

You can detect staleness by running a scan across the grimoires tree, which computes a bounded health score from artifact frontmatter, git commit history, and decay parameters, yielding per-artifact status and recommended actions.

How does a confidence score calculate artifact staleness from git history?▼

A confidence score evaluates staleness by applying configurable decay constants and boost factors to git history and frontmatter metadata, yielding a bounded health classification for each artifact.

Can I filter staleness scans to target specific artifact packs?▼

Yes, you can apply optional pack filtering to target specific artifact groups across canvas, journeys, reality, and taste files, yielding focused per-artifact health reports with actionable recommendations.

What is the best way to monitor markdown frontmatter for outdated content?▼

Deriving a freshness score from immutable inputs like frontmatter and git history provides lightweight health checks with per-artifact staleness classification and actionable refresh recommendations.

Do I need external dependencies to classify artifact health and recommend next steps?▼

No external dependencies are required. The classification derives its confidence score entirely from immutable inputs already present in the repository, such as artifact frontmatter, git history, and configuration files.

Related Skills

Explore More Data & Analytics Skills→
samjhechtsamjhecht
4

initialize-governance

Generate Constitution, Roadmap, and process documentation templates for project governance.

Community
Advanced
prestariusprestarius
1

skill-stocktake

Audit Claude Code skills for overlap, freshness, and trigger integrity.

Community
Advanced
0xHoneyJar0xHoneyJar

refreshing-artifacts

Route artifacts to re-validation skills and update confidence metadata in frontmatter.

Official
Intermediate
nrakownrakow
1

anomaly-detection

Automate anomaly detection in dbt data pipelines for volume, freshness, and distribution issues.

Community
Advanced