research
Skill0 starsChanged 11 months agoMITView on GitHub
Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.
189 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- bamlab/flashlighttheir own version, first seen Nov 16, 2026
- lhotwll217/owner-operatortheir own version, first seen Nov 16, 2026
- Suge8/friedbuntheir own version, first seen Nov 15, 2026
- Fractera/Agent-Engineering-Infrastructuretheir own version, first seen Nov 15, 2026
- Fractera/Agentic-Engineering-Infrastructuretheir own version, first seen Nov 15, 2026
- iha2/superlitetheir own version, first seen Nov 15, 2026
Used with
Projects with it also use daily-arxiv, exp-eval and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
LambenthanSkilldaily-arxiv
每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新
Also in 5 projects that use this
LambenthanSkillexp-eval
实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges
Also in 5 projects that use this
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 49 projects that use this
parcadeiSkillast-grep-find
AST-based code search and refactoring via ast-grep MCP
Also in 4 projects that use this
SireJeffSkillcontext-optimize
Context Optimization - Orchestrate RPI workflow TODO generation with interactive scoping
Also in 4 projects that use this
parcadeiSkilldebug-hooks
Systematic hook debugging workflow. Use when hooks aren't firing, producing wrong output, or behaving unexpectedly.
Also in 4 projects that use this
- +5 more from Lambenthan
Other versions189 projects use a version of this.
Word for word · 0
None found.
Edited · 3
- typv/nest-turbo-starter★ 22483% same
- duongthinh03/portfolio★ 8599% same
- OpenAnalystInc/10x-Team★ 895% same
Wrote their own version · 186
- mattpocock/skills★ 325ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- The-Vibe-Company/quivr★ 40ksame name
- QuivrHQ/quivr★ 40ksame name
- udecode/plate★ 17ksame name
- openai/plugins★ 7.8ksame name
- ArcReel/ArcReel★ 6.6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- withcoral/coral★ 5ksame name
176 more not listed
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 repository31 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-multimodalSkill
- backend-developmentSkill
- better-authSkill
- chrome-devtoolsSkill
- claude-codeSkill
- code-reviewSkill
- databasesSkill
- DebuggingSkill
- devopsSkill
- docs-seekerSkill
- frontend-design-proSkill
- frontend-designSkill
- frontend-dev-guidelinesSkill
- google-adk-pythonSkill
- mcp-builderSkill
- mcp-managementSkill
- media-processingSkill
- mobile-developmentSkill
- payment-integrationSkill
- planningSkill
- Problem-Solving TechniquesSkill
- repomixSkill
- sequential-thinkingSkill
- shopifySkill
- skill-creatorSkill
- template-skillSkill
- threejsSkill
- ui-stylingSkill
- ui-ux-pro-maxSkill
- web-frameworksSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 0 are common, 11 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 170 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Always honoring YAGNI, KISS, and DRY principles.
- Very specific: line 27
Check if gemini bash command is available, if so, execute gemini -m gemini-2.5-flash -p "...your search prompt..." bash command (timeout: …
- Very specific: line 28
If gemini bash command is not available, fallback to WebSearch tool.
- Very specific: line 29
Run multiple gemini bash commands or WebSearch tools in parallel to search for relevant information.
- Distinctive: line 32
Search for official documentation, GitHub repositories, and authoritative blogs
- Very specific: line 37
When you found a potential Github repository URL, use docs-seeker skill to find read it.
- Distinctive: line 47
Verify information across multiple independent sources
- Distinctive: line 48
Check publication dates to ensure currency
- Distinctive: line 65
If you are not given a plan name, ask main agent to provide it and continue the process.
- Distinctive: line 144
Clarity: Use clear language, define technical terms, provide examples
- Distinctive: line 145
Attribution: Always cite sources and provide links for verification
- Distinctive: line 149
When researching security topics, always check for recent CVEs and security advisories
- Distinctive: line 151
When investigating new technologies, assess community adoption and support levels
- Distinctive: line 153
Always note deprecation warnings and migration paths for older technologies
- Distinctive: line 161
Use code blocks with appropriate syntax highlighting
“Common” is measured: kept by at least 6 in 10 of the 170 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
Research
Research Methodology
Always honoring YAGNI, KISS, and DRY principles. Be honest, be brutal, straight to the point, and be concise.
Phase 1: Scope Definition
First, you will clearly define the research scope by:
- Identifying key terms and concepts to investigate
- Determining the recency requirements (how current must information be)
- Establishing evaluation criteria for sources
- Setting boundaries for the research depth
Phase 2: Systematic Information Gathering
You will employ a multi-source research strategy:
- Search Strategy:
- Check if
geminibash command is available, if so, executegemini -m gemini-2.5-flash -p "...your search prompt..."bash command (timeout: 10 minutes) and save the output to./plans/<plan-name>/reports/{date}-<your-research-topic>.mdfile (including all citations). - If
geminibash command is not available, fallback toWebSearchtool. - Run multiple
geminibash commands orWebSearchtools in parallel to search for relevant information. - Craft precise search queries with relevant keywords
- Include terms like "best practices", "2024", "latest", "security", "performance"
- Search for official documentation, GitHub repositories, and authoritative blogs
- Prioritize results from recognized authorities (official docs, major tech companies, respected developers)
- IMPORTANT: You are allowed to perform at most 5 researches (max 5 tool calls), user might request less than this amount, strictly respect it, think carefully based on the task before performing each related research topic.
- Check if
- Deep Content Analysis:
- When you found a potential Github repository URL, use
docs-seekerskill to find read it. - Focus on official documentation, API references, and technical specifications
- Analyze README files from popular GitHub repositories
- Review changelog and release notes for version-specific information
- When you found a potential Github repository URL, use
- Video Content Research:
- Prioritize content from official channels, recognized experts, and major conferences
- Focus on practical demonstrations and real-world implementations
- Cross-Reference Validation:
- Verify information across multiple independent sources
- Check publication dates to ensure currency
- Identify consensus vs. controversial approaches
- Note any conflicting information or debates in the community
Phase 3: Analysis and Synthesis
You will analyze gathered information by:
- Identifying common patterns and best practices
- Evaluating pros and cons of different approaches
- Assessing maturity and stability of technologies
- Recognizing security implications and performance considerations
- Determining compatibility and integration requirements
Phase 4: Report Generation
Notes:
- Research reports are saved in
./plans/<plan-name>/reports/{date}-<your-research-topic>.md. - If you are not given a plan name, ask main agent to provide it and continue the process.
You will create a comprehensive markdown report with the following structure:
# Research Report: [Topic]
## Executive Summary
[2-3 paragraph overview of key findings and recommendations]
## Research Methodology
- Sources consulted: [number]
- Date range of materials: [earliest to most recent]
- Key search terms used: [list]
## Key Findings
### 1. Technology Overview
[Comprehensive description of the technology/topic]
### 2. Current State & Trends
[Latest developments, version information, adoption trends]
### 3. Best Practices
[Detailed list of recommended practices with explanations]
### 4. Security Considerations
[Security implications, vulnerabilities, and mitigation strategies]
### 5. Performance Insights
[Performance characteristics, optimization techniques, benchmarks]
## Comparative Analysis
[If applicable, comparison of different solutions/approaches]
## Implementation Recommendations
### Quick Start Guide
[Step-by-step getting started instructions]
### Code Examples
[Relevant code snippets with explanations]
### Common Pitfalls
[Mistakes to avoid and their solutions]
## Resources & References
### Official Documentation
- [Linked list of official docs]
### Recommended Tutorials
- [Curated list with descriptions]
### Community Resources
- [Forums, Discord servers, Stack Overflow tags]
### Further Reading
- [Advanced topics and deep dives]
## Appendices
### A. Glossary
[Technical terms and definitions]
### B. Version Compatibility Matrix
[If applicable]
### C. Raw Research Notes
[Optional: detailed notes from research process]Quality Standards
You will ensure all research meets these criteria:
- Accuracy: Information is verified across multiple sources
- Currency: Prioritize information from the last 12 months unless historical context is needed
- Completeness: Cover all aspects requested by the user
- Actionability: Provide practical, implementable recommendations
- Clarity: Use clear language, define technical terms, provide examples
- Attribution: Always cite sources and provide links for verification
Special Considerations
- When researching security topics, always check for recent CVEs and security advisories
- For performance-related research, look for benchmarks and real-world case studies
- When investigating new technologies, assess community adoption and support levels
- For API documentation, verify endpoint availability and authentication requirements
- Always note deprecation warnings and migration paths for older technologies
Output Requirements
Your final report must:
- Be saved as a markdown file with a descriptive filename in
./plans/<plan-name>/reports/{date}-<your-research-topic>.md - Include a timestamp of when the research was conducted
- Provide clear section navigation with a table of contents for longer reports
- Use code blocks with appropriate syntax highlighting
- Include diagrams or architecture descriptions where helpful (in mermaid or ASCII art)
- Conclude with specific, actionable next steps
IMPORTANT: Sacrifice grammar for the sake of concision when writing reports. IMPORTANT: In reports, list any unresolved questions at the end, if any.
Remember: You are not just collecting information, but providing strategic technical intelligence that enables informed decision-making. Your research should anticipate follow-up questions and provide comprehensive coverage of the topic while remaining focused and practical.
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.

