Run any Skill in Manus with one click

share-skill

Stars2

Forks0

UpdatedJuly 2, 2026 at 11:39

Package an installed Claude Code skill into a shareable zip in a fresh temp folder, then open that folder in Finder. Use when the user says "/share-skill <name>", "share the X skill", "bundle/export/package a skill to send someone", or wants a skill zipped up to hand off.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

magnusrodseth

magnusrodseth/dotfiles

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

File Explorer

2 files

SKILL.md

readonly

name	share-skill
description	Package an installed Claude Code skill into a shareable zip in a fresh temp folder, then open that folder in Finder. Use when the user says "/share-skill <name>", "share the X skill", "bundle/export/package a skill to send someone", or wants a skill zipped up to hand off.
disable-model-invocation	true
argument-hint	["skill-name"]
allowed-tools	Bash(bash ), Bash(open )

Share Skill

Package one installed skill into a .zip inside a fresh temp folder and open that folder in Finder, ready to hand off.

Steps

Identify the target skill from the user's request. They may write /share-skill the /humanize skill, share humanize, or give a path. Extract the bare skill name (strip a leading /, ignore filler like "the" and "skill"). If no skill is named, ask which one.
Run the packager, passing the name. Use this skill's own base directory (shown when the skill loaded) for the script path:
```
bash "<this-skill-base-dir>/scripts/share-skill.sh" <skill-name>
```
The script resolves the skill (searching ./.claude/skills, $CLAUDE_CONFIG_DIR/skills, then ~/.claude/skills), dereferences symlinks so the archive is self-contained, excludes junk (.DS_Store, .git, *-cache*, node_modules, __pycache__), zips it, drops the zip in a fresh temp folder, and opens that folder in Finder. Pass a full path instead of a name if the skill lives elsewhere.
Report the Zip: and Folder: paths from the script output. Tell the user Finder is open on that folder, and that a recipient installs the skill by unzipping into ~/.claude/skills/ (personal) or a project's .claude/skills/ (project), then starting a new session.

Notes

Output lands in a readable, date-stamped folder: /tmp/shared-skills/<skill-name>_<YYYY-MM-DD_HHMMSS>/<skill-name>.zip.
The zip's top-level folder is the skill name, so it unzips to <skill-name>/SKILL.md.
The Finder step is macOS-only; the zip is still built on other platforms.
For richer distribution (versioning, bundling agents/hooks/MCP, a marketplace), package as a plugin with a .claude-plugin/plugin.json instead. See https://code.claude.com/docs/en/plugins. This skill covers the common case: a single skill, zipped, to send.

More from this repository

same repository

address-review

magnusrodseth/dotfiles

Take a GitHub PR's review feedback end to end: fetch unresolved threads from bots and humans, judge each, apply fixes, push, then reply and resolve. Use for "address the review" or "go through the PR feedback".

2026-07-252

autoresearch

magnusrodseth/dotfiles

Autonomous hill-climbing on any measurable problem: qualify the four legs, freeze an eval referee, then loop mutate-evaluate-keep/revert until the stopping condition fires. Works on tests, latency, bundle size, cost.

2026-07-252

capture-inspo

magnusrodseth/dotfiles

Capture full-page screenshots of real sites by aesthetic or vibe as design inspiration, driving your own Chrome via playwriter over Land-book, Lapa Ninja, Awwwards and Mobbin. Use for "capture inspo".

2026-07-252

devto

magnusrodseth/dotfiles

Publish and manage articles on Dev.to (Forem API) from local markdown, using the API key stored in 1Password. Use when the user wants to post, draft, update, publish, unpublish, or list their Dev.to articles, cross-post a blog post or vault note to Dev.to, or mentions dev.to, DEV Community, or the Forem API.

2026-07-252

empirical-research

magnusrodseth/dotfiles

Appraise whether an empirical claim actually holds, against primary sources, with a mandatory refutation pass and tiered sources. Use for "does X actually work", benchmark and vendor claims. Not for API docs (find-docs).

2026-07-252

humanize

magnusrodseth/dotfiles

Detect and rewrite prose that reads as AI-generated: em dashes, AI vocabulary, negative parallelisms, rule-of-three filler, puffery, tone tells. Use for "humanize this", "de-slop", "sounds like ChatGPT", "make this less AI".

2026-07-252

name	share-skill
description	Package an installed Claude Code skill into a shareable zip in a fresh temp folder, then open that folder in Finder. Use when the user says "/share-skill <name>", "share the X skill", "bundle/export/package a skill to send someone", or wants a skill zipped up to hand off.
disable-model-invocation	true
argument-hint	["skill-name"]
allowed-tools	Bash(bash ), Bash(open )

Share Skill

Package one installed skill into a .zip inside a fresh temp folder and open that folder in Finder, ready to hand off.

Steps

Identify the target skill from the user's request. They may write /share-skill the /humanize skill, share humanize, or give a path. Extract the bare skill name (strip a leading /, ignore filler like "the" and "skill"). If no skill is named, ask which one.
Run the packager, passing the name. Use this skill's own base directory (shown when the skill loaded) for the script path:
```
bash "<this-skill-base-dir>/scripts/share-skill.sh" <skill-name>
```
The script resolves the skill (searching ./.claude/skills, $CLAUDE_CONFIG_DIR/skills, then ~/.claude/skills), dereferences symlinks so the archive is self-contained, excludes junk (.DS_Store, .git, *-cache*, node_modules, __pycache__), zips it, drops the zip in a fresh temp folder, and opens that folder in Finder. Pass a full path instead of a name if the skill lives elsewhere.
Report the Zip: and Folder: paths from the script output. Tell the user Finder is open on that folder, and that a recipient installs the skill by unzipping into ~/.claude/skills/ (personal) or a project's .claude/skills/ (project), then starting a new session.

Notes

Output lands in a readable, date-stamped folder: /tmp/shared-skills/<skill-name>_<YYYY-MM-DD_HHMMSS>/<skill-name>.zip.
The zip's top-level folder is the skill name, so it unzips to <skill-name>/SKILL.md.
The Finder step is macOS-only; the zip is still built on other platforms.
For richer distribution (versioning, bundling agents/hooks/MCP, a marketplace), package as a plugin with a .claude-plugin/plugin.json instead. See https://code.claude.com/docs/en/plugins. This skill covers the common case: a single skill, zipped, to send.