technical-discovery
Performs technical research and analysis without implementation. Use when asked to "analyze this", "research this change", "investigate", "what would be involved", "where would changes occur", "scope this work", "technical discovery", or before creating complex Trellis issues to understand the technical landscape.
Profile →npx skills add majiayu000/claude-skill-registry --skill technical-discovery --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Technical Discovery Perform technical research and analysis to understand a problem, question, or proposed change. Produce a comprehensive report without any code implementation. ## Goal Investigate the codebase and relevant context to provide findings that inform decision-making or subsequent issue creation. This skill answers "what would be involved?" without actually doing the work. ## Required Inputs - **Problem or Question**: Description of what to analyze (e.g., "How would we add user authentication?" or "Why is the API slow?") - **Additional Context** (optional): Constraints, related issues, or specific areas to focus on ## When to Ask Questions Use `AskUserQuestion` to clarify before proceeding when: - The problem statement is too vague to research meaningfully - Multiple interpretations exist and the correct one significantly affects the analysis - You discover a decision point where user input would focus the research - You need domain knowledge or context that isn't in the codebase Ask focused questions early rather than making assumptions. One good clarifying question up front saves wasted research down the wrong path. ## Process ### 1. Understand the Request Parse th
- Goal
- Required Inputs
- When to Ask Questions
- Process
- 1. Understand the Request
- 2. Research the Codebase
- 3. Research External Context
- 4. Analyze Findings
- 5. Formulate Recommendations
- Output
- Guidelines
What does the technical-discovery skill do?
Performs technical research and analysis without implementation. Use when asked to "analyze this", "research this change", "investigate", "what would be involved", "where would changes occur", "scope this work", "technical discovery", or before creating complex Trellis issues to understand the technical landscape.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill technical-discovery --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.