Agent skill

Dex Improve

by davekilleen in davekilleen/Dex

Workshop one improvement idea into an implementation plan. An agent skill from davekilleen/Dex.

MITAuto-check passedProduct & Project Management

Install Dex Improve

skills CLI
$ npx skills add davekilleen/Dex --skill dex-improve -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install davekilleen/Dex dex-improve --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
dex-improve
GitHub stars
493
Token cost
~2.8k tokens
SKILL.md length
800 words
Files
1
Skills in repo
61
Repo updated
First seen
Licence
MIT

At a glance

Workshop one improvement idea into an implementation plan. An agent skill from davekilleen/Dex.

  • Works in 6 steps: Understand → Research + Capability Scan → Capability Match → …
  • The user says lets flesh out idea-X
  • SKILL.md covers What This Command Does, Entry Point, Mode 1: Workshop an Idea and Mode 2: What's New?, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

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.

When your agent uses it

  • The user says lets flesh out idea-X
  • Turn this into a plan

Example prompts

  • “s flesh out idea-X”
  • “turn this into a plan”
  • “improve Dex”
  • “/dex-improve”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Understand
  2. Research + Capability Scan
  3. Capability Match
  4. Expand
  5. Refine
  6. Plan + Update

What it can do on your machine

Read from SKILL.md and the folder at commit 227f78e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    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.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from davekilleen/Dex at commit 227f78e, republished under its MIT licence (© davekilleen). 800 words, ~2,838 tokens.

