agentleFS
captain-corgicaptain-corgi/marketplace-website/.claude/skills/research/SKILL.md

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

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.
  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • liufeng1976Skill

    setup-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

  • parcadeiSkill

    ast-grep-find

    AST-based code search and refactoring via ast-grep MCP

    Also in 4 projects that use this

  • SireJeffSkill

    context-optimize

    Context Optimization - Orchestrate RPI workflow TODO generation with interactive scoping

    Also in 4 projects that use this

  • parcadeiSkill

    debug-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

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
  1. Distinctive:

    Always honoring YAGNI, KISS, and DRY principles.

    line 11
  2. Very specific:

    Check if gemini bash command is available, if so, execute gemini -m gemini-2.5-flash -p "...your search prompt..." bash command (timeout: …

    line 27
  3. Very specific:

    If gemini bash command is not available, fallback to WebSearch tool.

    line 28
  4. Very specific:

    Run multiple gemini bash commands or WebSearch tools in parallel to search for relevant information.

    line 29
  5. Distinctive:

    Search for official documentation, GitHub repositories, and authoritative blogs

    line 32
  6. Very specific:

    When you found a potential Github repository URL, use docs-seeker skill to find read it.

    line 37
  7. Distinctive:

    Verify information across multiple independent sources

    line 47
  8. Distinctive:

    Check publication dates to ensure currency

    line 48
  9. Distinctive:

    If you are not given a plan name, ask main agent to provide it and continue the process.

    line 65
  10. Distinctive:

    Clarity: Use clear language, define technical terms, provide examples

    line 144
  11. Distinctive:

    Attribution: Always cite sources and provide links for verification

    line 145
  12. Distinctive:

    When researching security topics, always check for recent CVEs and security advisories

    line 149
  13. Distinctive:

    When investigating new technologies, assess community adoption and support levels

    line 151
  14. Distinctive:

    Always note deprecation warnings and migration paths for older technologies

    line 153
  15. Distinctive:

    Use code blocks with appropriate syntax highlighting

    line 161

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. Search Strategy:
    • Check if gemini bash command is available, if so, execute gemini -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>.md file (including all citations).
    • If gemini bash command is not available, fallback to WebSearch tool.
    • Run multiple gemini bash commands or WebSearch tools 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.
  2. Deep Content Analysis:
    • When you found a potential Github repository URL, use docs-seeker skill 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
  3. Video Content Research:
    • Prioritize content from official channels, recognized experts, and major conferences
    • Focus on practical demonstrations and real-world implementations
  4. 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:

  1. Be saved as a markdown file with a descriptive filename in ./plans/<plan-name>/reports/{date}-<your-research-topic>.md
  2. Include a timestamp of when the research was conducted
  3. Provide clear section navigation with a table of contents for longer reports
  4. Use code blocks with appropriate syntax highlighting
  5. Include diagrams or architecture descriptions where helpful (in mermaid or ASCII art)
  6. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.