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

Packmind Update Playbook

by PackmindHub in PackmindHub/packmind

A skill your agent uses when updating, adding, fixing, changing, or deprecating Packmind playbook artifacts (standards, commands, skills).

Apache-2.0Auto-check passed

Install Packmind Update Playbook

skills CLI
$ npx skills add PackmindHub/packmind --skill packmind-update-playbook -a claude-code

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

GitHub CLI
$ gh skill install PackmindHub/packmind packmind-update-playbook --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/PackmindHub/packmind.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/packmind-update-playbook .claude/skills/packmind-update-playbook && 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
packmind-update-playbook
GitHub stars
317
Token cost
~1.9k tokens
SKILL.md length
797 words
Files
12 (incl. references)
Skills in repo
35
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when updating, adding, fixing, changing, or deprecating Packmind playbook artifacts (standards, commands, skills).

  • Deprecating Packmind playbook artifacts (standards
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Explicit phrases like update packmind standard
  • Add a packmind skill

What it does

Packmind Update Playbook is an agent skill from PackmindHub/packmind. Use when updating, adding, fixing, changing, or deprecating Packmind playbook artifacts (standards, commands, skills). Triggers on explicit phrases like "update packmind standard", "add a packmind skill", "fix packmind command", "change packmind playbook", "deprecate a standard". Also triggers — even without an explicit request — whenever the conversation reveals an opportunity: a new coding convention was just agreed on, a recurring pattern emerged, a workflow changed, a rule was found outdated, or the user says…

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 17 other files, including reference files (for example `packmind-versions/0.21.0/apply-changes.md`, `packmind-versions/0.23.0/apply-changes.md` and `packmind-versions/0.35.0/apply-changes.md`).

The repository describes itself as: Packmind seamlessly captures your engineering playbook and turns it into AI context, guardrails, and governance. The licence is Apache-2.0.

When your agent uses it

  • Deprecating Packmind playbook artifacts (standards
  • Explicit phrases like update packmind standard
  • Add a packmind skill
  • Fix packmind command

Example prompts

  • “update packmind standard”
  • “add a packmind skill”
  • “fix packmind command”
  • “/packmind-update-playbook”

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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

Packmind Update Playbook loads about 1.9k tokens when it runs, and up to ~6.6k if it reads all its reference files. Until then it costs about 216 tokens; SKILL.md has 797 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~216
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.6k

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 passed

The automated check found no risky patterns in SKILL.md.

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 PackmindHub/packmind at commit 67de8a2, republished under its Apache-2.0 licence (© PackmindHub). 797 words, ~1,880 tokens.

Download SKILL.mdSave it as .claude/skills/packmind-update-playbook/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
name
packmind-update-playbook
description
Use when updating, adding, fixing, changing, or deprecating Packmind playbook artifacts (standards, commands, skills). Triggers on explicit phrases like "update packmind standard", "add a packmind skill", "fix packmind command", "change packmind playbook", "deprecate a standard". Also triggers — even without an explicit request — whenever the conversation reveals an opportunity: a new coding convention was just agreed on, a recurring pattern emerged, a workflow changed, a rule was found outdated, or the user says things like "we always do X", "let us remember to Y", "that is the pattern we use". If there is any chance the conversation established a convention or exposed a gap, invoke this skill proactively. This skill defines a mandatory workflow: do NOT edit artifact files directly — follow all phases regardless of change size.

Update Playbook

Run "packmind --version" to get the current cli installation.

Find the highest version at or below the cli version in this list:

  • 0.21.0
  • 0.23.0
  • 0.35.0 Remember this value as $PACKMIND_CLI_VERSION for the rest of the skill.

Evaluate the user's intent against existing Packmind artifacts (standards, commands, skills) to identify what needs creating or updating. Produce a structured change report, then apply approved changes using the playbook CLI workflow.

⚠️ MANDATORY WORKFLOW — This skill defines a strict sequence: Understanding Your Request → Summarizing Changes → Analyzing Playbook → Change Report → Applying Changes. Do NOT skip steps or edit artifact files directly. Even for a single-line change, follow every step. The workflow ensures changes are reviewed, approved, submitted, and propagated correctly.

Understanding Your Request

STOP. This phase runs FIRST, before anything else. No file reads, no CLI commands, no subagents until this gate passes.

Analyze the user's input and conversation context to determine intent:

Case A: No prior conversation / empty input

The skill was invoked standalone with no context. Ask:

"What Packmind artifact do you want to modify? For example: a standard (coding rule/convention), a command (multi-step workflow), or a skill (specialized capability). Please describe what you'd like to change."

BLOCK — do not proceed until the user responds.

Case B: Explicit intent found

The user explicitly asked to update, add, fix, or change a Packmind artifact. Extract an intent summary:

  • Target artifact(s): which standard(s), command(s), or skill(s) to modify (or "new")
  • Kind of change: create or update
  • Specifics: any details the user provided about the change

Proceed to Summarizing Changes with this validated intent.

Case C: Opportunity detected from conversation

The conversation reveals a playbook update opportunity — e.g., a convention was established, a pattern emerged, a workflow was changed, or a known artifact is now stale — but the user did not explicitly ask for a playbook update. Summarize the opportunity and ask:

"I noticed an opportunity to update the Packmind playbook: <brief description>. Would you like me to run the update workflow?"

BLOCK — do not proceed until the user confirms.

Case D: No intent and no opportunity

If the conversation contains no references to modifying Packmind artifacts and no detectable update opportunity, tell the user:

"I didn't detect any intent or opportunity to modify the Packmind playbook. What artifact would you like to update — a standard, command, or skill? Please describe the change."

BLOCK — do not proceed until the user responds.

Summarizing Changes

Only proceed after Understanding Your Request validates intent (explicit request or confirmed opportunity).

Summarize the validated intent before launching any subagents. Extract:

  • Which artifact(s) the user wants to modify and what kind of change
  • Any specifics the user provided about the desired change
  • If prior conversation exists, relevant context that supports the intent (patterns observed, decisions made, problems encountered)

This intent summary is passed as input to all subagents.

Show full SKILL.md (329 more words)Show less
Analyzing Playbook

CLI health check: Before launching subagents, run packmind --version. If it fails, stop immediately and tell the user: "The Packmind CLI is not available or not working. Please check your installation before proceeding." Do not continue.

No subagent support? If the Task tool is unavailable, perform all three domain analyses sequentially in the current session — run each steps/analyze-*.md analysis one after another before proceeding to Change Report.

Launch all three as Task(general-purpose) subagents simultaneously — do not wait for one before starting the others. Each subagent handles its own listing, filtering, and deep analysis in one pass.

Construct each prompt as:

## Validated Intent

<the intent summary from Summarizing Changes>

## Analysis Task

<full contents of the corresponding steps/analyze-*.md file>
SubagentStep FileOutput
Standardssteps/analyze-standards.mdStandards change report
Commandssteps/analyze-commands.mdCommands change report
Skillssteps/analyze-skills.mdSkills change report

For each domain, decide whether to launch or skip based on the validated intent's target artifact type:

  • Launch if the intent mentions or affects that artifact type (standard, command, or skill)
  • Always launch skills — skill accuracy must be checked against any behavioral change
  • Limit scope to the targeted artifact type when the intent is explicit and narrow (e.g., "update standard X" → standards only, no commands or unrelated skills)
Change Report

After all subagents complete, consolidate their reports. Before numbering, deduplicate: if multiple subagents propose modifying the same artifact, merge those into one entry combining both rationales — do not list the same artifact twice. Number every change sequentially so the user can selectively approve:

## Playbook Change Report

<!-- Only include sections that have changes. Omit empty sections entirely. -->
<!-- Ordering reflects priority: skill accuracy first, then standards, then commands. -->
<!-- New commands have a high bar — see domain-commands.md for criteria. -->

### Skill Updates
1. [skill] <name>: <what changed and why>

### New Skills
2. [skill] <name>: <reason>

### Standard Updates
3. [standard] <name>: <what changed and why>

### New Standards
4. [standard] <name>: <reason>

### New Commands
5. [command] <name>: <reason>

### Command Updates
6. [command] <name>: <what changed and why>

Only include sections that have actual changes — omit empty sections entirely. Order by priority: skills first, then standards, then commands.

Present this report and ask the user for approval:

  • Single change: ask "Do you accept this change?"
  • Multiple changes: ask "Which changes to apply?" and accept:
    • All: apply every numbered change
    • Inclusion list: "1, 3, 5" or "only 2 and 6"
    • Exclusion list: "all but 4" or "everything except 2, 7"
Applying Changes

Follow the procedure in packmind-versions/<$PACKMIND_CLI_VERSION>/apply-changes.md. Pass it the list of approved changes (with their numbers and details) from the Change Report above.

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

Files

SKILL.md and 11 other files (references) in .agents/skills/packmind-update-playbook of PackmindHub/packmind.

  • SKILL.md
  • LICENSE.txt
  • packmind-versions/0.21.0/apply-changes.md
  • packmind-versions/0.23.0/apply-changes.md
  • packmind-versions/0.35.0/apply-changes.md
  • references/agent-skills-specification.md
  • references/create-command-procedure.md
  • references/create-skill-procedure.md
  • references/create-standard-procedure.md
  • steps/analyze-commands.md
  • steps/analyze-skills.md
  • steps/analyze-standards.md

Open the folder on GitHubat commit 67de8a2

Compare with similar skills

Packmind Update Playbook 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.

Packmind Update Playbook compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Packmind Update Playbook this skillPackmindHub/packmind317—~1.9kAutomated safety check: PassApache-2.0
Fixalirezarezvani/claude-skills28k1 repos~765Automated safety check: PassMIT
Update Docsvercel/next.js143k—~1.9kAutomated safety check: PassMIT
Orch Change Featureaffaan-m/ECC276k1 repos~420Automated safety check: PassMIT
Make Changesremix-run/remix33k—~2.4kAutomated safety check: PassMIT
Openclaw Updateopenclaw/openclaw392k—~1.5kAutomated safety check: PassMIT

Similar skills

  • Fix

    alirezarezvani/claude-skills

    Fix failing or flaky Playwright tests. An agent skill from alirezarezvani/claude-skills.

    28k GitHub starsUsed in 1 repo~765 tokens
    Testing & QAAuto-check passed

  • Update Docs

    vercel/next.js

    Official

    This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature"…

    143k GitHub stars~1.9k tokensUpdated today
    Documents & OfficeAuto-check passed

  • Orch Change Feature

    affaan-m/ECC

    Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit.

    276k GitHub starsUsed in 1 repo~420 tokens
    Auto-check passed

  • Make Changes

    remix-run/remix

    Create or update Remix repo change files under packages//.changes.

    33k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Openclaw Update

    openclaw/openclaw

    Route routine updates of an existing local or remote OpenClaw Gateway to its installation owner, with automatic session recovery.

    392k GitHub stars~1.5k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Fix Dependabot

    remotion-dev/remotion

    Official

    Fix a Dependabot PR by updating all monorepo instances of the dependency, running bun install, and pushing

    63k GitHub stars~509 tokensUpdated today
    DevelopmentAuto-check passed

More from PackmindHub/packmind

All 35 skills in this repo

  • Michel CLI Demo Recorder

    PackmindHub/packmind

    Produce proof-of-execution demos of the Packmind CLI (packmind-cli) as terminal-styled images (colors and formatting preserved exactly), for embedding in a GitHub PR.

    317 GitHub stars~3.4k tokensUpdated today
    Auto-check passed

  • Michel UI Demo Recorder

    PackmindHub/packmind

    Record polished UI demo videos and screenshots of a running web app using Playwright MCP — for client deliverables, release notes, feature walkthroughs, or bug repros.

    317 GitHub stars~6.4k tokensUpdated today
    Auto-check passed

  • Packmind Create Skill

    PackmindHub/packmind

    Guide for creating effective skills. An agent skill from PackmindHub/packmind.

    317 GitHub stars~3.5k tokensUpdated today
    Auto-check: notes

  • Doc Audit

    PackmindHub/packmind

    Audit Packmind end-user documentation (apps/doc/) for broken links, outdated CLI references, non-existent concepts, misleading information, and missing coverage.

    317 GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Feature Sprint

    PackmindHub/packmind

    Execute the implementation plan produced by /feature-spec. An agent skill from PackmindHub/packmind.

    317 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Michel Packmind Engineer Review

    PackmindHub/packmind

    Review an implemented GitHub issue the way a senior Packmind engineer would — the human-judgment checks that ESLint, the TypeScript compiler, and e2e tests cannot catch (authorization scoping…

    317 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Questions about Packmind Update Playbook

What does Packmind Update Playbook do?

A skill your agent uses when updating, adding, fixing, changing, or deprecating Packmind playbook artifacts (standards, commands, skills). Packmind Update Playbook is an agent skill from PackmindHub/packmind. Use when updating, adding, fixing, changing, or deprecating Packmind playbook artifacts (standards, commands, skills).

When should I use Packmind Update Playbook?

Packmind Update Playbook fits situations like: deprecating Packmind playbook artifacts (standards; explicit phrases like update packmind standard; add a packmind skill; fix packmind command.

How do I install Packmind Update Playbook in Claude Code?

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

How do I install Packmind Update Playbook in Codex?

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

Can I use Packmind Update Playbook 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 PackmindHub/packmind --skill packmind-update-playbook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/packmind-update-playbook, .gemini/skills/packmind-update-playbook, .github/skills/packmind-update-playbook and .opencode/skills/packmind-update-playbook in your project.

What does Packmind Update Playbook need to run?

SKILL.md names no scripts, command-line tools or credentials: Packmind Update Playbook is instructions for the agent only.

Does Packmind Update Playbook access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Packmind Update Playbook safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Packmind Update Playbook use?

Packmind Update Playbook is published under the Apache-2.0 licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Packmind Update Playbook use?

About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.7k tokens, read only when the agent opens those files.

What are the alternatives to Packmind Update Playbook?

Skills that share tags, products or a category with Packmind Update Playbook: Fix (alirezarezvani/claude-skills, 28k stars), Update Docs (vercel/next.js, 143k stars), Orch Change Feature (affaan-m/ECC, 276k stars) and Make Changes (remix-run/remix, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Packmind Update Playbook?

PackmindHub (a GitHub organization) maintains it in PackmindHub/packmind, which has 317 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 9, 2026.

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