mirror of
https://github.com/EveryInc/compound-engineering-plugin.git
synced 2026-09-19 01:09:55 +08:00
8c762bee3c
The 'Script Path References in Skills' checklist claimed bare relative
paths resolve against the skill directory on all platforms and that no
env-var prefix is needed. That directly contradicted the same file's
'Permission gate on extracted scripts' section (and the empirical
#764/#811/#898 reality): the runtime Bash tool runs from the project
CWD, so a bare scripts/... path misses. This is the authoring root cause
that kept reintroducing the bug into skills.
Rewrite the two runtime-invocation bullets to require
${CLAUDE_SKILL_DIR:-.}, cross-reference the authoritative permission-gate
section, and state honestly that the :-. fallback does not resolve to the
bundled script on Codex/Gemini. Keep (and clarify) the third bullet: a
backtick *read-time* reference does resolve against the skill dir on all
platforms.