agentleFS
lutzseverinolutzseverino/repo-canon/.agents/skills/research/SKILL.md

research

Skill1 starsChanged yesterdayMITView on GitHub

Investigate a question against high-trust primary sources and publish the assigned artifact, defaulting to a Markdown findings file in the repo. Use for topic research, docs or API facts, and delegated investigation, including triage research runs.

190 other projects use a version of this, 56 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use Problem-Solving Techniques, daily-arxiv 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.
  • 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 6 projects that use this

  • 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

  • +5 more from Lambenthan

The file

Files
SKILL.md

A prompt or brief naming this skill is its invocation.

Perform the investigation in the current run, including when another run delegated it to you.

  1. Investigate the question against primary sources (official docs, source code, specs, first-party APIs), not a secondary write-up of them. Follow every claim back to the source that owns it.
  2. When the task assigns an artifact and destination, publish the findings there, citing each claim's source. For an assigned issue artifact, publication is complete on the issue; no repository findings file or index edit is needed. Post an issue or pull request artifact as .repo-standards/rules/comments.md#disclaimers says.
  3. Otherwise, write the findings to a single Markdown file, citing each claim's source. Save it where the repo's documentation rules or existing convention put such notes, such as beside the usage or development topic it serves, and add it to that directory's index, creating the index when those rules require one. If there is no such place, put it somewhere sensible and say where.

Reads

Paths are relative to the repository root.

  • The installed documentation rules, which the repository-standards skill looks up. When they are missing, follow the repository's existing convention for such notes, or put them somewhere sensible and say where, as step 3 says.
  • The index of the directory the notes go in, such as docs/development/README.md. When it is missing, create it only when the documentation rules require one.
  • .repo-standards/rules/comments.md: the installed comment rules, whose section the posting steps name. When it is missing, post issue bodies and comments as the steps describe.

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.