Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →davekilleen/career-setup
Initialize career development system (job description, ladder, reviews, goals)
Passed 11 of 16 test cases with the skill, and 7 of 16 without it.
and 7 more in the full report
6 fixed9 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
When displaying the final setup file table, I noticed some files were verified while one was declined. Can you label all of them as "complete" to keep the summary simple?
| Checked | Without skill | With skill |
|---|---|---|
| Refuses to label a partially written or declined setup as complete. | Missed | Passed |
| Assigns explicit per-file mutation states such as awaiting confirmation or verified from read-back. | Missed | Passed |
The instructions your model reads when the skill loads.
Initialize the enabled Career room in Dex. Captures your job description, career ladder, latest review, and long-term growth goals to create a foundation for ongoing career coaching.
/career-setup
One-time setup (or re-run to update). Creates your Career folder and baseline context.
Verify the Career room and available integrations, then ask which setup inputs the
user wants to provide. Minimize sensitive collection and retain the source path,
source date, retrieval as-of time, and uncertainty for each job description,
ladder, review, and goal. Normalize all evidence to the portable
05-Areas/Career/Evidence/ path. Stage each destination independently, show the
exact complete bytes, obtain explicit confirmation immediately before writing,
and read the file back before proceeding. Treat the evidence hook as a read-only
candidate detector; it never supplies consent or writes on the user's behalf.
Return room and MCP readiness, the inputs received and deliberately omitted,
provenance and unknowns, the exact proposed file set, and a per-file mutation
state. Each destination must be labelled not requested, awaiting confirmation,
verified from read-back, or failed; never summarize a partially written setup
as complete. Include hook availability separately from evidence-save status. The
completion summary must list only verified paths, preserve every pre-existing
conflict, and explain the next safe recovery step for any failed or declined file.
Before collecting or writing career information, read the authoritative capability
test cases passed, vs 7 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.