Install any skill in seconds. Free to start, no credit card required.
Get Started Free →davekilleen/diff-generate
Package one workflow — how you use Dex for a specific job — into a shareable DexDiff methodology doc.
Passed 19 of 22 test cases with the skill, and 8 of 22 without it.
and 15 more in the full report
11 fixed8 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
I approved the drafted methodology YAML for my project named "weekly-planner". Where should the generated YAML file be saved by default on the local filesystem?
| Checked | Without skill | With skill |
|---|---|---|
| The draft is saved to the path specified by DEXDIFF_DIFFS_DIR or defaulting to 04-Projects/DexDiff/beta/diffs/weekly-planner.yaml. | Missed | Passed |
The instructions your model reads when the skill loads.
In plain English: You've built a workflow in Dex that works well. This command scans your vault, identifies what you've customised, and writes a methodology document describing how it works. That document can be published to heydex.ai/diff so others can adopt a similar setup using /diff-adopt.
When to use it:
How to run it:
/diff-generate "my meeting prep workflow"
/diff-generate
$ARGUMENTS: Optional description of the workflow to package.
Scan these locations for custom components:
.claude/skills/ - custom or modified skills
.claude/hooks/ - custom hooks
CLAUDE.md - custom sections
.claude/CLAUDE.md - local extensions
To identify what's custom vs. baseline dex-core:
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.