From discovery
Web research via platform web tools. Use for technical comparisons, current-state and release-behavior questions, recent facts, ecosystem news, best practices, standards, or questions needing grounded web evidence. NOT for exact API syntax, config keys, or code examples — use looking-up-docs for those. NOT for repo-specific questions — search local files first.
How this skill is triggered — by the user, by Claude, or both
Slash command
/discovery:researching-web <research question><research question>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Follow the base skill. This Claude overlay only defines tool use and execution details.
Follow the base skill. This Claude overlay only defines tool use and execution details.
WebFetch to inspect primary or official sources directly after source discovery.looking-up-docs.Inspect enough sources to support the answer. Do not fetch every citation unless the risk or ambiguity justifies it.
Use Task only for broad background research that can run independently without
changing the output contract. Keep the prompt bounded and ask it to return cited
facts, not final recommendations.
Use the base skill's Research Result output contract exactly.
npx claudepluginhub alexei-led/cc-thingz --plugin discoveryGuides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.