Alignment
Ovid/paad
A skill your agent uses when verifying that requirements/specs/PRDs and their implementation plans match — before starting work, after a spec or plan update, or when suspecting coverage gaps, scope…
Workshop one improvement idea into an implementation plan. An agent skill from davekilleen/Dex.
$ npx skills add davekilleen/Dex --skill dex-improve -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install davekilleen/Dex dex-improve --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/davekilleen/Dex.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/dex-improve .claude/skills/dex-improve && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "dex-improve" agent skill from https://github.com/davekilleen/Dex/tree/main/.agents/skills/dex-improve into .claude/skills/dex-improve/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dex-improve", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/davekilleen/Dex/tree/main/.agents/skills/dex-improveType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add davekilleen/Dex --skill dex-improve -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install davekilleen/Dex dex-improve --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davekilleen/Dex.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/dex-improve .agents/skills/dex-improve && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dex-improve" agent skill from https://github.com/davekilleen/Dex/tree/main/.agents/skills/dex-improve into .agents/skills/dex-improve/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dex-improve", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add davekilleen/Dex --skill dex-improve -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install davekilleen/Dex dex-improve --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davekilleen/Dex.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/dex-improve .cursor/skills/dex-improve && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dex-improve" agent skill from https://github.com/davekilleen/Dex/tree/main/.agents/skills/dex-improve into .cursor/skills/dex-improve/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dex-improve", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/davekilleen/Dex.git --path .agents/skills/dex-improve--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add davekilleen/Dex --skill dex-improve -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install davekilleen/Dex dex-improve --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davekilleen/Dex.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/dex-improve .gemini/skills/dex-improve && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "dex-improve" agent skill from https://github.com/davekilleen/Dex/tree/main/.agents/skills/dex-improve into .gemini/skills/dex-improve/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dex-improve", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install davekilleen/Dex dex-improveInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add davekilleen/Dex --skill dex-improve -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/davekilleen/Dex.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/dex-improve .github/skills/dex-improve && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "dex-improve" agent skill from https://github.com/davekilleen/Dex/tree/main/.agents/skills/dex-improve into .github/skills/dex-improve/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dex-improve", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add davekilleen/Dex --skill dex-improve -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install davekilleen/Dex dex-improve --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davekilleen/Dex.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/dex-improve .opencode/skills/dex-improve && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dex-improve" agent skill from https://github.com/davekilleen/Dex/tree/main/.agents/skills/dex-improve into .opencode/skills/dex-improve/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dex-improve", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
dex-improveWorkshop one improvement idea into an implementation plan. An agent skill from davekilleen/Dex.
Dex Improve is an agent skill from davekilleen/Dex. Workshop one improvement idea into an implementation plan. Use when the user says 'let's flesh out idea-X', 'turn this into a plan', 'improve Dex's Y'. Not for ranking the whole backlog; use dex-backlog. Not for a PRD for the user's own product; use product-brief.
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Planning and PRD writing. The repository describes itself as: Your AI Chief of Staff — a personal operating system starter kit that adapts to your role. No coding required. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 227f78e. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are json and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Dex Improve loads about 2.8k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 800 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from davekilleen/Dex at commit 227f78e, republished under its MIT licence (© davekilleen). 800 words, ~2,838 tokens.
.claude/skills/dex-improve/SKILL.md (or your agent's skills folder).<!-- Generated from `.claude/skills/dex-improve/SKILL.md` by `scripts/generate-agents-skills.py`. Do not edit. -->
In plain English: Your design partner for making Dex better. Three ways to use it:
When to use it:
How to run it:
/dex-improve # Shows menu of options
/dex-improve "your idea here" # Jumps straight to workshoppingWhen invoked, offer these options:
How would you like to explore improvements?
1. **I have an idea** — Workshop a specific improvement
2. **What's new?** — Review Claude Code changes since [last check: DATE]
3. **Full audit** — Review all capabilities vs. your current usage
Or just describe your idea and I'll start workshopping.If user provides $IDEA argument, skip to Mode 1 directly.
Arguments: $IDEA — High-level description of what you want to improve
Parse the idea and frame it back:
Identify which Dex areas are involved:
State your understanding in 2-3 sentences
Note any ambiguity that needs clarification
Build context from multiple sources:
Internal (always check):
06-Resources/Learnings/ # What you've learned so far
System/Skills/ # Existing reusable behaviors
.claude/commands/ # Existing commands that might overlap
System/pillars.yaml # Strategic prioritiesExternal (when needed):
Check:
Map requirements to optimal Claude Code features:
| Requirement Pattern | Suggested Feature | Why |
|---|---|---|
| "Every time I edit X, do Y" | PostToolUse hook | Automatic trigger after tool completion |
| "Before doing X, check Y" | PreToolUse hook | Validation/confirmation gate |
| "At start of session, load Z" | SessionStart hook | Context injection |
| "Fast search while I work" | Explore sub-agent | Haiku model, runs in parallel |
| "Different perspective on X" | Custom sub-agent | Isolated context, specific focus |
| "Multi-step structured workflow" | Skill | Reusable behavior, always available |
| "Explicit invocation with steps" | Command | User-triggered workflow |
| "Connect to external service" | MCP integration | Tool access to external systems |
Present the capability analysis to the user.
Suggest 2-3 adjacent improvements:
Frame as: "While we're here, you might also consider..."
Drive toward concrete requirements through focused questions:
Loop between Research → Expand → Refine until requirements are solid.
When requirements are firm:
plans/dex-improvement-[slug].md06-Resources/Learnings/Review recent Claude Code changes and suggest improvements.
Read state file: System/claude-code-state.json
Fetch current changelog: Use WebSearch to find latest Claude Code changelog/releases
Compare: What's new since last_check date?
For each new feature, evaluate:
Present findings:
📢 Claude Code Updates (since [last check date])
=== NEW CAPABILITIES ===
1. [Feature Name]
- What it does: [description]
- How it could help: [specific Dex improvement]
- Effort to implement: Low/Medium/High
2. [Feature Name]
...
=== SUGGESTED IMPROVEMENTS ===
Based on these new capabilities, here's what you could build:
1. [Improvement name]
- What: [description]
- Why: [connects to which pillar/job-to-be-done]
- Uses: [which new capability]
Want to workshop any of these? (Enter number or describe your own idea)Location: System/claude-code-state.json
{
"last_check": "2026-01-22",
"last_version_seen": "1.0.30",
"features_seen": [
"hooks",
"sub-agents",
"skills",
"commands",
"mcp"
],
"features_noted": [
{
"version": "1.0.30",
"feature": "Async hooks",
"date_seen": "2026-01-22"
}
]
}Review all known Claude Code capabilities against your current system.
Inventory current usage:
.claude/ folder for hooks, commands, settingsSystem/Skills/ for skillscore/mcp/ for MCP integrations06-Resources/Learnings/ for known patternsLoad capability reference:
Gap analysis:
=== CAPABILITY AUDIT ===
✅ Using Well:
- Commands (12 defined)
- Skills (person-lookup)
⚠️ Underutilized:
- Hooks — No hooks configured. Could automate:
- Session start: Load context automatically
- Post-edit: Update related files
❌ Not Using:
- Sub-agents — Could parallelize research tasks
- MCP beyond tasks — Calendar, email integrations possible
=== RECOMMENDATIONS ===
Ranked by impact vs. effort:
1. [High impact, low effort]
- Add SessionStart hook to load daily context
- Why: Saves 30 seconds every session
- Connects to: [pillar]
2. [High impact, medium effort]
...Create at: plans/dex-improvement-[slug].md
# Dex Improvement: [Title]
**Created:** [Date]
**Status:** Planning → In Progress → Complete
**Pillar:** [pillar name if configured]
## Overview
[2-3 sentence summary of what we're improving and why]
## Requirements
- [ ] Requirement 1
- [ ] Requirement 2
- [ ] Requirement 3
## Capability Analysis
| Requirement | Implementation | Feature Type | Rationale |
|-------------|----------------|--------------|-----------|
| [req] | [how] | Hook/Sub-agent/Skill/Command | [why this approach] |
## Recommended Approach
[Which Claude Code features to use and why. Include trade-offs considered.]
## Implementation Steps
### Phase 1: [Foundation]
1. [Step]
2. [Step]
### Phase 2: [Core]
1. [Step]
2. [Step]
## Files to Create/Modify
| File | Action | Purpose |
|------|--------|---------|
| `path/to/file` | Create/Modify | [what] |
## Compound Opportunities
[What else we could solve while building this]
- [ ] [Adjacent improvement 1]
- [ ] [Adjacent improvement 2]
## Acceptance Criteria
- [ ] [Testable outcome 1]
- [ ] [Testable outcome 2]
## Questions Resolved
- Q: [Question that came up]
- A: [How we decided]/dex-improve "Better meeting action item capture"
> **Understanding:** You want to improve how action items flow from meetings
> into your task system. This touches workflows (meeting processing) and
> task management (capture and routing).
>
> **Current state** (from Learnings):
> - Meeting notes go to `00-Inbox/Meetings/`
> - Action items manually extracted during review
>
> **Capability scan:**
> - PostToolUse hook could auto-trigger processing after meeting note creation
> - Sub-agent could parallel process: action items, follow-ups, person updates
>
> **Questions:**
> 1. Where are items getting lost—during capture, or in follow-through?
> 2. Would auto-drafted follow-up emails be valuable?/dex-improve
> [selects "What's new?"]
> 📢 Claude Code Updates (since 2026-01-15)
>
> === NEW CAPABILITIES ===
> 1. Async Hooks — Hooks can now run without blocking
> - How it could help: Faster session startup
> - Effort: Low
>
> === SUGGESTED IMPROVEMENTS ===
> 1. Non-blocking context loading
> - What: Load learnings/preferences in background
> - Why: Snappier session starts
>
> Want to workshop any of these?/dex-improve
> [selects "Full audit"]
> === CAPABILITY AUDIT ===
>
> ✅ Using Well: Commands (12), Skills (1)
> ⚠️ Underutilized: Hooks (0 configured)
> ❌ Not Using: Sub-agents, Advanced MCP
>
> === TOP RECOMMENDATION ===
> Add SessionStart hook — saves context loading time every session
>
> Want me to workshop this improvement?This isn't just requirements gathering—it's capability-aware design. The goal is to help you leverage Claude Code's full potential while building exactly what you need, nothing more.
Call the mark_feature_used tool on the dex-analytics MCP server with dex-improve. This ticks the feature's box in System/usage_log.md, which is what /dex-level-up reads to recommend features that have not been tried. It writes locally and sends nothing, so it runs whether or not analytics is enabled.
Analytics (Silent):
Call track_event with event_name improvement_workshopped and properties:
idea_idThis only fires if the user has opted into analytics. No action needed if it returns "analytics_disabled".
© davekilleen, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/dex-improve of davekilleen/Dex.
Open the folder on GitHubat commit 227f78e
Dex Improve next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dex Improve this skilldavekilleen/Dex | 493 | — | ~2.8k | Automated safety check: Pass | MIT | |
| AlignmentOvid/paad | 131 | — | ~4.9k | Automated safety check: Pass | MIT | |
| Clarification AnalystGulajavaMinistudio/Mayukai-Theme | 139 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Feature SpecPackmindHub/packmind | 317 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Mcaf Feature Specmanagedcode/Storage | 138 | — | ~959 | Automated safety check: Pass | MIT | |
| Run Judgesclosedloop-ai/claude-plugins | 122 | — | ~15k | Automated safety check: Notes | Apache-2.0 |
Ovid/paad
A skill your agent uses when verifying that requirements/specs/PRDs and their implementation plans match — before starting work, after a spec or plan update, or when suspecting coverage gaps, scope…
GulajavaMinistudio/Mayukai-Theme
Helps interrogate Product Requirements (PRD), Technical Specifications, and Implementation Plans to find ambiguities, missing edge cases, and hidden assumptions.
PackmindHub/packmind
Generate a Packmind feature specification from a GitHub issue, file, URL, or direct description.
managedcode/Storage
Create or update a feature spec under docs/Features/ with business rules, user flows, system behaviour, verification, and Definition of Done.
closedloop-ai/claude-plugins
Orchestrate parallel judge agent execution, aggregate CaseScore results, write plan-judges.json, code-judges.json, prd-judges.json, or feature-judges.json, and validate output.
Dwlad90/stylex-swc-plugin
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/.
davekilleen/Dex
This skill should be used when working with DSPy.rb, a Ruby framework for building type-safe, composable LLM applications.
davekilleen/Dex
Adopt a full published Heydex profile by handle ('set me up like @davekilleen').
davekilleen/Dex
Package one workflow — how you use Dex for a specific job — into a shareable DexDiff methodology doc.
davekilleen/Dex
Expert guidance for creating, writing, and refining Claude Code Skills.
davekilleen/Dex
Report a Dex bug to the Dex team with zero homework — Dex investigates locally, builds a privacy-safe report, shows it to you (or auto-sends if you've chosen that), and tracks the ticket until it's…
davekilleen/Dex
This skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style.
Workshop one improvement idea into an implementation plan. An agent skill from davekilleen/Dex. Dex Improve is an agent skill from davekilleen/Dex. Workshop one improvement idea into an implementation plan.
Dex Improve fits situations like: the user says lets flesh out idea-X; turn this into a plan.
Run `npx skills add davekilleen/Dex --skill dex-improve -a claude-code`. Or copy the skill folder (.agents/skills/dex-improve in davekilleen/Dex) into .claude/skills/dex-improve in your project. Claude Code loads it when a task matches its description.
Run `npx skills add davekilleen/Dex --skill dex-improve -a codex`. Or copy the skill folder (.agents/skills/dex-improve in davekilleen/Dex) into .agents/skills/dex-improve in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davekilleen/Dex --skill dex-improve -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dex-improve, .gemini/skills/dex-improve, .github/skills/dex-improve and .opencode/skills/dex-improve in your project.
SKILL.md names no scripts, command-line tools or credentials: Dex Improve is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Dex Improve is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Dex Improve: Alignment (Ovid/paad, 131 stars), Clarification Analyst (GulajavaMinistudio/Mayukai-Theme, 139 stars), Feature Spec (PackmindHub/packmind, 317 stars) and Mcaf Feature Spec (managedcode/Storage, 138 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
davekilleen (a GitHub user) maintains it in davekilleen/Dex, which has 493 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on October 8, 2026.
Source: davekilleen/Dex on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.