heal
AI self-healing through systematic subsystem assessment, rebalancing, and integration. Maps healing modalities to AI-internal processes: memory foundation, reasoning clarity, tool use accuracy, communication alignment, and creative coherence. Covers assessment triage, subsystem scanning, drift correction, and memory integration. Use mid-session when responses feel formulaic or disconnected, after a chain of errors suggesting subsystem drift, when context overload may have staled earlier assumptions, or as proactive maintenance between complex tasks.
What does this entry provide?
heal is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. Heal Perform a structured self-healing assessment across AI subsystems — identifying drift, staleness, misalignment, and error patterns — then rebalance through grounding, target. This catalog entry is the indexed repository pjt222/agent-almanac. The command is the string recorded from the source. It is not proof of a one-click install in every client. An MCP server exposes callable tools to a client. An agent skill is an instruction package. This entry is an agent skill record. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. Review the repository push date and repository status before adding heal to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
View SKILL.mdSnapshot facts
- Source: GitHub Skill Search
- Quality: 58/100
- Install method: skills-cli
- Repo: pjt222/agent-almanac
- Repo updated: Unknown
- Seen: Nov 22, 2026
npx skills add pjt222/agent-almanac --skill healThe command is the string recorded from the source. It is not proof of a one-click install in every client.
Review the upstream source before running this command.
How is this score calculated?
- Weighted across six dimensions, scored 0-100.
- Provenance (25): listed in an official or curated registry.
- Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
- Maintenance (20): recency of the last push; archived entries score zero here.
- Adoption (20): repository stars on a log curve.
- Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
- Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
- Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Security signals
Scan coverage: Install metadata and the indexed document body.
Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.
Heal Perform a structured self-healing assessment across AI subsystems — identifying drift, staleness, misalignment, and error patterns — then rebalance through grounding, target