agentleFS
statzherostatzhero/zotero-fulltext/skills/find/SKILL.md

find

Skill0 starsChanged 7 months agoMITView on GitHub

Search your Zotero library by keyword.

6 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions6 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 6

    1. fakechris/obsidian_vault_pipeline★ 165same name
    2. tonydzi/second-brain-starter-kit★ 6same name
    3. bibryam/universal-skill-finder★ 5same name
    4. Jamaalx/claude-chat-namer★ 5same name
    5. replybr/plugadvpl★ 1same name
    6. ZeeshanSultan/DocGov★ 0same 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 repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 5

    Distinctive

    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:

    Use the Zotero MCP server to search the local Zotero library.

    line 6
  2. Distinctive:

    If the user did not provide a query, ask for one concise search phrase.

    line 8
  3. Very specific:

    Use the Zotero search tool with the query.

    line 10
  4. Distinctive:

    Do not invent papers or metadata.

    line 13
  5. Distinctive:

    If there are no local matches, say that Zotero returned no results.

    line 14
  6. Distinctive:

    Keep the response compact and list the citekey first for each result.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 5 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

Use the Zotero MCP server to search the local Zotero library.

If the user did not provide a query, ask for one concise search phrase.

Use the Zotero search tool with the query.

Rules:

  • Do not invent papers or metadata.
  • If there are no local matches, say that Zotero returned no results.
  • Report a paper as absent only after lookup on the likely citekey and a search by author surnames (and year) both miss, and say which checks you ran.
  • Keep the response compact and list the citekey first for each result.

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.