Name: GSD Update
Author: Skills Guide Bot

Automated summary

Updates GSD to its latest version, shows the changelog, and handles skill resynchronization and reapplying local customizations.

Strengths

Detects whether the install is local or global before checking npm and displaying the changelog for what changed
Warns before installing and reminds you to restart after the update and cache clearing
Offers dedicated modes: --sync to align managed skills across runtime roots, --reapply to restore local edits via a three-way comparison, and --next/--rc for release candidates
Keeps the standard flow (scope detection, changelog preview, custom-file backup) even on the RC channel

Limitations

Assumes GSD was installed via npm and that workflow files exist under ~/.claude/gsd-core
Three-way patch reapplication may require manual conflict resolution
Does not cover distribution channels other than npm (@latest / @next)

When to use it

When you want to update GSD cleanly while keeping skills synced across runtimes and preserving your local customizations.

When not to use it

If GSD was not installed through npm, or if you need to manage updates for a different tool.

Security analysis

Caution

Quality score82/100

The skill is a legitimate GSD updater with no direct destructive, exfiltration, or obfuscated instructions. However, it uses powerful tools including Bash, Write, and Edit to update packages, modify files, and clear caches, and its detailed behavior depends on external workflow files, so it warrants caution rather than safe.

Findings

•Declares Bash, Write, and Edit, enabling package installation, file modification, and cache clearing during updates.
•Delegates execution to local workflow files under ~/.claude/gsd-core/workflows/ that are not included in the SKILL.md, so the full command surface cannot be audited from this file alone.

How this analysis is made

Examples

Standard update

Update GSD to the latest version and show me the changelog before installing.

Release candidate

Install the latest GSD release candidate using the @next channel and show me what changed.

Sync and reapply

Sync my GSD skills across runtimes after the update, then reapply my local modifications.

name: gsd-update description: "Update GSD to latest version with changelog display" argument-hint: "[--sync | --reapply | --next | --rc]" allowed-tools:

Read
Write
Edit
Bash
Glob
Grep
AskUserQuestion

<objective> Check for GSD updates, install if available, and display what changed.

Routes to the update workflow which handles:

Version detection (local vs global installation)
npm version checking
Changelog fetching and display
User confirmation with clean install warning
Update execution and cache clearing
Restart reminder </objective>

<execution_context> @~/.claude/gsd-core/workflows/update.md </execution_context>

<flags> - **--sync**: Sync managed GSD skills across runtime roots so multi-runtime users stay aligned after an update. Runs the sync-skills workflow (--from, --to, --dry-run, --apply flags supported). - **--reapply**: Reapply local modifications after a GSD update. Uses three-way comparison (pristine baseline, user-modified backup, newly installed version) to merge user customizations back. Runs the reapply-patches workflow. - **--next** (alias **--rc**): Target the `@next` RC dist-tag instead of `@latest` so you can install or refresh a release candidate (e.g. `1.4.0-rc.1`) through the normal update flow — scope/runtime detection, changelog preview, custom-file backup, and cache clearing all still apply. Omitting it keeps targeting `@latest` (no change). See ADR #660 for the RC channel. - **(no flag)**: Standard update — check for new version, show changelog, install. </flags> <process> Parse the first token of $ARGUMENTS: - If it is `--sync`: strip the flag, execute the sync-skills workflow (passing remaining args for --from/--to/--dry-run/--apply). - If it is `--reapply`: strip the flag, execute the reapply-patches workflow. - Otherwise (including `--next` / `--rc`): execute the update workflow end-to-end, passing `$ARGUMENTS` through so the workflow's parse_update_channel step can select the release channel. </process>

<execution_context_extended> @~/.claude/gsd-core/workflows/sync-skills.md @~/.claude/gsd-core/workflows/reapply-patches.md </execution_context_extended>

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/gsd-update-mrx3xxm8/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/gsd-update-mrx3xxm8' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/gsd-update-mrx3xxm8/download' --output '.skill-downloads/gsd-update-mrx3xxm8/SKILL.md.part' && mv '.skill-downloads/gsd-update-mrx3xxm8/SKILL.md.part' '.skill-downloads/gsd-update-mrx3xxm8/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/gsd-update-mrx3xxm8/SKILL.md' && test -s '.skill-downloads/gsd-update-mrx3xxm8/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/gsd-update' && cp -R '.skill-downloads/gsd-update-mrx3xxm8' '.claude/skills/gsd-update'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/gsd-update-mrx3xxm8'

openskills read 'gsd-update-mrx3xxm8'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/gsd-update-mrx3xxm8/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Configure a Chat Channel with SecretRefs

DevOps

Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.

Claude CodeCodexintermediateSafe 387,940

Skills Guide Bot

Investigate ClickHouse CI Failures

DevOps

Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.

Claude CodeadvancedSafe 49,516

Skills Guide Bot