lookup
Skill0 starsChanged 7 months agoMITView on GitHub
Look up one Zotero item by citekey.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- giacomoguidotto/skillstheir own version, first seen Jul 23, 2026
- theYahia/dadata-mcptheir own version, first seen Mar 31, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- theYahia/dadata-mcp★ 2same name
- giacomoguidotto/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.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
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
- Distinctive: line 6
Use the Zotero MCP server to look up an item by its exact citekey.
- Distinctive: line 8
If the user did not provide a citekey, ask for one.
- Very specific: line 10
Use the Zotero lookup tool with the citekey.
- Distinctive: line 13
Treat this as exact citekey lookup, not broad search.
- Distinctive: line 14
Do not invent metadata.
- Very specific: line 15
If Zotero has no entry for the citekey, say so clearly and list any candidates it returned (near keys with the same surname, year within …
- Distinctive: line 17
When an item is found, return a short metadata summary and include whether fulltext is available.
≈ “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.
Files
Use the Zotero MCP server to look up an item by its exact citekey.
If the user did not provide a citekey, ask for one.
Use the Zotero lookup tool with the citekey.
Rules:
- Treat this as exact citekey lookup, not broad search.
- Do not invent metadata.
- If Zotero has no entry for the citekey, say so clearly and list any
candidatesit returned (near keys with the same surname, year within one). - Report a paper as absent only after
lookupon the likely citekey and a search by author surnames (and year) both miss, and say which checks you ran. - When an item is found, return a short metadata summary and include whether fulltext is available.
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
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.