Skills Management · recorded 2026-08-29 · applies to 1 tool(s) ✓ Verified

Problem: Same package won't install across products — Codex can't read skills / CodeBuddy channel error —— Trove problem library

Verified 2026-08-29no local file read permission / channel mismatch — grant local file read in Codex desktop settings first, then install per product form.

Quick fix

# One-liner: Codex desktop — grant local-file read permission in settings first, then install per the product form
# Settings → Permissions/Security → allow local file reads; install: cp -r skills ~/.codex/skills/superpowers

What you will run into

Codex desktop can't read skills after install (no local-file read permission); CodeBuddy and other products report channel mismatch errors installing OpenSpec/Superpowers. The same package, but it won't install in a different product.

Why this happens

  • Desktop without local-file read permission granted can't read the skills directory;
  • Different products have different format/directory conventions for "site docs": Codex desktop, CodeBuddy, and Claude Code each have their own; mixing them causes channel-mismatch errors.
ProductForm
Codexskills directory (pure files, measured here)
Claude CodePlugin marketplace or skills directory
CodeBuddyIts own channel (first check the form that product supports for Superpowers)

"Plugins/skills" are not the same thing across products: each product defines its own "what a skill looks like, which directory it lives in, how it gets scanned".

Codex desktop uses a pure-file skills directory (scanned at startup; every subdirectory with a SKILL.md is a skill); Claude Code uses the plugin marketplace or a skills directory; CodeBuddy has its own channel.

Moving product A's directory into product B means reading A's layout with B's scanner — it can't find things and reports "missing files / channel mismatch".

Desktop apps also add a system-permission layer: reading outside the user directory requires an explicit grant; without it, "the directory exists but can't be read".

So wiring into any product is always two fixed steps: check what form that product recognizes first (site docs statements), then place it per that product's directory convention (and handle desktop permissions).

Judging "why can't it read" is also layered: directory location (convention layer) -> permission granted (system layer) -> format correct (content layer).

Step by step

1. Grant local-file read permission in the product's settings — Required

Codex desktop: enable local file read permission in settings (CSDN 2026-06 case).

2. Install per the product's form — Required

cp -r skills ~/.codex/skills/superpowers

Codex uses the skills directory; Claude Code uses the plugin marketplace or skills directory; CodeBuddy uses its own channel.

3. On channel-mismatch errors, stick to the product's own channel — Required

Don't mix install paths; follow the product's built-in plugin install channel.

How to confirm it works

Codex-form install/uninstall closure (measured output here):

[install] superpowers installed: OK (cp -r skills ~/.codex/skills/superpowers)
[uninstall] superpowers removed: OK (rm -rf, zero leftovers)

Skills visible in a new session; CodeBuddy/Claude Code each verify via their own channel.

Other environments

EnvironmentNotes
Codex desktopGrant local-file read permission first, then install via the skills directory
CodeBuddyUse its own channel; check supported forms first (CSDN 2026-07)
Claude CodePlugin marketplace or skills directory
Channel mixingOn errors, return to the product's own channel
Not measuredClaude Code form (no login state); Codex form is pure files with no permission/port/background requirements

Symptom

Codex desktop cannot read skills after install (no local file read permission); CodeBuddy and other products report channel-inconsistent errors when installing OpenSpec/Superpowers.

Cause

The desktop app was not granted local file read permission; different products have different formats/dir conventions for "site docs" (Codex desktop, CodeBuddy, Claude Code each have their own).

Solution

  1. Grant local file read permission in the corresponding product's settings.
  2. Install per product form: Codex uses the skills dir; Claude Code uses the plugin marketplace or skills dir; CodeBuddy uses its own channel (first check which Superpowers form that product supports).
  3. On channel-inconsistent errors, follow the product's built-in plugin install channel; do not mix.
Verification Evidence
  • Web case: CSDN Codex desktop (2026-06) — permission issue; CSDN CodeBuddy (2026-07) — channel inconsistency.
  • This marketplace's form boundary: Codex form is pure files (no permission/port/background needs); Claude Code form not tested (no login state).

Verified install / uninstall in this marketplace (2026-08-27/28)

Local verification record Local verification record

  • local repro log; connectivity: + site docs.

Conflict notes

  • possible-compatible: oh-my-claudecode / agent-governance-toolkit / deepcode (no shared write surface; co-install judgement per conflict matrix).
  • possible-conflict: ruflo (Claude form shares ~/.claude/skills write surface, not tested) — when installing ruflo on the same machine, prefer the Codex form.
  • Form dimension: the Codex form only writes ~/.codex/skills/superpowers, the smallest shared surface with other entries; the Claude plugin-marketplace form writes in the Claude plugin dir; evaluate per form.

Name confusion

No high-risk same-name entries (mind singular/plural spelling differences when searching).

Applicable tools (1)

This problem is linked from the tool pages below — reachable from either side.

superpowers

Source & evidence

Recorded Verified ✓ VerifiedApplies to 1 tool(s)
Entries contain locally measured or reviewable-source solutions; unmeasured items are explicitly labeled.

← Skills Management domain | Problem Catalog Experience | Facing another issue? Go to the Helpdesk