Two open threads, one doc. #652 reads the Cursor guide as wrong because
this repository has no .cursor/ directory; the guide means the user's
project but never says so. #494 reports Cursor failing with "An
unexpected error occurred on our servers" when a skill is attached to a
prompt with /, after which every message in that chat fails; the
maintainer confirmed it is Cursor-side, named referencing the skill by
name as the workaround, and said the setup doc should carry a note.
Add one sentence after the intro saying every .cursor/ path is in the
reader's project and this repo ships none, linking to the install step.
Add a troubleshooting row for the attach error with the workaround and a
pointer to #494, which stays open as a known host issue. Add the
project-not-repo clause to the README's Cursor entry.
Closes#652. Refs #494.
#542 reports following docs/copilot-setup.md and finding no /spec, /plan,
/build or /test. The doc already says the wrappers are Claude Code
commands, but in the middle of a paragraph that a reader scanning for
install steps walks past; the reporter did. The maintainer's answer on
the issue was that the doc should make this explicit.
Add a callout right after the intro that names the commands, says they
are expected to be absent, and points to the skill-name mapping and the
optional aliases. Add a lead-in to the troubleshooting list that rules
out the expected case before the real diagnostics. Add one sentence to
the README's Copilot entry so the expectation is set before the doc is
opened.
Closes#542
Pi implements the Agent Skills standard natively and discovers skills from
~/.agents/skills/ and .agents/skills/ with no plugin or config file, so its
package manager installs the pack directly from git.
Follows the Adding a Host Guide bar (CONTRIBUTING.md): one line, host name
and install command only.
Refs #355, #365
The fx setup guide (#507) was closed under the new host-guide bar, which
gives hosts no maintainer has run one line in docs/other-hosts.md. Add
that line with the corrected install command from the guide: copy the
skills into .fx/skills/, fx's native project root, discovered from 0.0.5
on. No affiliation with fx or Vercel Labs.
Refs #504, #507
The README install section now lists only hosts a maintainer has run.
Every other host gets one line in docs/other-hosts.md, with no setup
page, vendor links or branding, and host guides are reviewed in the
order they were opened. Oh My Pi moves there.
#616 went in within six days, ahead of community host guides that had
been open since July and August, and no maintainer has run Dojo. That
was an inconsistent merge, not a problem with the submission. Dojo is
welcome back under the host-listing bar added in this change.
OMP installs the existing Claude Code marketplace plugin and routes skills
natively, so the bootstrap extension stacked a second router (see #574).
Drop the extension, root package.json, and its test; keep the setup guide
and README entry, now pointing at the marketplace install, with the OMP
tool mapping as a doc section.
docs/advanced-per-agent-configuration.md calls itself the canonical
reference for keeping SKILL.md frontmatter portable, yet nothing in the
repository links to it. Add the frontmatter rule it states to the anatomy
doc's Frontmatter section, and point at it from the README contributing
paragraph and CONTRIBUTING's frontmatter step, so contributors meet the
rule where they read the format.
The plugin's SessionStart hook injected using-agent-skills/SKILL.md as
additionalContext on every session. Claude Code already discovers and
routes skills from their descriptions, so the hook stacks a second
router on the native one — the pattern docs/getting-started.md warns
against ("That creates two routers for the same task"), measured at
~3.5k wasted cache-creation tokens per session in #569.
Delete hooks/hooks.json (the registration; the plugin now ships no
hooks) and keep hooks/session-start.sh as a standalone script for hosts
without native skill routing, matching the fix shape suggested in the
issue. Update the hook header, CONTRIBUTING.md, codex-setup.md, and
gemini-cli-setup.md to match.
`## All 24 Skills` is contradicted by the sentence directly beneath it —
"The pack includes 25 skills total" — and by the section's own contents:
skills listed under the heading 25
directories under skills/ 25
validate-skills --strict 25 skills checked
difference (none)
The section does list every skill, meta-skill included, in its own `Meta`
subsection. So 25 is the honest number for the heading.
The nearby "24 lifecycle skills plus the `using-agent-skills` meta-skill"
phrasing is correct and is left alone — 24 is a real count, just not of
what the heading is counting.
Also retargets the one inbound anchor, which the rename would otherwise
break:
docs/adoption-guide.md:5 ...README.md#all-24-skills -> #all-25-skills
That link is the only reference to the anchor anywhere in the repo
(checked across md/json/ts/js), so the rename is complete.
Gates: validate-skills --strict 25 skills, 0 errors, 0 warnings; the JS
suite 44 pass / 0 fail.
A step that exists because one model gets a specific call wrong
constrains agents that would have solved the task directly and spends
turns stronger models need for the actual work — cross-model transfer
measurements (WikiSkill, arXiv:2608.27454) show such skills can leave
a stronger model worse off than no skill at all.
Add 'Write the Procedure, Not the Workaround' to skill-anatomy: the
rule (no step justified only by naming a model, version, or one
agent's private tool name), the two smells (over-specified mechanics,
fragmented diagnostics), a model-neutral writing principle, and a
matching pre-flight line in CONTRIBUTING.
Affected agy 1.1.x releases report the 8 legacy command TOMLs as
converted to skills, but the converted wrappers never appear in the
slash-command or skill catalog — plugin validate passing confirms the
files are well formed, not that /build and the other wrappers exist.
Replace the slash-command table with a wrapper-to-direct-invocation
map (/agent-skills:<skill-name>, /agents for the webperf persona),
note the wrapper-only behaviors that are unavailable (/build auto
orchestration, /ship persona fan-out), warn against the YAML
frontmatter workaround that breaks Gemini CLI's TOML parser, and add
a post-install verification step. Align the README blurb with the
same guidance.
Addy Osmani