refresh-research
Skill2 starsChanged 4 months agoMITView on GitHub
Maintainer-only. Re-run web research on README best practices, diff findings against skills/readme/references/, update stale content, bump last-verified dates, and append dated CHANGELOG and research-log entries.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Jamie-BitFlight/claude_skillstheir own version, first seen Sep 23, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Jamie-BitFlight/claude_skills★ 67same 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
3 rules. About 0 are common, 1 is distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Read ${CLAUDE_SKILL_DIR}/references/research-protocol.md and run the research required by the mode.
- Very specific: line 28
Read ${CLAUDE_SKILL_DIR}/references/update-protocol.md and apply it: diff findings against the knowledge base, edit only what changed, bump …
- Distinctive: line 36
Commit with a message summarizing what changed (or that nothing did).
≈ “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.
Files
Refresh research
This is what makes readme-skill a living system. Run from the repo root.
Today's date (from the environment) is used everywhere a date is written.
Modes
- full — re-run all five research clusters in
references/research-protocol.mdwith parallel research agents. Use monthly, or whenquicksurfaces something big. - quick (default) — search for developments since the newest entry in
research/log/, plus re-fetch only the volatile clusters (AI-era practices, GitHub platform features). Use weekly. - source-check — no new research; re-fetch every URL in
skills/readme/references/sources.mdand update each source's status (active / moved / dead). Fast link-rot sweep.
Procedure
- Read
${CLAUDE_SKILL_DIR}/references/research-protocol.mdand run the research required by the mode. Every claim returned must carry a source URL. - Read
${CLAUDE_SKILL_DIR}/references/update-protocol.mdand apply it: diff findings against the knowledge base, edit only what changed, bumpLast verified:dates only for files whose sources were actually re-fetched. - Record the run (always, even when nothing changed):
- append
research/log/YYYY-MM-DD-<mode>.mdwith raw findings and a verdict, - append a dated entry under Research in
CHANGELOG.md, - bump the version in
.claude-plugin/plugin.jsonper the update protocol if KB content changed.
- append
- Commit with a message summarizing what changed (or that nothing did). Do not push without the maintainer's go-ahead unless they asked for the full cycle.
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.

