agentleFS
k1p1l0k1p1l0/claude-telegram-supercharged/skills/update/SKILL.md

update

Skill144 starsChanged 8 months agoApache-2.0View on GitHub

Update the Telegram Supercharged plugin to the latest version from GitHub. Use when the statusline shows "⬆ Supercharged", or when the user says "update telegram plugin", "update supercharged", or "telegram:update".

61 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use end, create 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.
  • 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

    note

    Use this skill to record progress, partial findings, hypotheses, and page-anchored evidence while investigating a long document. Call Note aggressively — any time you read a page and confirm, narrow, or update your understanding of the user's question. Triggers include "jot that down", "save this finding", "note that page 7 says X", or (more often) implicit internal signals — you just learned something and want it recoverable later. Notes persist in the session and Review can select among them. Never paraphrase notes back from memory; write them as you go.

    Also in 4 projects that use this

  • kv0906Skill

    inbox

    Quick capture mode (with content) or batch processing mode (no content). GTD-style routing of inbox items to proper folders. Use "/inbox thought to capture" or "/inbox" to process.

    Also in 4 projects that use this

  • jholhewresSkill

    backup

    Backup and restore — files, databases, and system backups

    Also in 3 projects that use this

  • +2 more from microsoft

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 59 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If update is available (or unknown), pull the latest:

    line 31
  2. Distinctive:

    If hashes match, report "Already up to date" and exit.

    line 51
  3. Distinctive:

    Always show the user what changed before applying

    line 94
  4. Distinctive:

    Ask for confirmation before overwriting files

    line 95

“Common” is measured: kept by at least 6 in 10 of the 59 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 Telegram Supercharged Plugin

Pull the latest version from GitHub and apply it to the installed plugin.

Process

Step 1: Check current state

# Get local file hash (Claude Code runs the newest version directory in the cache)
CACHE="$HOME/.claude/plugins/cache/claude-plugins-official/telegram"
LOCAL_FILE="$CACHE/$(ls "$CACHE" | sort -V | tail -1)/server.ts"
LOCAL_HASH=$(shasum -a 256 "$LOCAL_FILE" 2>/dev/null | cut -c1-12)
echo "Local hash: $LOCAL_HASH"

Step 2: Check for updates

# Read cache if available
cat ~/.claude/cache/telegram-update-check.json 2>/dev/null || echo '{"update_available":"unknown"}'

Step 3: Pull latest from GitHub

If update is available (or unknown), pull the latest:

cd /tmp
if [ -d "claude-telegram-supercharged" ]; then
  cd claude-telegram-supercharged && git pull
else
  git clone https://github.com/k1p1l0/claude-telegram-supercharged.git
  cd claude-telegram-supercharged
fi

Step 4: Compare versions

REMOTE_HASH=$(shasum -a 256 /tmp/claude-telegram-supercharged/server.ts 2>/dev/null | cut -c1-12)
echo "Remote hash: $REMOTE_HASH"
echo "Local hash: $LOCAL_HASH"

If hashes match, report "Already up to date" and exit.

Step 5: Show what changed

cd /tmp/claude-telegram-supercharged && git log --oneline -10

Show the user the recent commits and ask for confirmation before updating.

Step 6: Apply update

After user confirms, run the installer from the checkout. It copies server.ts and the skills into the cache directory Claude Code actually runs, keeps the official package.json (its start script keeps bun install output off the MCP channel), and installs the supervisor, the daemon wrapper and the Agentic Mode hook:

TELEGRAM_SUPERCHARGED_DIR=/tmp/claude-telegram-supercharged bash /tmp/claude-telegram-supercharged/install.sh

Then restart: a new Claude Code session, or for the daemon launchctl bootout + launchctl bootstrap (a soft restart doesn't reload the supervisor).

Step 7: Clear update cache

rm -f ~/.claude/cache/telegram-update-check.json

Step 8: Report success

Display:

╔═══════════════════════════════════════════════════════════╗
║  Supercharged Updated!                                    ║
╚═══════════════════════════════════════════════════════════╝

⚠️  Restart the Telegram daemon to apply changes:
   /telegram:daemon restart

   Or write restart signal:
   echo "restart" > ~/.claude/channels/telegram/data/restart.signal

Important Notes

  • Always show the user what changed before applying
  • Ask for confirmation before overwriting files
  • Clear the update cache after successful update so the statusline indicator disappears
  • Remind user to restart the daemon after updating

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.