agentleFS
Sign inStart free
JaimeGBAJaimeGBA/Ion/.claude/skills/health/SKILL.md

health

Skill9 starsChanged 7 months agoMITView on GitHub

Comprehensive health check of the knowledge base — coverage, freshness, consistency, structure

We split this skill into the rules it gives an agent

9 rules. 0 are common, 3 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check last_updated dates on all files

    line 19
  2. Very specific:

    Verify knowledge/decisions/ entries are consistent with current state

    line 26
  3. Very specific:

    Check that ops/action-items.md doesn't reference completed or abandoned work

    line 27
  4. Very specific:

    Verify [[wiki links]] resolve to existing files

    line 28
  5. Distinctive:

    Verify all files have valid YAML frontmatter with required fields

    line 35
  6. Distinctive:

    Check naming conventions are followed

    line 36
  7. Very specific:

    Verify every knowledge subfolder has a README.md with a ## Current Contents section that matches reality (dispatch the Librarian for the …

    line 38
  8. Distinctive:

    Check the age of the oldest unprocessed item

    line 42
  9. Very specific:

    Add remaining fixes to ops/action-items.md with appropriate priority

    line 77

“Common” is measured: kept by at least 6 in 10 of the 36 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Health — Knowledge Base Health Check

Perform a comprehensive health check of the entire knowledge base.

Checks

1. Coverage

  • List all knowledge files and their status (skeleton / draft / active / stale / archived)
  • Calculate: X of Y files are active
  • Identify areas with only skeleton files or no content
  • Flag knowledge areas critical for the partner's situation that are underdeveloped

2. Freshness

  • Check last_updated dates on all files
  • Flag anything not updated in 30+ days as potentially stale
  • Flag files with status: draft older than 14 days
  • Assess whether stale content is still likely accurate based on other files

3. Consistency

  • Dispatch the Librarian sub-agent for thorough contradiction detection
  • Verify knowledge/decisions/ entries are consistent with current state
  • Check that ops/action-items.md doesn't reference completed or abandoned work
  • Verify [[wiki links]] resolve to existing files

4. Completeness

  • For each knowledge area, assess depth relative to what the partner's situation needs
  • Flag critical gaps (e.g., for a startup: no financial projections while fundraising; for a researcher: no source notes while writing a paper; for a creative project: no character work while drafting)

5. Structure

  • Verify all files have valid YAML frontmatter with required fields
  • Check naming conventions are followed
  • Scan for potential sensitive data that shouldn't be in committed files
  • Verify every knowledge subfolder has a README.md with a ## Current Contents section that matches reality (dispatch the Librarian for the detailed sync check)

6. Inbox Health

  • Count files in ops/inbox/ (excluding README.md and any processed/ subfolder)
  • Check the age of the oldest unprocessed item
  • Apply these thresholds:
    • Healthy: fewer than 10 items AND oldest is less than 14 days old
    • Warning: 10-25 items OR oldest is 14-30 days old → recommend running /process-inbox soon
    • Critical: more than 25 items OR oldest is over 30 days old → the inbox is becoming a graveyard, process now
  • Also check sources/ for files that have never been ingested (no entries in ops/changelog.md referencing them) — flag these as "captured but not digested"

Output

# Health Report — [Date]

## Overall Health: [Excellent / Good / Needs Attention / Critical]

## Coverage: X/Y files active and current

## Issues

### Critical (act now)
[Issues that could cause problems if not addressed]

### Warning (act soon)
[Issues that are degrading knowledge quality]

### Info (nice to fix)
[Minor structural or completeness issues]

## Recommendations
[Prioritized list of what to fix, grouped by effort level]

After Health Check

  • Save report to ops/reviews/YYYY-MM-DD-health-report.md
  • Offer to fix issues that can be addressed immediately
  • Add remaining fixes to ops/action-items.md with appropriate priority

Download now (ZIP)

  • Other versions52 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 52

    1. garrytan/gstack★ 139ksame name
    2. tw93/Waza★ 7.5ksame name
    3. tw93/claude-health★ 7.3ksame name
    4. agenticnotetaking/arscontexta★ 3.5ksame name
    5. kellyvv/PhoneClaw★ 1.3ksame name
    6. ninehills/skills★ 280same name
    7. kv0906/pm-kit★ 138same name
    8. buildomator/buildomator★ 101same name
    9. priyanshuchaudhary53/naval-skills★ 19same name
    10. IvanSkainet/arena-agent★ 8same name

    42 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use ios-clean, ios-fix and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • Saqlain-811Skill

      ios-clean

      Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)

      Also in 5 projects that use this

    • Saqlain-811Skill

      ios-fix

      Autonomous iOS bug fixer. (gstack)

      Also in 5 projects that use this

    • ShreyRaviSkill

      plan-tune

      Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). Review which AskUserQuestion prompts fire across gstack skills, set per-question preferences (never-ask / always-ask / ask-only-for-one-way), inspect the dual-track profile (what you declared vs what your behavior suggests), and enable/disable question tuning. Conversational interface — no CLI syntax required.

      Also in 8 projects that use this

    • seek888Skill

      pair-agent

      Pair a remote AI agent with your browser. One command generates a setup key and prints instructions the other agent can follow to connect. Works with OpenClaw, Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent gets its own tab with scoped access (read+write by default, admin on request). Use when asked to "pair agent", "connect agent", "share browser", "remote browser", "let another agent use my browser", or "give browser access". (gstack) Voice triggers (speech-to-text aliases): "pair agent", "connect agent", "share my browser", "remote browser access".

      Also in 10 projects that use this

    • ShreyRaviSkill

      landing-report

      Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)

      Also in 7 projects that use this

    • seek888Skill

      open-gstack-browser

      Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".

      Also in 8 projects that use this

    • +2 more from Saqlain-811
    • +3 more from ShreyRavi
  • In this repository11 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free