agentleFS
sherificansherifican/Agent-FleetOps/skills/decomposed-local-research/SKILL.md

decomposed-local-research

Skill34 starsChanged 37 days agoMITView on GitHub

Run bounded local-model research by separating deterministic retrieval from short language passes.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Keep evidence packs small enough for the target context window.

    line 19
  2. Distinctive:

    If needed evidence was not retrieved, add it and rerun retrieval rather than asking the model to guess.

    line 20
  3. Distinctive:

    Use discovery-capable research or a human review for open-ended source discovery and reliability-critical work.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Decomposed Local Research

Why decompose

A long agentic loop can exceed a local model's tool-call or context budget even when it can summarize and compare evidence well. Separate deterministic retrieval from bounded language work so each model call has one focused purpose.

Architecture

  1. A deterministic retriever reads the supplied source and retrieves the selected evidence URLs into an evidence pack.
  2. A bounded model pass summarizes the source and extracts checkable claims.
  3. A bounded verification pass labels each claim supported, contradicted, unsupported, or overstated against the evidence pack.
  4. A bounded synthesis pass writes the verdict using only the prior stages; it introduces no new facts.

Procedure

  • The orchestrator chooses the source and only critical evidence URLs.
  • Keep evidence packs small enough for the target context window; split or summarize source material when needed.
  • If needed evidence was not retrieved, add it and rerun retrieval rather than asking the model to guess.
  • Use discovery-capable research or a human review for open-ended source discovery and reliability-critical work.

Pitfalls

  • Handing a local model a monolithic fetch-and-write agent loop.
  • Calling a claim verified when the evidence pack does not cover it.
  • Treating a supplied-evidence workflow as web discovery.

Verification checklist

  • Evidence was selected and retrieved before claim verification.
  • Unsupported claims are labeled rather than filled in.
  • The final synthesis is traceable to the evidence pack.

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.