agentleFS
DJDeborahDJDeborah/research-mechanics-skills/skills/research-gap/SKILL.md

research-gap

Skill0 starsChanged 45 days agoMITView on GitHub

Find and test bounded research gaps using a reproducible search ledger, primary-paper capability matrix, counterexample search and falsifiable gap statements. Use for literature-backed novelty assessment, not unsupported first-ever claims.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. ZimoLiao/scholaraio★ 585same name
    2. devinat1/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the search and gap contract.

    line 12
  2. Very specific:

    Run python <skill-dir>/scripts/audit_gap.py <project>/gap.json <project>/search-ledger.csv --out <project>/gap-audit.json.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Research gap

Find what the closest work has not resolved within an explicit problem domain.

  1. Read the search and gap contract. State the intended mechanism, geometry family, boundary protocol, observable and method. Search synonyms and the closest competing approaches, not only the user's phrasing. Browse and open primary sources; titles or snippets do not prove capabilities.
  2. Copy assets/search-ledger.csv and assets/gap.json into the project. They are templates, not literature evidence. Replace demo records. Log query, engine, date, URL/DOI, inclusion decision, and the supporting passage location for each capability assessment.
  3. Build the nearest-work matrix: study → solved capability → scope/control → unresolved capability → direct source. Label unknown full-text access as unknown, not absent.
  4. Actively search for a paper that would invalidate the proposed gap. Narrow or retire a contradicted claim. A finite search cannot establish universal absence.
  5. Run python <skill-dir>/scripts/audit_gap.py <project>/gap.json <project>/search-ledger.csv --out <project>/gap-audit.json. Report search coverage and deduplication, not an automatic novelty verdict.
  6. Deliver two or three bounded gap candidates with scientific consequence, closest counterexample and cheapest decisive test; recommend one based on the actual evidence and feasibility.

Useful handoff: a gap says what remains unresolved; significance says why resolving it matters; the test states what outcome would disprove the proposed contribution. If the user's question is already covered, say so and identify the residual issue.

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.