agentleFS
Sign inStart free
lynchypinlynchypin/project-onboard/skills/research/SKILL.md

research

Skill0 starsChanged 3 months agoMITView on GitHub

Investigate a question against high-trust primary sources and capture findings as a markdown file in the repo. Spins up a background agent so the main conversation keeps working while it reads.

189 other projects use a version of this, 53 of them edited.

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

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

  • 0

    Common

    Most of the 169 edited versions we read keep these.

  • 5

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

    Write findings to a single markdown file, citing each claim's source.

    line 19
  2. Distinctive:

    When the research agent completes, summarize key findings back to the caller (wayfinder or the user).

    line 24
  3. Distinctive:

    Never cite secondary sources as the authority — trace back to primary.

    line 37
  4. Distinctive:

    Never guess when the answer is findable.

    line 38
  5. Distinctive:

    Never block the main conversation — always use a background agent.

    line 39

“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

Investigate a question against primary sources — official docs, source code, specs, first-party APIs — not secondary write-ups. Follow every claim back to the source that owns it.

Process

  1. Spin up a background agent so the main conversation keeps working while it reads.
  2. The background agent's job:
    • Investigate the question against primary sources only.
    • Write findings to a single markdown file, citing each claim's source.
    • Save where the repo already keeps such notes; if no convention exists, use docs/research/.
  3. When the research agent completes, summarize key findings back to the caller (wayfinder or the user).

What counts as a primary source

  • Official documentation (not blog posts about the docs)
  • Source code of the library/tool in question
  • Published specifications (RFCs, W3C specs, language specs)
  • First-party API references
  • The project's own code and git history

What this skill must never do

  • Never cite secondary sources as the authority — trace back to primary.
  • Never guess when the answer is findable.
  • Never block the main conversation — always use a background agent.

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