agentleFS
patrickjajapatrickjaja/claude-desktop-extra/.claude/skills/fresh-upstream/SKILL.md

fresh-upstream

Skill761 starsChanged yesterdayMITView on GitHub

For claude-desktop-extra - wipe any existing extracted Claude Desktop bundles and extract a fresh, CLEAN, UNPATCHED copy of the latest official Claude Desktop Linux .deb into ./tmp/ for patch analysis. Fetches + GPG/SHA256-verifies the latest .deb if missing or stale, then extracts app.asar via asar (NOT the build script, which applies patches).

  • Deletes or force-pushes

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Leave the freshly downloaded ./tmp/claude-desktop_*_amd64.deb in place and leave ./build/ packages alone unless the user asked for a full …

    line 43

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

Fresh upstream extract (clean, unpatched)

Goal: a pristine unpatched bundle in ./tmp/ so patch work compares against the true upstream. Run from the repo root. ./tmp/ is gitignored.

Critical: scripts/build-patched-tarball.sh runs apply_patches.py - its output is PATCHED. For a clean baseline use the manual fetch + asar flow below.

Steps

  1. cd to the repo and read tracked version:
    cd "$(git rev-parse --show-toplevel)"
    cat .upstream-version
  2. Resolve latest upstream version (GPG + SHA256-verified via the canonical fetcher):
    LATEST_VERSION=$(.github/scripts/apt-fetch-verify.sh poll)
    echo "upstream latest: $LATEST_VERSION"
    Report latest vs .upstream-version so the user sees whether this is a new version.
  3. Download + verify the official .deb if missing or stale. apt-fetch-verify.sh download resolves the highest amd64 version, downloads the .deb into ./tmp/, and verifies its SHA256 against the signed Packages index (which is itself verified against the GPG-signed Release):
    mkdir -p ./tmp
    DEB=$(.github/scripts/apt-fetch-verify.sh download amd64 ./tmp)
    echo "verified .deb: $DEB"
    (~150MB.) If the download or verification fails, stop and report - do NOT trust an unverified .deb.
  4. Wipe old extracted bundles (project-local only - never touch ~/.config/Claude):
    rm -rf ./tmp/extract ./tmp/app.asar.contents ./extract ./build/work 2>/dev/null || true
    Leave the freshly downloaded ./tmp/claude-desktop_*_amd64.deb in place and leave ./build/ packages alone unless the user asked for a full clean.
  5. Extract clean, unpatched to ./tmp/. Crack the .deb (dpkg-deb -x, or ar + tar if dpkg-deb is unavailable), then asar extract the app.asar:
    dpkg-deb -x "$DEB" ./tmp/extract
    asar extract ./tmp/extract/usr/lib/claude-desktop/resources/app.asar ./tmp/app.asar.contents
    • Unpatched main bundle: ./tmp/app.asar.contents/.vite/build/index.js
    • Renderer bundles: ./tmp/app.asar.contents/.vite/renderer/*/assets/*.js
    • ion-dist (3P-config SPA): packed as ./tmp/extract/usr/lib/claude-desktop/resources/ion-dist.asar since v4.29.0 (a plain ion-dist/ dir before); read it with asar extract ./tmp/extract/usr/lib/claude-desktop/resources/ion-dist.asar ./tmp/ion-dist
    • i18n: ./tmp/app.asar.contents/resources/i18n/*.json (inside app.asar since v4.29.0)
  6. Sanity check and report:
    node --check ./tmp/app.asar.contents/.vite/build/index.js && echo "OK: clean unpatched index.js parses"
    ls -la ./tmp/app.asar.contents/.vite/build/
    Report: upstream version extracted, where the unpatched index.js is, whether it's a new version vs .upstream-version. If new, suggest /update. If just refreshing for analysis, suggest /audit.

Notes

  • This does NOT patch, build, or bump anything - it only stages a clean bundle.
  • Distinguish "clean unpatched" (this skill, manual .deb crack + asar) from "patched build" (./scripts/build-local.sh).
  • The official .deb bundles its own Electron (see usr/lib/claude-desktop/version in the deb tree) and prebuilt node-pty for both arches - we do not self-manage either.
  • Stale extracts have different minified names → always re-extract before patch debugging if ./tmp is older than today.

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.