update
Skill6 starsChanged 3 days agoMITView on GitHub
Refresh engagement metrics (upvotes, comments, views) on published posts and thread replies by fetching their canonical URLs, propose reply outcomes that are due, then print an engagement report. Use when the user asks to "update engagement", "refresh metrics", or "how are the posts doing". Default scope is the last 14 days.
65 other projects use a version of this.
Adopted by
Most recently taken up by
- finolabs/finolabs-vibecodetheir own version, first seen Nov 16, 2026
- patrickjaja/claude-desktop-extratheir own version, first seen Nov 15, 2026
- FYClamityDestiny/vettedtheir own version, first seen Nov 15, 2026
- shivasaini04/nanocrewtheir own version, first seen Nov 15, 2026
- finolabs/vibecodetheir own version, first seen Nov 15, 2026
- onetapstudiogames/1f3d9-citylifetheir own version, first seen Nov 13, 2026
Used with
Projects with it also use pause, end and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
kennethleungtySkillpause
Pause — stop the music (alias for /stop)
Also in 4 projects that use this
torarnvSkillend
Wrap up a work session. Updates memory files, logs decisions and lessons, appends to the session log.
Also in 3 projects that use this
MicrosoftSkillcreate
Also in 4 projects that use this
bitwize-music-studioSkilltutorial
Provides interactive guided album creation for new users. Use when the user is new to the plugin or asks for a walkthrough of the album creation process.
Also in 3 projects that use this
MicrosoftSkillhelp
Entry point for the MedImageInsight plugin, covering the getting-started walkthrough, how the skills work, what MI2 is, and troubleshooting.
Also in 8 projects that use this
jholhewresSkillbackup
Backup and restore — files, databases, and system backups
Also in 3 projects that use this
- +1 more from microsoft
Other versions65 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 65
- anthropics/knowledge-work-plugins★ 36ksame name
- Q00/ouroboros★ 6.4ksame name
- vellum-ai/vellum-assistant★ 1.5ksame name
- patrickjaja/claude-desktop-extra★ 761same name
- me2resh/apexyard★ 542same name
- daloopa/investing★ 488same name
- TokenRollAI/cc-plugin★ 483same name
- egregore-labs/egregore★ 293same name
- k1p1l0/claude-telegram-supercharged★ 144same name
- kv0906/pm-kit★ 138same name
55 more not listed
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
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 63 edited versions we read keep these.
2
Distinctive
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 8
Keep engagement.* frontmatter close to reality so the weekly digest and the user's judgment work from current numbers.
- Very specific: line 27
Write back: Update each post's engagement.upvotes, engagement.comments, engagement.views (only fields you actually observed), and a dated …
- Distinctive: line 54
Never invent numbers. An unfetchable page is a note, not an estimate.
- Distinctive: line 57
Don't refresh more often than the venue meaningfully changes — daily at most.
“Common” is measured: kept by at least 6 in 10 of the 63 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.
Files
Update engagement
Keep engagement.* frontmatter close to reality so the weekly digest and the
user's judgment work from current numbers. Replies are refreshed the same way,
but their measure is outcome, not score.
Steps
- Scope.
iwe find --filter '{type: post, stage: published}' --project '$title,platform,resource,published' -f json, keep posts that carry aresource, published in the last 14 days (or the range the user asked for). - Fetch. For each post, fetch its
resourceand extract what the platform shows: upvotes/points, comment count, views/impressions where visible. Platforms differ — read what's actually on the page; if a fetch fails or the page hides numbers, record the failure inengagement.notesinstead of guessing. Reddit blocks most server-side fetches: retry the post throughhttps://embed.reddit.com/<post-path>— the embed route serves score and comment count whenreddit.comrefuses. If a post is gone at the source (deleted/removed by moderators), setstage: removedandstatus: deprecated, and say so in the report. - Write back. Update each post's
engagement.upvotes,engagement.comments,engagement.views(only fields you actually observed), and a dated one-lineengagement.noteswhen something needs context. - Replies.
iwe find --filter '{type: reply, stage: published}' --project '$title,resource,published,outcome' -f json, last 14 days. Fetch eachresourceand updateengagement.upvotes,engagement.replies, and the thread'sthread_upvotesandthread_comments. Append what the comment drew to## Discussionas dated bullets. For a reply published three or more days ago with nooutcome, propose one from what the discussion literally shows (none,replied,asked,will-try,tried) and set it withreviewed: <today>once the user agrees; raise an existing outcome when the conversation has moved. A comment gone at the source getsstage: removedandstatus: deprecated. - Success lines. For posts published more than a week ago with no
verdict, check thesuccessline against the evidence: setsuccess_evidence, and averdictwithverdict_datewhen the evidence could be read. A line that cannot be observed getsunobservableand no verdict. - Validate.
iwe schema validate. In a git repository, commitupdate: engagement refresh — <n> posts, <n> replies. - Report. Print a table — post or reply title, venue, upvotes, comments, and the change since the last recorded values — then the outcomes set this run, plus one line calling out anything notable (a post taking off, a venue consistently flat).
Rules
- Never invent numbers. An unfetchable page is a note, not an estimate.
- An outcome is what someone wrote, not what the score suggests.
triedneeds a person saying they used the product. - Don't refresh more often than the venue meaningfully changes — daily at most.
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.

