agentleFS
iwe-orgiwe-org/marketing-workspace/.claude/skills/update/SKILL.md

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

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.
  • kennethleungtySkill

    pause

    Pause — stop the music (alias for /stop)

    Also in 4 projects that use this

  • torarnvSkill

    end

    Wrap up a work session. Updates memory files, logs decisions and lessons, appends to the session log.

    Also in 3 projects that use this

  • MicrosoftSkill

    create

    Also in 4 projects that use this

  • bitwize-music-studioSkill

    tutorial

    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

  • MicrosoftSkill

    help

    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

  • jholhewresSkill

    backup

    Backup and restore — files, databases, and system backups

    Also in 3 projects that use this

  • +1 more from microsoft

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
  1. Very specific:

    Keep engagement.* frontmatter close to reality so the weekly digest and the user's judgment work from current numbers.

    line 8
  2. Very specific:

    Write back: Update each post's engagement.upvotes, engagement.comments, engagement.views (only fields you actually observed), and a dated …

    line 27
  3. Distinctive:

    Never invent numbers. An unfetchable page is a note, not an estimate.

    line 54
  4. Distinctive:

    Don't refresh more often than the venue meaningfully changes — daily at most.

    line 57

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Scope. iwe find --filter '{type: post, stage: published}' --project '$title,platform,resource,published' -f json, keep posts that carry a resource, published in the last 14 days (or the range the user asked for).
  2. Fetch. For each post, fetch its resource and 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 in engagement.notes instead of guessing. Reddit blocks most server-side fetches: retry the post through https://embed.reddit.com/<post-path> — the embed route serves score and comment count when reddit.com refuses. If a post is gone at the source (deleted/removed by moderators), set stage: removed and status: deprecated, and say so in the report.
  3. Write back. Update each post's engagement.upvotes, engagement.comments, engagement.views (only fields you actually observed), and a dated one-line engagement.notes when something needs context.
  4. Replies. iwe find --filter '{type: reply, stage: published}' --project '$title,resource,published,outcome' -f json, last 14 days. Fetch each resource and update engagement.upvotes, engagement.replies, and the thread's thread_upvotes and thread_comments. Append what the comment drew to ## Discussion as dated bullets. For a reply published three or more days ago with no outcome, propose one from what the discussion literally shows (none, replied, asked, will-try, tried) and set it with reviewed: <today> once the user agrees; raise an existing outcome when the conversation has moved. A comment gone at the source gets stage: removed and status: deprecated.
  5. Success lines. For posts published more than a week ago with no verdict, check the success line against the evidence: set success_evidence, and a verdict with verdict_date when the evidence could be read. A line that cannot be observed gets unobservable and no verdict.
  6. Validate. iwe schema validate. In a git repository, commit update: engagement refresh — <n> posts, <n> replies.
  7. 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. tried needs a person saying they used the product.
  • Don't refresh more often than the venue meaningfully changes — daily at most.

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.