.agents/skills/abyss-self-diagnostic-spine/SKILL.md
Apply the aoa-session-self-diagnose workflow inside an abyss-* repository using repo-relative runtime evidence, bounded diagnostic-session artifacts, last-good comparison posture, and honest owner-aware handoff. Use when the base diagnosis workflow is correct but one abyss repo needs a thin runtime-owned diagnostic read model before any repair claim becomes honest. Do not use when the request is really for silent repair, when no concrete target path exists, or when the base skill is already sufficient without local adaptation.
npx skillsauth add 8Dionysus/aoa-skills abyss-self-diagnostic-spineInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill to adapt aoa-session-self-diagnose to an abyss-* repository
when the local repo needs one runtime-owned diagnostic session artifact that can
cite runtime evidence, compare against last-good posture, and hand off honestly
toward the reviewed session diagnosis family.
Use this skill when:
aoa-session-self-diagnose workflow is already correct, but an abyss-* repo needs one runtime-owned diagnostic session artifact with repo-relative evidence refsDo not use this skill when:
aoa-session-self-repair only after reviewed diagnosis existsabyss-* repo adaptation is needed and the base aoa-session-self-diagnose skill is sufficientdiagnostic_session_v1exit_classaoa-session-self-diagnoseaoa-session-self-repairaoa-session-progression-liftaoa-quest-harvestaoa-session-self-diagnose instead of inventing a new project-family workflowaoa-doctorManifest-backed techniques:
8Dionysus/aoa-techniques at 5c6f0496edc3c2e74590baa35627c85fe58ef765 using path techniques/agent-workflows/session-drift-taxonomy/TECHNIQUE.md and sections: Intent, Outputs, Risks, Validation8Dionysus/aoa-techniques at 5c6f0496edc3c2e74590baa35627c85fe58ef765 using path techniques/agent-workflows/diagnosis-from-reviewed-evidence/TECHNIQUE.md and sections: Intent, Inputs, Outputs, Core procedure, Contracts, Validationdevelopment
Sanitize private technical material into a public-safe owner-bounded derivative, or resolve authority among authored, generated, runtime, and installed sources. Use for governed incidents, logs, configs, diagnostics, or conflicting source roles. Do not use for ordinary editing, memo/session work, direct publication, or durable-memory authority.
tools
Diagnose a reviewed recurring session/workflow failure, or carry one bounded owner repair through checkpoint, rollback, and real health verification. Use for reviewed contamination, drift, repeated route/tool failure, or an established diagnosis ready for repair. Do not use on live evidence, for vague self-improvement, or to call a proposed or merely executed change verified.
tools
Use only when a literal ref to a closed/reviewed session packet is supplied, to extract, classify, propose promotion or branching, or identify an automation opportunity. Missing, live, or unreviewed evidence must fail closed without inventing a ref. Natural closeout preservation belongs to aoa-memo-writeback. Do not use for generic summaries, progression, direct owner writes, scheduling, mutation, or telemetry authority.
testing
Turn one stable technical truth into bounded evidence through contract, coverage-audit, or property mode. Use to define a named consumer seam, audit what existing checks really constrain, or express a broad invariant after manual cases establish meaning. Compose with aoa-eval when an evaluation surface must first be found or applied. Do not use for undefined behavior, generic test plans, or green checks as whole-system proof.