Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →davekilleen/diff-adopt
Adopt one shared DexDiff methodology — reads a workflow description, adapts it to your role and vault, and walks you through setup.
Passed 15 of 19 test cases with the skill, and 4 of 19 without it.
and 12 more in the full report
13 fixed4 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before asking the user for their job role during vault discovery, where in the vault should you check for an existing profile record, and what field should you read?
| Checked | Without skill | With skill |
|---|---|---|
| Checks for file path System/user-profile.yaml | Missed | Passed |
The instructions your model reads when the skill loads.
In plain English: Someone figured out a great way to use Dex for a specific job — like prepping for meetings, reviewing deals, or building performance evidence. This command reads their methodology and walks you through setting up a similar workflow in your vault. It adapts to your role, your tools, and your folder structure. Nothing is copied from their system — your Dex generates everything fresh, tailored to you.
When to use it:
How to run it:
/diff-adopt @davekilleen/meeting-intelligence
/diff-adopt https://heydex.ai/diff/davekilleen/meeting-intelligence
/diff-adopt 04-Projects/DexDiff/beta/diffs/meeting-prep.yaml
$ARGUMENTS - A reference to one methodology document:
@<handle>/<diff-id> - fetch the raw methodology from the API host:
GET https://api.heydex.ai/api/diff?author=<handle>&id=<diff-id>https://heydex.ai/diff/<handle>/<diff-id> - parse out the handle and diff id, then make the same API call. Never WebFetch the page itself: heydex.ai pages are a React app shell and contain no methodology text. The API lives on api.heydex.ai; the website host has no /api/* routes.DEXDIFF_DIFFS_DIR (default 04-Projects/DexDiff/beta/diffs/meeting-prep.yaml) (read directly)The argument is always an explicit location — never a bare name.
Fetch failures must stop the flow with a plain explanation, never silently:
dexdiff_schema: "2.0". If it is a short one-line summary instead, say so plainly: "This workflow was published in an old thin format that cannot be regenerated faithfully - ask the author to re-publish it." Do not invent the missing methodology.If no argument or invalid input:
/diff-adopt expects a workflow reference, URL, or file path.
Examples:
/diff-adopt @davekilleen/meeting-intelligence
/diff-adopt https://heydex.ai/diff/davekilleen/meeting-intelligence
test cases passed, vs 4 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.