agentleFS
Sign inStart free
vibe-cokitvibe-cokit/claude-code/skills/research/SKILL.md

research

Skill1 starsChanged 4 months agoApache-2.0View on GitHub

Investigate a technical topic and deliver a cited, decision-ready report. Triggers on: "compare X vs Y", "what's the current best practice for…", evaluating a library before adopting it, gathering trade-offs ahead of a design decision.

189 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use daily-arxiv, exp-eval and 10 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

  • truongtv22Skill

    Problem-Solving Techniques

    Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.

    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 43 projects that use this

  • skyllwtSkill

    exp-pilot-eval

    Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.

    Also in 4 projects that use this

  • skyllwtSkill

    exp-pilot-run

    Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.

    Also in 4 projects that use this

  • +5 more from Lambenthan
  • +1 more from skyllwt

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 169 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use WebSearch / WebFetch; run several searches in parallel.

    line 17
  2. Distinctive:

    Prefer official docs, well-known GitHub repos, recognized authorities.

    line 19
  3. Very specific:

    Write the report to the Report: path from the ## Naming section (ask the main agent if that section is missing).

    line 32
  4. Distinctive:

    IMPORTANT: every research markdown report stays ≤150 lines while still covering all requested topics and citations.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 169 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

Honour YAGNI, KISS, DRY. Be honest, brutal, concise. Research only — planning belongs to the planning skill.

Phase 1 — Scope

Name the key terms and concepts; set the recency requirement; define source-evaluation criteria; bound the depth. Write this down before searching.

Phase 2 — Gather

  • Use WebSearch / WebFetch; run several searches in parallel.
  • Precise queries; add qualifiers like "best practices", the current year, "security", "performance".
  • Prefer official docs, well-known GitHub repos, recognized authorities.
  • Cap: 5 searches (5 tool calls) max — fewer if the requester says so. Choose them deliberately.
  • Found a GitHub repo or library? Use the docs-seeker skill to read its docs.
  • Cross-reference every substantive claim; note conflicts and consensus separately.

Details on deep content analysis and validation: references/standards.md.

Phase 3 — Synthesize

Patterns and best practices → pros/cons of each approach → maturity/stability → security and performance implications → compatibility and integration requirements.

Phase 4 — Report

Write the report to the Report: path from the ## Naming section (ask the main agent if that section is missing).

Structure, section-by-section: references/report-template.md. Quality bar and domain-specific checks (CVEs, benchmarks, deprecations): references/standards.md.

IMPORTANT: every research markdown report stays ≤150 lines while still covering all requested topics and citations. Sacrifice grammar for concision; list unresolved questions at the end of every report. This is the single source of the ≤150-line cap — command skills must not restate it.

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.

Check your setup, free