Agent skill

Fix Worktree Opsx Skills Not Created

by BlackBeltTechnology in BlackBeltTechnology/pi-agent-dashboard

Diagnose/fix worktrees missing the generated openspec- (opsx) skills after worktreeInit.

MITAuto-check passedDevelopment

Install Fix Worktree Opsx Skills Not Created

skills CLI
$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill fix-worktree-opsx-skills-not-created -a claude-code

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

GitHub CLI
$ gh skill install BlackBeltTechnology/pi-agent-dashboard fix-worktree-opsx-skills-not-created --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/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/openspec-workflow/.pi/skills/fix-worktree-opsx-skills-not-created .claude/skills/fix-worktree-opsx-skills-not-created && 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
fix-worktree-opsx-skills-not-created
GitHub stars
315
Token cost
~822 tokens
SKILL.md length
297 words
Files
1
Skills in repo
70
Repo updated
First seen
Licence
MIT

At a glance

Diagnose/fix worktrees missing the generated openspec- (opsx) skills after worktreeInit.

  • Works in 6 steps: Confirm the skills are generated, not… → Confirm the repository declares… → Require a clean git status… → …
  • Tasks that involve Git worktrees
  • SKILL.md covers When to Use, Procedure, Why the old path fails and Pitfalls, plus 1 more section
  • Calls pnpm, git and npx

What it does

Fix Worktree Opsx Skills Not Created is an agent skill from BlackBeltTechnology/pi-agent-dashboard. Diagnose/fix worktrees missing the generated openspec- (opsx) skills after worktreeInit. Root cause: bare npx openspec can resolve a squatted registry stub instead of the real CLI.

Its SKILL.md is about 820 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 Development, covering Git worktrees and Root cause analysis. It works with Git and pnpm. The repository describes itself as: Real-time web dashboard for pi coding-agent sessions. Multi-session view, live chat mirroring, integrated terminal, diff viewer, pi-flows execution, and mobile-first remote… The licence is MIT.

When your agent uses it

  • Tasks that involve Git worktrees
  • Tasks that involve Root cause analysis

Example prompts

  • “/fix-worktree-opsx-skills-not-created”

Requirements

  • Node.js

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Confirm the skills are generated, not committed. .pi/.gitignore contains skills/openspec-*/**; each fresh worktree must run openspec init.
  2. Confirm the repository declares @fission-ai/openspec and identify its package-manager install command. The unscoped npm package openspec…
  3. Require a clean git status --porcelain=v1, then install repository dependencies. For this repository, run pnpm install --frozen-lockfile.
  4. Use the repository-pinned binary when it exists
  5. Verify the CLI reports setup success. Check the lifecycle skills this repository requires by name: openspec-explore, openspec-propose…
  6. Check git status --short. Generated openspec-* skill directories should remain ignored. Review any tracked context-file rewrite before…

What it can do on your machine

Read from SKILL.md and the folder at commit 7a2d171. 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

    Shell commands in SKILL.md call:

    • pnpm
    • git
    • npx

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

  • Network

    No URLs in SKILL.md. Its commands use pnpm, git and npx, 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

Fix Worktree Opsx Skills Not Created loads about 822 tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 297 words of instructions outside code blocks.

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

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 BlackBeltTechnology/pi-agent-dashboard at commit 7a2d171, republished under its MIT licence (© BlackBeltTechnology). 297 words, ~822 tokens.

Download SKILL.mdSave it as .claude/skills/fix-worktree-opsx-skills-not-created/SKILL.md (or your agent's skills folder).
name
fix-worktree-opsx-skills-not-created
description
Diagnose/fix worktrees missing the generated openspec-* (opsx) skills after worktreeInit. Root cause: bare `npx openspec` can resolve a squatted registry stub instead of the real CLI.
version
1
created
2026-07-13
updated
2026-08-20

When to Use

Use when a git worktree lacks the OpenSpec lifecycle skills (.pi/skills/openspec-explore, openspec-propose, and related directories), /opsx: commands are missing, openspec-apply-change stalls, or .pi/settings.json#worktreeInit needs an audit.

Procedure

  1. Confirm the skills are generated, not committed. .pi/.gitignore contains skills/openspec-*/**; each fresh worktree must run openspec init.
  2. Confirm the repository declares @fission-ai/openspec and identify its package-manager install command. The unscoped npm package openspec is a 0.0.0 stub.
  3. Require a clean git status --porcelain=v1, then install repository dependencies. For this repository, run pnpm install --frozen-lockfile.
  4. Use the repository-pinned binary when it exists:
    bash
    pnpm exec openspec init --tools pi --force
    pnpm exec uses the declared local dependency and fails when the binary is absent. In a repository that does not declare the CLI, use the version-pinned scoped package explicitly: npx @fission-ai/openspec@1.6.0 init --tools pi --force.
  5. Verify the CLI reports setup success. Check the lifecycle skills this repository requires by name: openspec-explore, openspec-propose, openspec-apply-change, openspec-update-change, and openspec-archive-change.
  6. Check git status --short. Generated openspec-* skill directories should remain ignored. Review any tracked context-file rewrite before continuing.

