Tech research
Search GitHub, Stack Overflow, and technical blogs for solutions to a technical implementation problem. Returns a comparative analysis with a recommendation. Use when facing a technical decision, choosing a library, or looking for proven patterns in similar projects.From its SKILL.md
npx -y skills add tykisgod/quick-question --skill tech-researchAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 176 tokens by cl100k_base, as published. Nobody here has run it
Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).
Search for technical implementation solutions to the problem currently being discussed.
Arguments: $ARGUMENTS
Process
- Extract keywords (in English), construct 2-3 search queries
- Search GitHub projects, Stack Overflow, technical blogs using WebSearch
- Organize into a comparison table:
| Approach | Representative Projects | How It Works | Pros | Cons |
|---|
- Recommend which approach best fits this project, and why
Notes
- Prioritize approaches from similar project types (same engine, same language, similar scale)
- Do not just provide links — provide key conclusions
- If there is no industry consensus, state that directly
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most research analysis skills give in 176 tokens
Counted across 1,213 of the 2,113 authors here whose files we hold, read 2026-09-06
- Cite sources for every important claimin 47 of 1213, across 38 files
- Separate facts from inferences and recommendationsin 21 of 1213, across 12 files
- Write findings to a markdown filein 19 of 1213
- Label every insight with a confidence levelin 18 of 1213, across 8 files
- Read product marketing context before asking questionsin 18 of 1213, across 8 files
- Rank themes by frequency and intensityin 16 of 1213, across 6 files
- Establish research mode before proceedingin 16 of 1213, across 6 files
- Segment survey responses by customer tier or tenurein 16 of 1213, across 6 files
- Categorize support tickets before analyzingin 16 of 1213, across 6 files
- Weight research sources from the last twelve monthsin 16 of 1213, across 6 files
- Use at least five data points per segmentin 15 of 1213, across 5 files
- Extract verbatim quotes for all research findingsin 15 of 1213, across 5 files
Said here and by no other author read
- Organize findings into a comparison table
- Extract keywords for search queries
- Search GitHub and Stack Overflow for solutions
- Recommend the best approach for the project
- Prioritize approaches from similar project types
- Provide key conclusions instead of just links
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.