scholar-monitoring
Skill108 starsChanged 8 months agoMITView on GitHub
This skill should be used when the user asks to "monitor a scholar",
- Reads credentials
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- literature-reviewSkill
- paper-reproductionSkill
- trend-analysisSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 1 is distinctive, and 7 are 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.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Call check_scholar with the researcher's name.
- Very specific: line 32
If degraded=True, the scholar was not found on Semantic Scholar or the API is unavailable
- Very specific: line 37
If recent_papers is non-empty and the user wants thematic analysis, call analyze_trends.
- Very specific: line 48
Call save_to_memory with a summary of the scholar's recent activity.
- Distinctive: line 67
Name format: Use "First Last" format; middle names are generally not needed but can help disambiguate common names
- Very specific: line 75
When analyze_trends returns degraded=True:
- Very specific: line 79
When check_scholar itself returns degraded=True:
- Very specific: line 82
Check candidates in the response for close matches
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Scholar Monitoring Workflow
Monitor a researcher's recent publication activity: fetch their profile and papers, optionally analyze output trends, and save a monitoring note.
Workflow
Step 1: Check scholar activity
Call check_scholar with the researcher's name.
- Parameters:
scholar_name(required; use the researcher's full name as commonly published),max_papers(default 10; increase to 20–30 for career-wide coverage) - Returns: dict with:
scholar: profile dict withname,hIndex,citationCount,affiliations,paperCount,urlrecent_papers: list of paper dicts (title, abstract, year, venue, citation count)candidates: list of top-3 candidate matches (inspect if the top result is wrong)
- If
degraded=True, the scholar was not found on Semantic Scholar or the API is unavailable
Step 2: Analyze paper trends (optional)
If recent_papers is non-empty and the user wants thematic analysis, call analyze_trends.
- Parameters:
topic(use the scholar's name or primary research area as the topic),papers(therecent_paperslist from Step 1) - Returns: dict with
trend_analysis(natural language narrative of the scholar's research focus and evolution) - Skip this step if the user only needs raw paper metadata (no LLM API key required for Step 1 alone)
Step 3: Save monitoring note
Call save_to_memory with a summary of the scholar's recent activity.
- Parameters:
content(monitoring summary — include scholar name, hIndex, recent paper titles, and trend analysis if available),kind="note",user_id(default"default"),scope_type="global",confidence(0.0–1.0; suggest 0.9 for factual publication data) - Returns: dict with
createdorskippedstatus
Note on Scholar Lookup
check_scholar searches Semantic Scholar by name. Common issues:
- Name diacritics: Names with accents (e.g., "Müller", "Bengio") may need the ASCII variant ("Muller", "Yoshua Bengio") if exact-match fails
- New researchers: Very new researchers may have limited or no Semantic Scholar
records — check
paperCountin the returned profile - Name ambiguity: The
candidatesfield in the response lists the top 3 matches; inspect these if the top result appears to be the wrong person (wrong affiliation, wrong research area) - Name format: Use "First Last" format; middle names are generally not needed but can help disambiguate common names
Degraded Mode
analyze_trends (Step 2) requires a configured LLM API key. check_scholar (Step 1)
and save_to_memory (Step 3) do not require LLM.
When analyze_trends returns degraded=True:
- Set
OPENAI_API_KEYorANTHROPIC_API_KEYand restart the MCP server - Skip Step 2 and proceed directly to Step 3 with a summary based on raw paper metadata
When check_scholar itself returns degraded=True:
- This indicates the scholar was not found or the Semantic Scholar API is unavailable
- Try an alternate name spelling or abbreviation
- Check
candidatesin the response for close matches
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.