Why the old path fails

Bare npx openspec init ... can fetch openspec@0.0.0 when node_modules/.bin/openspec is absent. The stub exits without generating lifecycle skills. Installing dependencies first and using pnpm exec openspec preserves the lockfile-selected CLI and fails visibly when setup is incomplete.

Pitfalls

  • Run the dependency install first. pnpm exec openspec cannot recover a missing local binary.
  • Do not hard-code the number of generated skills or commands. OpenSpec releases generate different sets; validate the required lifecycle names.
  • The worktree-init gate test ! -d .pi/skills/openspec-explore correctly re-triggers initialization when generated skills are absent.
  • openspec init --force can rewrite tracked AGENTS.md or CLAUDE.md. Generated skill directories are safe; tracked context changes require review.

Verification

bash
set -euo pipefail
before_status="$(git status --porcelain=v1)"
if [ -n "$before_status" ]; then
  printf '%s\n' "Refusing recovery in a dirty worktree" >&2
  exit 1
fi
pnpm install --frozen-lockfile
pnpm exec openspec --version
pnpm exec openspec init --tools pi --force
for skill in openspec-explore openspec-propose openspec-apply-change openspec-update-change openspec-archive-change; do
  test -d ".pi/skills/$skill" || exit 1
done
after_status="$(git status --porcelain=v1)"
test -z "$after_status"

Completion requires setup success, every named directory, and empty Git status before and after recovery.

© BlackBeltTechnology, 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 packages/openspec-workflow/.pi/skills/fix-worktree-opsx-skills-not-created of BlackBeltTechnology/pi-agent-dashboard.

Open the folder on GitHubat commit 7a2d171

Compare with similar skills

Fix Worktree Opsx Skills Not Created 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.

Fix Worktree Opsx Skills Not Created compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fix Worktree Opsx Skills Not Created this skillBlackBeltTechnology/pi-agent-dashboard315—~822Automated safety check: PassMIT
Kanvibe Release Deployrookedsysc/kanvibe144—~12kAutomated safety check: NotesAGPL-3.0
Worktrees and Dev Serverspierrecomputer/pierre6.3k—~573Automated safety check: NotesApache-2.0
Worktree StackLanternOps/breeze132—~1.2kAutomated safety check: NotesAGPL-3.0
Devcontainer Devstacklok/toolhive-studio171—~3.8kAutomated safety check: NotesApache-2.0
Voiceover-First DevelopmentDevin-AXIS/iPolloWork6.8k—~879Automated safety check: PassCustom licence

Similar skills

  • Kanvibe Release Deploy

    rookedsysc/kanvibe

    A skill your agent uses whenever releasing or deploying KanVibe desktop from a clean, up-to-date dev checkout: ask only for the target version and release-note approval, then let the AI update…

    144 GitHub stars~12k tokensUpdated today
    DevelopmentAuto-check: notes
  • Worktrees and Dev Servers

    pierrecomputer/pierre

    Explains the Pierre repo's moonx root:wt helper for managed git worktrees, per-worktree port offsets, and cleaning up stale dev servers and test fixtures.

    6.3k GitHub stars~573 tokensUpdated yesterday
    DevelopmentAuto-check: notes
  • Worktree Stack

    LanternOps/breeze

    A skill your agent uses when an agent needs a running, seeded, Playwright-ready Breeze stack for the current git worktree.

    132 GitHub stars~1.2k tokensUpdated yesterday
    DevelopmentAuto-check: notes
  • Devcontainer Dev

    stacklok/toolhive-studio

    Spin up and interact with ToolHive Studio's containerized dev environment (Xvfb + noVNC + DinD).

    171 GitHub stars~3.8k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes
  • Voiceover-First Development

    Devin-AXIS/iPolloWork

    Starts a feature as a demo narration instead of a PRD: you approve the script before any code, then the agent builds in a fresh worktree and opens a PR with proof.

    6.8k GitHub stars~879 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

More from BlackBeltTechnology/pi-agent-dashboard

