Generate a beautiful, deployable HTML introduction page for any AgentSkill. Reads USAGE.md (preferred) or SKILL.md, parses name, description, and feature sec...
集成
Skill Install Bridge
试用Generate install commands, README snippets, website cards, and social copy for published skills
它能做什么
Generate install commands, README snippets, website cards, and social copy for published skills
技能文档
Skill Install Bridge
Use this skill when a builder needs one clean install surface for a published skill.
When To Use
- A ClawHub skill is published and needs README, landing page, or docs install copy.
- A builder wants one command, one card, and one short explanation users can understand.
- A skill launch needs consistent links across GitHub, X, Substack, and websites.
- A landing page needs a compact install block before the Chrome Web Store or ClawHub link is final.
Workflow
- Collect the skill slug, display name, owner handle, version, and public URL.
- Run the bundled script:
python3 scripts/install_bridge.py \
--slug skill-package-doctor \
--name "Skill Package Doctor" \
--owner zack-dev-cm \
--version 0.1.1 \
--out-dir install-bridge
- Review the generated Markdown, HTML, JSON, and social post text.
- If you intentionally replace existing snippets, add
--force. - Replace placeholders before publishing. Do not invent install commands.
- Put the Markdown snippet in GitHub and the HTML card on landing pages.
- Use the short social text for launch posts or comments.
- Read
references/source-manifest.jsononly when you need package provenance.
Review Rules
- Keep wording simple enough for a non-technical user.
- Use the real ClawHub CLI command:
npx --yes clawhub@0.9.0 install. - Include a no-install fallback: inspect the skill page and copy the usage prompt.
- Do not claim downloads, stars, ratings, or review status unless provided.
- Keep snippets short, copyable, and safe to paste into GitHub.
- If the slug is missing or invalid, stop and ask for it.
- Refuse accidental overwrites unless the user explicitly chooses
--force.
Output
Return:
- install command
- README Markdown snippet path
- landing-page HTML snippet path
- JSON metadata path
- short social launch copy
- missing fields or trust warnings
Stop Conditions
Do not generate launch-ready install copy when:
- the slug is missing or not slug-shaped
- the URL is not HTTPS
- the version is unknown and the user asks for version-specific copy
- the package has not been published or cannot be inspected
相关技能
Install or upgrade a ClawHub skill, then make the global copy under the machine's OpenClaw home `skills/` directory the final source of truth. Use when the u...
Generate Skill skeleton code, SKILL.md, and reference materials following best practices
Quickly open-source a local skill to GitHub (primary) and optionally clawhub.com. Workflow: slug pre-check, fork to opensourceskills, strip internal info, normalize SKILL.md, generate LICENSE/README, init git, push to GitHub with configurable token source, and optionally publish to clawhub. Use when the user says "open-source this skill", "把这个 skill 开源", "发到 github", "publish skill publicly", or "把本地 skill 发开源". Hard rules: never modify the original skill in place, never auto-add force/yes flags, never write tokens to git/remote/memory, and ask the user at decision points.
Understand a user or agent capability need, discover relevant Codex/agent skills, choose the best candidate, install it, and verify the installation. Use whe...
Create or repair local skills from verified, reusable workflows. Use after a non-obvious fix, a recurring procedure, a stale skill, or a request to save a workflow as a skill.