agentleFS
ignatovvignatovv/VibePad/.claude/skills/update-site/SKILL.md

update-site

Skill67 starsChanged 9 months agoMITView on GitHub

Update the VibePad website with new DMG and appcast entry

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 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.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Update the VibePad website: upload the new DMG for the download button and add an appcast entry for Sparkle auto-updates.

    line 7
  2. Distinctive:

    Ask the user for any values not provided as arguments or inferrable from context:

    line 11
  3. Very specific:

    If the user just ran /release, these values should be available in the conversation context — use them without asking again.

    line 18
  4. Very specific:

    Use the current date/time for <pubDate>.

    line 41

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

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

Update the VibePad website: upload the new DMG for the download button and add an appcast entry for Sparkle auto-updates.

Gathering info

Ask the user for any values not provided as arguments or inferrable from context:

  1. Version (e.g. 1.1) — the sparkle:shortVersionString
  2. Build number (e.g. 2) — the sparkle:version
  3. EdDSA signature — the sparkle:edSignature="..." value from sign_update
  4. File length in bytes — the length="..." value from sign_update

If the user just ran /release, these values should be available in the conversation context — use them without asking again.

Steps

  1. Read the current appcast: Read /Users/vyuignatiov/code/vibepad-site/appcast.xml.
  2. Replace the existing <item> entry in <channel> with the new version's data. Use this format:
    <item>
      <title>Version {VERSION}</title>
      <pubDate>{RFC 2822 date, e.g. "Sat, 08 Feb 2026 12:00:00 -0800"}</pubDate>
      <sparkle:version>{BUILD_NUMBER}</sparkle:version>
      <sparkle:shortVersionString>{VERSION}</sparkle:shortVersionString>
      <sparkle:minimumSystemVersion>14.0</sparkle:minimumSystemVersion>
      <enclosure
        url="https://vibepad.now/assets/VibePad.dmg"
        type="application/x-apple-diskimage"
        sparkle:edSignature="{ED_SIGNATURE}"
        length="{FILE_LENGTH}"
      />
    </item>

Use the current date/time for <pubDate>. Replace (don't stack) — the site serves a single DMG at a stable URL, so old entries would have stale signatures/lengths. Sparkle only checks the newest compatible item anyway.

  1. Copy the DMG to the website assets (stable filename for the download button):
cp "/Users/vyuignatiov/code/VibePad/VibePad-${VERSION}.dmg" "/Users/vyuignatiov/code/vibepad-site/assets/VibePad.dmg"
  1. Commit and push the vibepad-site repo (auto-deploys on push):
cd ~/code/vibepad-site && git add appcast.xml assets/VibePad.dmg && git commit -m "Update to VibePad ${VERSION}" && git push
  1. Report to the user:
    • Show the updated appcast entry
    • Remind them to verify at https://vibepad.now/appcast.xml

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.