Files
hyperframes/skills/hyperframes/references/plugin-installation.md
T
Wenbo ZhuandClaude Opus 5.5 6857bb08e8 docs(skills): stop directing the agent to install, update or remove skills (#7102)
A third-party skill-trust grader (DeltaVerdict D5) fails any skill text
that has the agent modify its own skills, even when disclosed or gated on
the user. Reword the skill lifecycle, plugin, CLI and scaffold text so it
states facts the agent can relay (skills are versioned with the CLI; the
person installs and updates them, and which command does it) instead of
commands for the agent to run. Every agent-run `init` example passes
--skip-skills, since init otherwise installs missing core skills; the
plugin header, plugin-cli and sfx messages are person-addressed; the
person's install commands are marked as theirs; /style-sampling joins
the on-demand lists. Regenerate skills-manifest.json and update the
pinned reverse init regex.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-04 10:17:14 +00:00

2.6 KiB

Running from an installed plugin

Check the directory two levels above the loaded SKILL.md for plugin.json, .claude-plugin/plugin.json, .codex-plugin/plugin.json, or .cursor-plugin/plugin.json identifying hyperframes, or a Gemini extension manifest. That directory is <PLUGIN_ROOT>. If none exists, this is a standalone skill install; run npx hyperframes directly.

For a plugin installation, these rules apply in every skill and reference:

  • Do not run hyperframes skills update, skills check, or npx skills add. The agent's plugin manager owns installation and updates. Read the skill at <PLUGIN_ROOT>/skills/<name>/SKILL.md; report a missing bundled skill instead of downloading a different release. Resolve all skill references inside this bundle, even if a standalone copy is also installed. Claude exposes the router as /hyperframes:hyperframes; other clients may expose /hyperframes.

  • Replace npx hyperframes (or bare hyperframes) in command examples with:

    node "<PLUGIN_ROOT>/skills/hyperframes/scripts/plugin-cli.mjs" <command> <args...>
    

    Run in the user's project directory, never in the plugin directory. The launcher selects the manifest's CLI version and disables automatic standalone skill installation, including during init. The first call may download that exact CLI version through npm. A download failure is an error, not permission to use latest. Existing project dependency files and lockfiles must not be overwritten to match the plugin; surface a runtime incompatibility before changing them.

  • For bundled Node helpers, use the same launcher with --script <absolute-script-path> <args...>. This passes the release version to their dependency loader. External providers, registry downloads, and existing project dependencies have their own versions; a plugin version alone does not freeze those inputs.

  • Treat the plugin directory as read-only. Put outputs and temporary work in the project or a temporary directory. Pass this plugin root and launcher convention to any delegated agent so it does not fall back to global skills.

Newer skills come through the client's plugin update flow and a session reload, which the person runs. Do not update an installed plugin yourself.

The launcher suppresses CLI update notices as well as standalone skill refreshes, including when running an older CLI with a stale notice cache. It passes the release as HYPERFRAMES_PLUGIN_VERSION for plugin-aware helpers and as HYPERFRAMES_SKILL_PKG_VERSION for the existing helper-package bootstrap. Our release process versions those packages together.