All 70 skills in this repo
  • Browser

    BlackBeltTechnology/pi-agent-dashboard

    Browser automation via the agent-browser CLI. An agent skill from BlackBeltTechnology/pi-agent-dashboard.

    316 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • CI Troubleshoot

    BlackBeltTechnology/pi-agent-dashboard

    Diagnose failed GitHub Actions runs for pi-agent-dashboard: the 11-file workflow taxonomy, affected-test selection, the release pipeline, known failure modes, and how to read gh run logs and…

    316 GitHub stars~3.5k tokensUpdated today
    Auto-check passed
  • Debug Dashboard

    BlackBeltTechnology/pi-agent-dashboard

    Diagnose problems in the running pi-agent-dashboard system: server.log, /api/health, bridge WebSocket connectivity, vitest triage, known-issue FAQ entries.

    316 GitHub stars~1.6k tokensUpdated today
    Auto-check passed
  • Implement

    BlackBeltTechnology/pi-agent-dashboard

    Disciplined implementation in pi-agent-dashboard: the rebuild matrix (extension→reload, server→restart, client→build+restart, openspec-apply→full rebuild) plus the project's code discipline rules.

    316 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Pi Dashboard

    BlackBeltTechnology/pi-agent-dashboard

    Monitor and control the pi-dashboard server. An agent skill from BlackBeltTechnology/pi-agent-dashboard.

    316 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Session To Guideline

    BlackBeltTechnology/pi-agent-dashboard

    Turn a pi session into a Markdown "how-we-did-it" collaboration guideline: reads the session's JSONL transcript and synthesizes a reusable playbook of which prompts worked, what had to be steered…

    316 GitHub stars~3.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Fix Worktree Opsx Skills Not Created

What does Fix Worktree Opsx Skills Not Created do?

Diagnose/fix worktrees missing the generated openspec- (opsx) skills after worktreeInit. Fix Worktree Opsx Skills Not Created is an agent skill from BlackBeltTechnology/pi-agent-dashboard. Diagnose/fix worktrees missing the generated openspec- (opsx) skills after worktreeInit.

When should I use Fix Worktree Opsx Skills Not Created?

Fix Worktree Opsx Skills Not Created fits situations like: tasks that involve Git worktrees; tasks that involve Root cause analysis.

How do I install Fix Worktree Opsx Skills Not Created in Claude Code?

Run `npx skills add BlackBeltTechnology/pi-agent-dashboard --skill fix-worktree-opsx-skills-not-created -a claude-code`. Or copy the skill folder (packages/openspec-workflow/.pi/skills/fix-worktree-opsx-skills-not-created in BlackBeltTechnology/pi-agent-dashboard) into .claude/skills/fix-worktree-opsx-skills-not-created in your project. Claude Code loads it when a task matches its description.

How do I install Fix Worktree Opsx Skills Not Created in Codex?

Run `npx skills add BlackBeltTechnology/pi-agent-dashboard --skill fix-worktree-opsx-skills-not-created -a codex`. Or copy the skill folder (packages/openspec-workflow/.pi/skills/fix-worktree-opsx-skills-not-created in BlackBeltTechnology/pi-agent-dashboard) into .agents/skills/fix-worktree-opsx-skills-not-created in your project. Codex loads it when a task matches its description.

Can I use Fix Worktree Opsx Skills Not Created 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 BlackBeltTechnology/pi-agent-dashboard --skill fix-worktree-opsx-skills-not-created -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fix-worktree-opsx-skills-not-created, .gemini/skills/fix-worktree-opsx-skills-not-created, .github/skills/fix-worktree-opsx-skills-not-created and .opencode/skills/fix-worktree-opsx-skills-not-created in your project.

What does Fix Worktree Opsx Skills Not Created need to run?

Going by SKILL.md and its folder, Fix Worktree Opsx Skills Not Created needs the command-line tools its instructions call (pnpm, git and npx). Our summary lists: Node.js.

Does Fix Worktree Opsx Skills Not Created access the network?

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

Is Fix Worktree Opsx Skills Not Created 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 Fix Worktree Opsx Skills Not Created use?

Fix Worktree Opsx Skills Not Created 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 Fix Worktree Opsx Skills Not Created use?

About 822 tokens (SKILL.md is roughly 3.3k 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 Fix Worktree Opsx Skills Not Created?

Skills that share tags, products or a category with Fix Worktree Opsx Skills Not Created: Kanvibe Release Deploy (rookedsysc/kanvibe, 144 stars), Worktrees and Dev Servers (pierrecomputer/pierre, 6.3k stars), Worktree Stack (LanternOps/breeze, 132 stars) and Devcontainer Dev (stacklok/toolhive-studio, 171 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fix Worktree Opsx Skills Not Created?

BlackBeltTechnology (a GitHub organization) maintains it in BlackBeltTechnology/pi-agent-dashboard, which has 315 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 10, 2026.

Source: BlackBeltTechnology/pi-agent-dashboard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.