一键在 Manus 中运行任何 Skill

skill-publish

星标3

分支0

更新时间2026年5月20日 18:14

Package a locally built skill and publish it to the madebymadhouse/skills repo. Handles copying files, reviewing for internals to scrub, updating the README table, and pushing. Use when a skill has been built or updated locally and needs to go into the public skills repo. Triggers on "publish skill", "push this skill", "add skill to the repo", "package my skill".

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

madebymadhouse

madebymadhouse/skills

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Skill Publish

Takes a skill from ~/.claude/commands/ and packages it into the public skills repo.

Arguments

Skill to publish: $ARGUMENTS

Step 1 - Stage

~/.claude/commands/skill-publish/scripts/stage.sh "$ARGUMENTS"

If the script exits with an error, stop and explain what's wrong.

Step 2 - Review for internals

Read every file in ~/dev/mad-house/skills/skills/$ARGUMENTS/ and check for:

Hardcoded IPs or hostnames
Specific container or service names from Mad House infrastructure
Orinadus references of any kind
Email addresses or personal information
Tokens, API keys, passwords, or anything that looks like a secret
Hardcoded paths that are specific to this machine (e.g. /home/samhc/ beyond ~, specific org names in ~/dev/)

Mad House branding and org identity (e.g. madebymadhouse, mad-house/lab) is fine to keep. Generic paths using ~ or $HOME are fine.

If you find anything that needs scrubbing, fix it before continuing.

Step 3 - Update the README

Open ~/dev/mad-house/skills/README.md and add the skill to the correct section of the skills table. Use the same one-line description style as existing entries.

If it does not fit an existing section, add a new one.

Step 4 - Commit and push

cd ~/dev/mad-house/skills && git add . && git commit -m "Add $ARGUMENTS skill

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>" && git push

Confirm the push succeeded and give the user the GitHub URL for the skill folder.

同仓库更多 Skills

同仓库

incubate

madebymadhouse/skills

Mad House project lifecycle manager. Create, list, stage, promote, ship, and archive projects in ~/dev/mad-house/lab. Every project has a stage (concept → prototype → building → shipped → maintained → archived) and a type (code, game, creative, tool, experiment, content, bot). Use when managing lab projects, moving a project between stages, promoting from lab to a GitHub org, marking something as shipped, or archiving a project.

2026-05-273

repo-bootstrap

madebymadhouse/skills

Bootstrap a new GitHub repo with all standard Mad House files. Creates the repo, clones it locally under the correct org path, and writes README, .gitignore, .env.example, Dockerfile, CHANGELOG, and AGENTS.md template. Triggers on "new repo", "bootstrap a repo", "create a new project", "start a new repo", "scaffold repo".

2026-05-273

agent-fleet

madebymadhouse/skills

Manage the Mad House agent fleet. List all agents in the central registry, check which repos have which agents deployed, and sync agents from the registry to target repos. Use when adding a new agent to the fleet, syncing agents across repos, auditing what agents are deployed where, or rebuilding the agent registry. Triggers on "sync agents", "deploy agents", "what agents are deployed", "add agent to repo", "agent fleet", "update agents".

2026-05-203

banner-design

madebymadhouse/skills

Generate SVG banners and navigation buttons for GitHub README files. Creates repeatable, customizable SVG assets - hero banners with title, subtitle, and tagline, and sets of rounded-corner navigation buttons with Inter font. Use when building or refreshing a repo README, updating branding, or generating any SVG visual assets. Triggers on "generate banner", "create svg banner", "make readme buttons", "banner for the readme", "design banner", "add banner to readme".

2026-05-203

cargo-check

madebymadhouse/skills

Run cargo fmt, clippy, and tests on a Rust workspace before committing. Catches format failures that break CI. Triggers on "cargo check", "check rust", "run rust tests", "before I commit rust", "fmt and test", "check the workspace", "is the rust build clean".

2026-05-203

co-author-fix

madebymadhouse/skills

Check whether the last git commit in the current repo has the Claude co-author trailer. If missing, amend it. Triggers on "add co-author", "fix co-author", "missing co-author", "add claude to commit", "co-author trailer".

2026-05-203

name	skill-publish
description	Package a locally built skill and publish it to the madebymadhouse/skills repo. Handles copying files, reviewing for internals to scrub, updating the README table, and pushing. Use when a skill has been built or updated locally and needs to go into the public skills repo. Triggers on "publish skill", "push this skill", "add skill to the repo", "package my skill".
argument-hint	<skill-name>
compatibility	Designed for Claude Code at Mad House. Requires ~/dev/mad-house/skills/ to be cloned and up to date.
allowed-tools	Bash Read Edit
disable_model_invocation	true

Skill Publish

Takes a skill from ~/.claude/commands/ and packages it into the public skills repo.

Arguments

Skill to publish: $ARGUMENTS

Step 1 - Stage

~/.claude/commands/skill-publish/scripts/stage.sh "$ARGUMENTS"

If the script exits with an error, stop and explain what's wrong.

Step 2 - Review for internals

Read every file in ~/dev/mad-house/skills/skills/$ARGUMENTS/ and check for:

Hardcoded IPs or hostnames
Specific container or service names from Mad House infrastructure
Orinadus references of any kind
Email addresses or personal information
Tokens, API keys, passwords, or anything that looks like a secret
Hardcoded paths that are specific to this machine (e.g. /home/samhc/ beyond ~, specific org names in ~/dev/)

Mad House branding and org identity (e.g. madebymadhouse, mad-house/lab) is fine to keep. Generic paths using ~ or $HOME are fine.

If you find anything that needs scrubbing, fix it before continuing.

Step 3 - Update the README

Open ~/dev/mad-house/skills/README.md and add the skill to the correct section of the skills table. Use the same one-line description style as existing entries.

If it does not fit an existing section, add a new one.

Step 4 - Commit and push

cd ~/dev/mad-house/skills && git add . && git commit -m "Add $ARGUMENTS skill

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>" && git push

Confirm the push succeeded and give the user the GitHub URL for the skill folder.