heal-skill_skill

This skill automatically fixes outdated SKILL.md files by analyzing interactions, proposing precise edits, and applying changes with optional commits.
  • TypeScript

10.5k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill everyinc/compound-engineering-plugin --skill heal-skill

  • SKILL.md3.9 KB

Overview

This skill repairs incorrect or outdated skill instruction files and related artifacts when a skill behaves unexpectedly. It detects which skill ran, identifies the root cause in instructions or API references, proposes concrete fixes with before/after diffs, and applies changes only after getting user approval.

How this skill works

The skill inspects the recent conversation and invocation traces to determine which skill was executed and where the mismatch occurred. It analyzes errors, logs, and referenced documentation to pinpoint incorrect instructions, outdated API calls, or wrong parameters. It then prepares precise edits across the instruction file and supporting files, presents them for approval, and applies the changes with an optional commit.

When to use it

  • A skill returns unexpected errors or fails during execution.
  • Examples or code in the skill instructions reference deprecated or changed APIs.
  • Invocation messages suggest the wrong skill or parameters were used.
  • You need an audit and quick fix of skill docs and supporting scripts.
  • Before publishing a skill update that corrects runtime failures.

Best practices

  • Detect the active skill from recent invocation traces or error messages before proposing edits.
  • Show exact before/after snippets for every change so reviewers can validate intent.
  • Limit edits to the smallest, safest scope needed to resolve the issue.
  • Ask for explicit approval before making any file modifications or commits.
  • Verify cross-file consistency after edits (examples, references, and scripts match).

Example use cases

  • A skill fails because examples use an old endpoint; prepare diffs to update endpoint and example payloads.
  • A parameter name changed upstream; update instructions and any sample scripts that use it.
  • Invocation logs show the wrong skill name; correct discovery and invocation guidance so callers use the right skill.
  • Documentation shows outdated authentication steps; replace with the current process and validate sample calls.
  • A referenced helper script signature changed; update both the instruction text and the script to match.

FAQ

I analyze recent invocation messages, error traces, and any instruction/file references in the conversation to identify the active skill. If unclear, I ask for clarification before proceeding.

Will you change files without my permission?

No. I prepare detailed proposed edits and wait for your explicit choice: apply and commit, apply without commit, revise, or cancel.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
heal-skill skill by everyinc/compound-engineering-plugin | VeilStrat