New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Update

by romiluz13 in romiluz13/cc10x

Safe cc10x upgrade through the Claude Code plugin CLI. An agent skill from romiluz13/cc10x.

MITAuto-check: notesAgent Workflows

Install Update

skills CLI
$ npx skills add romiluz13/cc10x --skill update -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install romiluz13/cc10x update --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/romiluz13/cc10x.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/cc10x/skills/update .claude/skills/update && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
update
GitHub stars
164
Token cost
~1.7k tokens
SKILL.md length
880 words
Files
1
Skills in repo
22
Repo updated
First seen
Licence
MIT

At a glance

Safe cc10x upgrade through the Claude Code plugin CLI. An agent skill from romiluz13/cc10x.

  • Works in 7 steps: Discovery → Locate The Marketplace → Capture Local Patches (Optional) → …
  • : updating cc10x
  • SKILL.md covers Phase 1: Discovery, Phase 2: Locate The Marketplace, Phase 3: Capture Local Patches… and Phase 4: Refresh The Marketplace, plus 3 more sections
  • Calls claude and git

What it does

Update is an agent skill from romiluz13/cc10x. Safe cc10x upgrade through the Claude Code plugin CLI. Lists every installed scope, refreshes the marketplace, updates each scope, and optionally carries local patches over to the new install. Use this skill when: updating cc10x, upgrading, pulling latest cc10x, syncing plugin, refreshing cache, or checking for new versions. Triggers: update cc10x, upgrade cc10x, pull cc10x, sync plugin, refresh cc10x, check for updates, new version, update plugin, upgrade plugin.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Hooks and plugins. The repository describes itself as: The Loop Engine for Claude Code — engineer the loop, not the prompt. 1 router · 9 agents · 16 skills · 4 workflows. Fail-closed gates, test honesty, anti-anchored review. The licence is MIT.

When your agent uses it

  • : updating cc10x
  • Pulling latest cc10x
  • Refreshing cache
  • Checking for new versions

Example prompts

  • “/update”

Requirements

  • Pre-approved tools (allowed-tools): Read, Bash, AskUserQuestion

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Discovery
  2. Locate The Marketplace
  3. Capture Local Patches (Optional)
  4. Refresh The Marketplace
  5. Update Each Scope
  6. Re-apply Patches
  7. Restart Or Reload

What it can do on your machine

Read from SKILL.md and the folder at commit f346ebe. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • claude
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Update loads about 1.7k tokens when it runs. Until then it costs about 119 tokens; SKILL.md has 880 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~119
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Bash, AskUserQuestion

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from romiluz13/cc10x at commit f346ebe, republished under its MIT licence (© romiluz13). 880 words, ~1,702 tokens.

