tech-research
Skill12 starsChanged 8 months agoMITView on GitHub
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.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- dmoreq/agent-grimoiretheir own version, first seen Nov 8, 2026
- neijix/AICodeFactorytheir own version, first seen Nov 1, 2026
- dsonders/claude-skillstheir own version, first seen Oct 20, 2026
- The-Focus-AI/standardstheir own version, first seen Oct 12, 2026
- CoteNite/tech-skillstheir own version, first seen Sep 28, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- CoteNite/tech-skills★ 1same name
- The-Focus-AI/standards★ 1same name
- dmoreq/agent-grimoire★ 0same name
- dsonders/claude-skills★ 0same name
- neijix/AICodeFactory★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-testsSkill
- best-practiceSkill
- bootstrapSkill
- briefSkill
- changesSkill
- claude-code-reviewSkill
- claude-plan-reviewSkill
- codex-code-reviewSkill
- codex-plan-reviewSkill
- commit-pushSkill
- depsSkill
- design-researchSkill
- designSkill
- doc-driftSkill
- doc-syncSkill
- doc-tidySkill
- executeSkill
- explainSkill
- full-briefSkill
- goSkill
- grandmaSkill
- planSkill
- post-design-reviewSkill
- recordSkill
- self-reviewSkill
- testSkill
- timelineSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Search for technical implementation solutions to the problem currently being discussed.
- Distinctive: line 13
Search in English. Check primary sources first (official docs, the library's or engine's source and README), then GitHub projects, Stack …
- Distinctive: line 26
If there is no industry consensus, state that directly
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- Search in English. Check primary sources first (official docs, the library's or engine's source and README), then GitHub projects, Stack Overflow, and 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
- Save the result, sources included, to
Docs/qq/<branch-name>/<topic>_tech-research.md(or wherever the project already keeps research notes; branch name fromgit branch --show-current | tr '/' '_'). If the project's instructions ask for research notes to be committed, commit that file alone, following them; otherwise leave it for/qq:commit-push
Notes
- Prioritize approaches from similar project types (same engine, same language, similar scale)
- Tag every conclusion with its source: official docs, source code you actually read, third-party post or answer (link each), or own knowledge
- If there is no industry consensus, state that directly
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.