bidirectional-differential
Audit coherence across an arrow of intent by running two parallel fresh Claude sessions — one reconstructs code from a single EARS, the other reconstructs…
Examining code for the line that is wrong
What it does
This skill runs a bidirectional differential audit on EARS↔code pairs. The audit is advisory — findings concentrate human review on specific cases, and acting on findings is always user-judged. When the audit surfaces drift, the recommended repair path walks the whole arrow: validate intent with the user, then cascade EARS → Tests → Code.
Use when the user invokes /differential-audit, asks to audit EARS-to-code drift for a feature or segment, wants a differential round-trip…
You don’t need to name it. Ask for the job in your own words — your AI loads the skill when the request matches.
What it can touch
No script files in its folder
Its folder holds text, not programs — but the instructions do tell your AI to run commands (see below).
How we know
Listed the 6 files in the skill’s folder on GitHub; none is a script or program.
Uses terminal commands
It shows your AI commands to run. In a coding agent that means your terminal; in a chat app it usually can’t.
How we know
The SKILL.md contains shell code blocks.
1 smaller thing worth knowing
Contains commands that delete or overwrite. Usually legitimate — listed so nothing is hidden.
How we know
Contains commands that delete or overwrite — SKILL.md line 66. Read 2026-10-05, commit 831c195.
SKILL.md, line 66 ↗No serious risk pattern found
Launch7’s automated check read all 6 text files in this skill and matched none of its serious risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.
How we know
Read 2026-10-05, commit 831c195 by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.
Recently maintained
Its repository has had changes recently.
How we know
Last push to jszmajda/lid: 2026-09-27 (8 days before the scan).
Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check
Add it to your AI
Supported. Upload it once in Claude’s settings. Works on every plan, including Free.
Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.
In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.
Make sure code execution is switched on (Settings → Capabilities). Skills need it.
Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.
How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end
More from jszmajda
All from this publisher →- lid-coach
Review a project's current linked-intent-development (LID) usage against LID's own principles and produce a prioritized report of recommendations for…
- linked-intent-dev
Guide for linked-intent development (LID).
- map-codebase
Bootstrap LID in an existing (brownfield) codebase.
- update-lid
Configure or reconcile a project for linked-intent development (LID).