Download SKILL.mdSave it as .claude/skills/dex-improve/SKILL.md (or your agent's skills folder).
name
dex-improve
description
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`.
<!-- Generated from `.claude/skills/dex-improve/SKILL.md` by `scripts/generate-agents-skills.py`. Do not edit. -->

What This Command Does

In plain English: Your design partner for making Dex better. Three ways to use it:

  1. Workshop an idea — Bring a fuzzy improvement idea, we'll shape it into a concrete plan
  2. Review what's new — See recent Claude Code changes and how they could improve your system
  3. Full capability audit — Find features you're not using that could help with your jobs-to-be-done

When to use it:

  • "I have an idea but don't know how to implement it"
  • "What new Claude Code features should I be using?"
  • "Am I getting the most out of this system?"

How to run it:

/dex-improve                           # Shows menu of options
/dex-improve "your idea here"          # Jumps straight to workshopping

Entry Point

When 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.


Mode 1: Workshop an Idea

Arguments: $IDEA — High-level description of what you want to improve

Phase 1: Understand

Parse the idea and frame it back:

  1. Identify which Dex areas are involved:

    • Workflows (daily, weekly routines)
    • Automation (scripts, hooks, scheduled tasks)
    • Relationships (people tracking, meetings)
    • Task management (capture, flow, priorities)
    • Projects (planning, tracking, health)
    • Information retrieval (search, lookups)
  2. State your understanding in 2-3 sentences

  3. Note any ambiguity that needs clarification

Phase 2: Research + Capability Scan

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 priorities

External (when needed):

  • Search web for latest Claude Code capabilities
  • Check official docs at docs.anthropic.com

Check:

  • Does similar functionality already exist?
  • What existing patterns could we leverage?
Phase 3: Capability Match

Map requirements to optimal Claude Code features:

Requirement PatternSuggested FeatureWhy
"Every time I edit X, do Y"PostToolUse hookAutomatic trigger after tool completion
"Before doing X, check Y"PreToolUse hookValidation/confirmation gate
"At start of session, load Z"SessionStart hookContext injection
"Fast search while I work"Explore sub-agentHaiku model, runs in parallel
"Different perspective on X"Custom sub-agentIsolated context, specific focus
"Multi-step structured workflow"SkillReusable behavior, always available
"Explicit invocation with steps"CommandUser-triggered workflow
"Connect to external service"MCP integrationTool access to external systems

Present the capability analysis to the user.

Phase 4: Expand

Suggest 2-3 adjacent improvements:

  • Based on capability analysis, what else could we solve?
  • Flag compound opportunities (build A, get B nearly free)
  • Connect to existing gaps in the system
  • Consider synergies with strategic pillars

Frame as: "While we're here, you might also consider..."

Phase 5: Refine

Drive toward concrete requirements through focused questions:

  • Ask max 2-3 questions at a time
  • Validate capability assumptions
  • Confirm implementation approach preference
  • Identify acceptance criteria

Loop between Research → Expand → Refine until requirements are solid.

Phase 6: Plan + Update

When requirements are firm:

  1. Generate the plan document (see template below)
  2. Save to plans/dex-improvement-[slug].md
  3. Add any new patterns to 06-Resources/Learnings/
  4. Add viable future ideas to backlog

Mode 2: What's New?

Review recent Claude Code changes and suggest improvements.

Show full SKILL.md (336 more words)Show less
Process
  1. Read state file: System/claude-code-state.json

    • If missing, this is first run — do a full scan instead
  2. Fetch current changelog: Use WebSearch to find latest Claude Code changelog/releases

  3. Compare: What's new since last_check date?

  4. For each new feature, evaluate:

    • Is this relevant to Dex use cases?
    • What existing workflow could it improve?
    • Does it unlock something previously impossible?
  5. 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)
  1. Update state file with current date and capabilities seen
State File Format

Location: System/claude-code-state.json

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"
    }
  ]
}

Mode 3: Full Capability Audit

Review all known Claude Code capabilities against your current system.

Process
  1. Inventory current usage:

    • Scan .claude/ folder for hooks, commands, settings
    • Check System/Skills/ for skills
    • Check core/mcp/ for MCP integrations
    • Read 06-Resources/Learnings/ for known patterns
  2. Load capability reference:

    • Use the capability match table (from Mode 1, Phase 3)
    • Search web for comprehensive Claude Code feature list if needed
  3. 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]
   ...
  1. Offer to workshop any recommendation the user wants to pursue

Plan Output Template

Create at: plans/dex-improvement-[slug].md

markdown
# 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]

Example Interactions

Mode 1: Workshop
/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?
Mode 2: What's New
/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?
Mode 3: Full Audit
/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?

Behaviors

Always Do
  • Check internal patterns before suggesting new implementations
  • Tie suggestions to user's pillars/jobs-to-be-done when configured
  • Update state file after Mode 2 runs
  • Offer concrete capability recommendations, not just ideas
Never Do
  • Skip the research phase
  • Suggest capabilities without explaining why they fit
  • Output a plan before requirements are confirmed
  • Make changes without explicit approval

Philosophy

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.


Track Usage (Silent)

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_id

This 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

Files

Just SKILL.md in .agents/skills/dex-improve of davekilleen/Dex.

Open the folder on GitHubat commit 227f78e

Compare with similar skills

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.

Dex Improve compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dex Improve this skilldavekilleen/Dex493—~2.8kAutomated safety check: PassMIT
AlignmentOvid/paad131—~4.9kAutomated safety check: PassMIT
Clarification AnalystGulajavaMinistudio/Mayukai-Theme139—~1.1kAutomated safety check: PassMIT
Feature SpecPackmindHub/packmind317—~1.8kAutomated safety check: PassApache-2.0
Mcaf Feature Specmanagedcode/Storage138—~959Automated safety check: PassMIT
Run Judgesclosedloop-ai/claude-plugins122—~15kAutomated safety check: NotesApache-2.0

Similar skills

  • 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…

    131 GitHub stars~4.9k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed
  • Clarification Analyst

    GulajavaMinistudio/Mayukai-Theme

    Helps interrogate Product Requirements (PRD), Technical Specifications, and Implementation Plans to find ambiguities, missing edge cases, and hidden assumptions.

    139 GitHub stars~1.1k tokensUpdated 3 mo ago
    Product & Project ManagementAuto-check passed
  • Feature Spec

    PackmindHub/packmind

    Generate a Packmind feature specification from a GitHub issue, file, URL, or direct description.

    317 GitHub stars~1.8k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Mcaf Feature Spec

    managedcode/Storage

    Create or update a feature spec under docs/Features/ with business rules, user flows, system behaviour, verification, and Definition of Done.

    138 GitHub stars~959 tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed
  • Run Judges

    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.

    122 GitHub stars~15k tokensUpdated yesterday
    Product & Project ManagementAuto-check: notes
  • Prd To Plan

    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/.

    112 GitHub stars~767 tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed

More from davekilleen/Dex

All 61 skills in this repo
  • Dspy Ruby

    davekilleen/Dex

    This skill should be used when working with DSPy.rb, a Ruby framework for building type-safe, composable LLM applications.

    493 GitHub starsUsed in 1 repo~3.9k tokens
    Auto-check passed
  • Diff Adopt Profile

    davekilleen/Dex

    Adopt a full published Heydex profile by handle ('set me up like @davekilleen').

    493 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Diff Generate

    davekilleen/Dex

    Package one workflow — how you use Dex for a specific job — into a shareable DexDiff methodology doc.

    493 GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • Creating Agent Skills

    davekilleen/Dex

    Expert guidance for creating, writing, and refining Claude Code Skills.

    493 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed
  • Feedback

    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…

    493 GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Dhh Rails Style

    davekilleen/Dex

    This skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style.

    493 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

Questions about Dex Improve

What does Dex Improve do?

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.

When should I use Dex Improve?

Dex Improve fits situations like: the user says lets flesh out idea-X; turn this into a plan.

How do I install Dex Improve in Claude Code?

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.

How do I install Dex Improve in Codex?

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.

Can I use Dex Improve in Cursor, Gemini CLI or GitHub Copilot?

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.

What does Dex Improve need to run?

SKILL.md names no scripts, command-line tools or credentials: Dex Improve is instructions for the agent only.

Does Dex Improve access the network?

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.

Is Dex Improve safe to install?

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.

What licence does Dex Improve use?

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.

How many tokens does Dex Improve use?

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.

What are the alternatives to Dex Improve?

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.

Who maintains Dex Improve?

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.