Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →majiayu000/skill-lifeguard
Use when a skill is brittle, drifting, repeatedly failing, or needs a Reliable Skill Contract. Trigger for phrases like skill lifeguard, reliable skill, self-maintaining skill, negative examples, verification checkpoints, drift signals, replay hooks, or failure log to skill patch. Audits or patches skills so high-value workflows include explicit forbidden behaviors, checkpoints, machine-checkable done conditions, replay or smoke hooks, and drift detection.
Passed 16 of 19 test cases with the skill, and 13 of 19 without it.
and 2 more in the full report
4 fixed15 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have a skill file for database migrations that has been drafted and tested once interactively by a developer, but it still requires human supervision during execution. Which exact maturity label should be assigned to this skill in our reliability report?
| Checked | Without skill | With skill |
|---|---|---|
| The skill maturity is classified as manual. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill to make an existing or new skill self-maintaining enough for real
agent work. It complements skill-audit and skill-creator: use this skill for
the reliability contract, then use those skills for library fit and authoring.
Read references/examples.md when you need example contract wording. Use
assets/reliable-contract-template.md when drafting a reusable section.
Every high-value workflow skill should either include these five elements or record why an element is intentionally deferred:
| Element | Required Evidence |
|---|---|
| Explicit negative examples | Named forbidden behaviors and concrete alternatives. |
| Verification checkpoints | Pass/fail checks after important phases, not only at the end. |
| Machine-checkable done conditions | Commands, assertions, artifacts, or state queries from the current session. |
| Replay or smoke hooks | A small way to rerun or sample the workflow, plus a log-to-patch loop. |
| Drift signal detection | Observable signs that the skill is stale, undertriggering, overtriggering, or producing false success. |
manual: workflow still needs human validation.skill: manually validated and packaged as reusable instructions.automation: repeatedly reliable and safe enough for scheduled or hook-driven use.present, partial, missing, or deferred.SKILL.md for routing and boundaries,
references/ for long examples, scripts/ for deterministic checks,
assets/ or templates/ for reusable report shapes.test cases passed, vs 13 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.