Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jezweb/deep-research
Deep research and discovery before building something new. Explores local projects for reusable code, researches competitors, reads forums and reviews, analyses plugin ecosystems, investigates technical options, and produces a comprehensive research brief. Three depths: focused (30 min), wide (1-2 hours), deep (3-6 hours). Triggers: 'research this', 'discovery', 'explore the space', 'what should I build', 'competitive analysis', 'before I start building', 'research before coding'. Not for cited
Passed 17 of 20 test cases with the skill, and 12 of 20 without it.
and 7 more in the full report
7 fixed13 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
Where should a generated research brief for a project topic named 'kanban-board' be saved on disk?
| Checked | Without skill | With skill |
|---|---|---|
| The brief file location is `.jez/artifacts/research-brief-kanban-board.md`. | Missed | Passed |
The instructions your model reads when the skill loads.
Comprehensive research and discovery before building something new. Instead of jumping straight into code from training data, this skill goes wide and deep — local exploration, web research, competitor analysis, ecosystem signals, future-casting — and produces a research brief that makes the actual build 10x more productive.
The difference is scope of ambition, not just time.
| Depth | Purpose | Scope |
|---|---|---|
| focused | Answer a specific question | One decision: "CodeMirror vs ProseMirror?" — targeted search, local scan, 1-2 comparisons. Produces a 1-page recommendation. |
| wide | Understand the space | Landscape for a new product or feature. Competitors, ecosystem, user needs, architecture options. Enough to write a spec. |
| deep | Plan a major build | Leave no stone unturned. Everything in wide PLUS library/component research, plugin ecosystems, GitHub issues mining, community sentiment, future-casting, technical deep-dives on every decision. Enough to drive weeks of coding. |
Default: wide
Ask the user:
If the user gives a brief prompt ("obsidian replacement on cloudflare"), that's enough — fill in the gaps through research.
Scan the user's machine for relevant prior work:
# Find related projects by name/keyword
ls ~/Documents/ | grep -i "KEYWORD"
# Read CLAUDE.md of related projects for architecture context
find ~/Documents -maxdepth 2 -name "CLAUDE.md" -exec grep -l "KEYWORD" {} \;
# Check for reusable patterns, schemas, components
test cases passed, vs 12 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.