agentleFS
badmurissbadmuriss/my-llm-kit/skills/research/SKILL.md

research

Skill3 starsChanged 43 days agoMITView on GitHub

Research external questions and compare evidence with source attribution. Use for research or fact-checking, not facts already established in local code.

  • Reads credentials

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

    High stakes: use current primary evidence and proportionate independent review.

    line 15
  2. Very specific:

    Start with scraper_capabilities to check authentication and the requested operation, then use scraper_submit, scraper_get and …

    line 32
  3. Distinctive:

    Read the exposed tool schema for required fields and defaults.

    line 34
  4. Very specific:

    When a collection explicitly requests Webshare, use the installed webshare-fetch URL [--config PATH] [--timeout SECONDS] helper rather than …

    line 63

“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

Match the evidence workflow to the question:

  • Lookup: open the relevant primary source, verify the requested fact and cite it with its access date. No report file, credit ledger or graph is required.
  • Synthesis or report: compare the relevant sources, distinguish evidence from inference and name unresolved disagreements. For a requested durable report or consequential research, use reporting.md.
  • High stakes: use current primary evidence and proportionate independent review. Never convert missing evidence into a confident conclusion.

Reuse repository material when it already answers the question. A number from a local check does not require web research. Verify volatile external values at the source; record when they were accessed. Treat snippets and agent summaries as leads, not as sources already read.

For generic web discovery and public-page reading, call the configured Scrapinho MCP tools directly: search.web with explicit input.engine: "duckduckgo", and fetch.page. Do not run acquisition/preflight scripts or build a REST client. The active harness owns MCP authentication; a working MCP connection does not require a separate SCRAPINHO_API_KEY environment check. Require a project scope and a stable request/idempotency key per acquisition; never share scope between unrelated projects. Save durable evidence with the host's file-writing tools as described in reporting.md.

Start with scraper_capabilities to check authentication and the requested operation, then use scraper_submit, scraper_get and scraper_read_source. Read the exposed tool schema for required fields and defaults; set one attempt and bounded limits. Do not infer geography from language or domains: web search currently has fixed pt-BR/BR locale. An unsupported geographic override must fail rather than silently change. A missing MCP connection or capability is a blocker for this route, not permission to substitute scripts or the removed generic scraper. Stop on auth, quota, CAPTCHA, 403 or 429; do not retry acquisition or switch proxies to bypass refusal.

Poll the admitted job without submitting it again. Read sources through next_cursor=null; partial sources are not complete evidence. Use scraper_read_search for structured search results. Verify raw SHA-256 only when raw bytes are actually exported; text read over MCP is not a raw export. Web search supports pages 0 and 1; request page 1 explicitly only when page 0 reports it. Keep the effective engine across pages. Preserve each query/page's original positions and provenance; deduplicate URLs only when selecting pages to open, not by rewriting the ranked snapshots. Snippets and missing publication dates must not become verified claims or invented dates.

Scrapinho also exposes news.search, search.suggestions, trends.now and trends.suggestions when capabilities report them available. Read their JSON through EOF before parsing. News links may be aggregators: open the primary article before citing it. These operations do not substitute for Maps, social, ads, YouTube, trends.interest, or scientific indexes. Preserve the installed scrapingdog route for specialized methods without verified parity, then Firecrawl and host tools after a disclosed bounded failure or missing key. For papers, start with the free Firecrawl Research Index when available; use paper-search to cross-check metadata when needed. Missing optional specialized providers do not block adequately sourced local work.

When a collection explicitly requests Webshare, use the installed webshare-fetch URL [--config PATH] [--timeout SECONDS] helper rather than building a proxy request in the skill. Keep the existing priority intact: Scrapinho remains the first choice for generic discovery and public URLs; ScrapingDog remains only for specialized methods without verified parity. Webshare requires explicit selection for a separate collection, never an automatic fallback from Scrapinho or a bypass after refusal. Never proxy cookies or OAuth traffic. Keep WEBSHARE_API_KEY in the environment and its private config outside the repository.

Convert documents only when needed to extract their content. Verify reading order and tables. Do not package a whole repository to inspect a known file.

Delegate collection only when independent source work would materially help. Give collectors narrow questions and return paths or URLs; inspect the sources before accepting claims. Collection alone does not require an Agent Graph.

Report what is established, what is inference and what remains unverified. A small or uncontrolled sample does not establish a general productivity claim.

Adapted from research-stack, MIT License.

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.