Download SKILL.mdSave it as .claude/skills/update/SKILL.md (or your agent's skills folder).
name
update
description
Safe cc10x upgrade through the Claude Code plugin CLI. Lists every installed scope, refreshes the marketplace, updates each scope, and optionally carries local patches over to the new install. Use this skill when: updating cc10x, upgrading, pulling latest cc10x, syncing plugin, refreshing cache, or checking for new versions. Triggers: update cc10x, upgrade cc10x, pull cc10x, sync plugin, refresh cc10x, check for updates, new version, update plugin, upgrade plugin.
allowed-tools
Read, Bash, AskUserQuestion

cc10x Update

Upgrade cc10x with the claude plugin CLI. The CLI owns the plugin registry and the install cache; this skill never edits either one directly and never assumes where they live.

Workflow: Discover installs → Locate the marketplace → (optional) Capture local patches → Refresh marketplace → Update each scope → Re-apply patches → Restart or reload.

Capture comes before the refresh on purpose: marketplace update moves the marketplace checkout to the new version, and the pristine baseline is read from that checkout. The marketplace checkout is often a shallow clone, so the baseline for an installed version is resolvable only when that version's commit is within the checkout depth; for an older install it usually is not. Carry-over is best-effort, and the skill says so plainly when it cannot run.

Phase 1: Discovery

bash
claude plugin list --json

The output is a JSON array. Keep only entries whose id is cc10x@cc10x. Each entry has version, scope (user, project, local, or managed), enabled, installPath, and, for project and local scopes, projectPath.

The same plugin can appear several times: once per scope, and once per project for project and local scopes. Different entries may point at different versions and different installPath values.

If no cc10x@cc10x entry exists → STOP and tell the user cc10x is not installed (install it with claude plugin install cc10x@cc10x).

Show the user one row per entry (scope, projectPath if present, version, installPath). For a project or local entry whose projectPath no longer exists on disk, mark it "skipped: project directory no longer exists"; it cannot be updated from there.

Phase 2: Locate The Marketplace

bash
claude plugin marketplace list --json

Take the entry named cc10x and set LOC to its installLocation. The plugin source is $LOC/plugins/cc10x. If the entry or that directory is missing → STOP and tell the user the marketplace is not registered (claude plugin marketplace add romiluz13/cc10x).

Phase 3: Capture Local Patches (Optional)

Ask the user whether they have modified cached cc10x files. Skip this phase only if they say no. Run it before Phase 4.

The scope gate comes later (Phase 4), so capture covers every discovered entry, not only those chosen afterwards. For each distinct old version among them, pin the pristine baseline: the commit that set that version in the marketplace checkout.

bash
SHA=$(git -C "$LOC" log --format=%H -S"\"version\": \"<old>\"" -- plugins/cc10x/.claude-plugin/plugin.json | tail -1)
git -C "$LOC" show "$SHA:plugins/cc10x/.claude-plugin/plugin.json"

tail -1 takes the oldest match, the commit that introduced the version string. The show output must contain "version": "<old>". The baseline is resolvable only if SHA is non-empty and the show output contains the old version string. If not (checkout depth is the usual cause: a one-commit shallow clone only resolves the version it currently holds) → ABORT carry-over: say plainly that carry-over is unavailable for that version because local modifications cannot be separated from upstream content, then offer the two safe choices: continue the update without carry-over, or stop so the user can save their edits by hand first. Do not guess a baseline from the new marketplace version.

With a pinned SHA, for each file in git -C "$LOC" ls-tree -r --name-only "$SHA" -- plugins/cc10x, save a per-file patch (pristine to locally modified, so applying it later re-adds the user's changes). A file that differs exits 1 from diff; a file missing from the install, or any exit 2, is reported rather than patched:

bash
git -C "$LOC" show "$SHA:plugins/cc10x/<file>" | diff -u - "<old installPath>/<file>" > "<backup dir>/<file with / replaced by __>.patch"

Entries that share an installPath share one result; capture it once. Use a backup directory the user approves (for example a cc10x-update-backup-<date> directory under the system temp directory). Report the modified files, files missing from the install, and files present only in the old installPath.

Gate: if local modifications exist, ask: "Save these patches and carry them over after the update?"

Show full SKILL.md (290 more words)Show less

Phase 4: Refresh The Marketplace

bash
claude plugin marketplace update cc10x

If it exits non-zero, show its output and STOP: the available version is unknown, so do not claim success or continue to Phase 5. Saved patches stay in the backup directory.

Installed versions only change in Phase 5. To learn the available version, read .claude-plugin/plugin.json under $LOC/plugins/cc10x. If every entry already matches that version → report "already up to date" and STOP.

Gate: show installed versus available versions and ask the user which scopes to update.

Phase 5: Update Each Scope

For each selected entry:

bash
claude plugin update cc10x@cc10x --scope <scope>

For project and local entries, run the command from the entry's projectPath so the CLI resolves the right project; if that directory no longer exists, skip the entry and say so. Do not run it for managed scope; tell the user managed installs are updated by whoever administers them.

If a command fails, report its output and continue with the remaining scopes; do not retry with other flags.

Phase 6: Re-apply Patches

Run claude plugin list --json again and read the new installPath for each updated entry. For each saved patch, apply it to the same file under the new installPath (the explicit target file makes header paths irrelevant):

bash
patch --forward "<new installPath>/<file>" "<patch file>"

If a hunk is rejected (a .rej file), show both versions and ask the user how to resolve it. Copy files that existed only in the old installPath into the new one. Report patches applied clean, conflicts, and files restored.

Phase 7: Restart Or Reload

Updates apply only to a fresh session. Tell the user to restart Claude Code or run /reload-plugins. Report old version → new version for each scope updated.

You cannot restart or reload the session yourself, and you cannot verify the new version is active until the user does.

© romiluz13, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/cc10x/skills/update of romiluz13/cc10x.

Open the folder on GitHubat commit f346ebe

Compare with similar skills

Update next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Update compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Update this skillromiluz13/cc10x164—~1.7kAutomated safety check: NotesMIT
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k11 repos~4.1kAutomated safety check: NotesApache-2.0
Claude Code Agent Developmentanthropics/claude-plugins-official38k8 repos~2.8kAutomated safety check: PassApache-2.0
Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase10k11 repos~3.5kAutomated safety check: PassMIT
Plugin Settings Patternanthropics/claude-plugins-official38k7 repos~3kAutomated safety check: PassApache-2.0
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0

Similar skills

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 11 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Skill Developer Guide

    diet103/claude-code-infrastructure-showcase

    A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.

    10k GitHub starsUsed in 11 repos~3.5k tokens
    Agent WorkflowsAuto-check passed

  • Plugin Settings Pattern

    anthropics/claude-plugins-official

    Official

    Shows how Claude Code plugins keep per-project settings and state in .claude/plugin-name.local.md files with YAML frontmatter and a markdown body.

    38k GitHub starsUsed in 7 repos~3k tokens
    Agent WorkflowsAuto-check passed

  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Command Development

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code slash commands: Markdown files with YAML frontmatter, arguments, file references, bash context and interactive prompts.

    38k GitHub starsUsed in 10 repos~4.8k tokens
    Agent WorkflowsAuto-check passed

More from romiluz13/cc10x

All 22 skills in this repo

  • Building

    romiluz13/cc10x

    A skill your agent uses when writing production code test-first: the RED-GREEN-REFACTOR cycle, false-RED detection, vertical slicing, scope escalation, test process discipline, and code generation…

    164 GitHub stars~2.7k tokensUpdated today
    Auto-check: notes

  • Diff Driven Docs

    romiluz13/cc10x

    A skill your agent uses when a BUILD phase completes, a commit is staged, or a PR is about to be created, and the diff has not yet been reflected in documentation.

    164 GitHub stars~2.7k tokensUpdated today
    Auto-check: notes

  • Planning

    romiluz13/cc10x

    A skill your agent uses when writing an execution plan or a decision RFC: task decomposition, context references, validation levels, risk-based testing, ADR format, plan completeness gate, and…

    164 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Verification

    romiluz13/cc10x

    A skill your agent uses when judging whether a task reached its goal, not just finished: the gate function, self-critique gate, validation levels, evidence array protocol, and goal-backward lens.

    164 GitHub stars~1.9k tokensUpdated today
    Auto-check: notes

  • Agent Common

    romiluz13/cc10x

    A skill your agent uses when a cc10x agent starts a task: the shared preamble for the memory protocol, the contract format, and the output rules.

    164 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Cc10x Guide

    romiluz13/cc10x

    Answers questions about cc10x itself — what it is, how to install and configure it, how the router, workflows, memory, and hooks operate, and how to troubleshoot.

    164 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

Categories

Questions about Update

What does Update do?

Safe cc10x upgrade through the Claude Code plugin CLI. An agent skill from romiluz13/cc10x. Update is an agent skill from romiluz13/cc10x. Safe cc10x upgrade through the Claude Code plugin CLI.

When should I use Update?

Update fits situations like: : updating cc10x; pulling latest cc10x; refreshing cache; checking for new versions.

How do I install Update in Claude Code?

Run `npx skills add romiluz13/cc10x --skill update -a claude-code`. Or copy the skill folder (plugins/cc10x/skills/update in romiluz13/cc10x) into .claude/skills/update in your project. Claude Code loads it when a task matches its description.

How do I install Update in Codex?

Run `npx skills add romiluz13/cc10x --skill update -a codex`. Or copy the skill folder (plugins/cc10x/skills/update in romiluz13/cc10x) into .agents/skills/update in your project. Codex loads it when a task matches its description.

Can I use Update in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add romiluz13/cc10x --skill update -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/update, .gemini/skills/update, .github/skills/update and .opencode/skills/update in your project.

What does Update need to run?

Going by SKILL.md and its folder, Update needs the command-line tools its instructions call (claude and git). Its frontmatter pre-approves these tools: Read, Bash, AskUserQuestion.

Does Update access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Update safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Update use?

Update is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Update use?

About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Update?

Skills that share tags, products or a category with Update: Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars), Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars) and Plugin Settings Pattern (anthropics/claude-plugins-official, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Update?

romiluz13 (a GitHub user) maintains it in romiluz13/cc10x, which has 164 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on October 7, 2026.

Source: romiluz13/cc10x on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.