How do I install the Share Skill skill?

Run npx skillmds@latest add luokai0/share-skill in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Share Skill safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Share Skill?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Share Skill free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Share Skill?

luokai0 (@luokai0) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Share Skill by luokai0 — Agent Skill

Name: Share Skill
Rating: 4.2 (5 reviews)
Author: luokai0

Share Skill

Safely prepare and guide skills for contribution to the Zo Skills Registry. Reviews code for secrets, validates SKILL.md format, checks for suspicious patterns, and provides clear next steps for community or external skill submissions.

luokai0 Updated Sep 8, 2026 10 repo stars

File contents

Share Skill to Registry

This skill helps you safely contribute a skill to the Zo Skills Registry (zocomputer/skills).

Usage

# Review a skill for safe sharing
bun /home/workspace/Skills/share-skill/scripts/validate.ts <skill-path>

# Example:
bun /home/workspace/Skills/share-skill/scripts/validate.ts /home/workspace/Skills/my-skill

What This Checks

Safety Scan (BLOCKING if found)

Hardcoded secrets (API keys, tokens, passwords)
Suspicious code patterns (eval, exec, shell injection risks)
Obfuscated or minified code
Private files (.env, local caches, personal data)

Structure Validation

SKILL.md with required frontmatter (name, description, compatibility)
Valid skill name (lowercase, hyphens, matches folder name)
Scripts are documented and executable
Required folders follow conventions

Contribution Workflows

Your Original Skill

Fork zocomputer/skills
Copy your skill folder to Community/<your-skill>/
Run the validator: bun validate (from the repo root)
Open a PR with this template:

## Skill Submission: <skill-name>

**Author:** @<your-github-username>
**Category:** <automation|integration|utility|media|other>

### What it does
<2-3 sentence description>

### Requirements
- <any external services needed>
- <any API keys required>

### Usage Example
```bash
bun /home/workspace/Skills/<skill-name>/scripts/<script>.ts <args>


### Someone Else's Skill (External)

1. Fork [zocomputer/skills](https://github.com/zocomputer/skills)
2. Add entry to `external.yml`:

```yaml
- name: <skill-name>
  source: <git-url-or-path>
  author: <original-author>
  license: <license-type>

Run: bun run sync-external
Open PR with attribution notes

Important Notes

Never include secrets in skill code—read from environment variables
Never submit PRs on your behalf automatically
Skills must be self-contained and documented
Community skills go in Community/; external skills use external.yml

---name: share-skilldescription: Safely prepare and guide skills for contribution to the Zo Skills Registry. Reviews code for secrets, validates SKILL.md format, checks for suspicious patterns, and provides clear next steps for community or external skill submissions.---# Share Skill to RegistryThis skill helps you safely contribute a skill to the Zo Skills Registry (zocomputer/skills).## Usage```bash# Review a skill for safe sharingbun /home/workspace/Skills/share-skill/scripts/validate.ts <skill-path># Example:bun /home/workspace/Skills/share-skill/scripts/validate.ts /home/workspace/Skills/my-skill```## What This Checks### Safety Scan (BLOCKING if found)- Hardcoded secrets (API keys, tokens, passwords)- Suspicious code patterns (`eval`, `exec`, shell injection risks)- Obfuscated or minified code- Private files (`.env`, local caches, personal data)### Structure Validation- SKILL.md with required frontmatter (`name`, `description`, `compatibility`)- Valid skill name (lowercase, hyphens, matches folder name)- Scripts are documented and executable- Required folders follow conventions## Contribution Workflows### Your Original Skill1. Fork [zocomputer/skills](https://github.com/zocomputer/skills)2. Copy your skill folder to `Community/<your-skill>/`3. Run the validator: `bun validate` (from the repo root)4. Open a PR with this template:```markdown## Skill Submission: <skill-name>**Author:** @<your-github-username>**Category:** <automation|integration|utility|media|other>### What it does<2-3 sentence description>### Requirements- <any external services needed>- <any API keys required>### Usage Example```bashbun /home/workspace/Skills/<skill-name>/scripts/<script>.ts <args>``````### Someone Else's Skill (External)1. Fork [zocomputer/skills](https://github.com/zocomputer/skills)2. Add entry to `external.yml`:```yaml- name: <skill-name> source: <git-url-or-path> author: <original-author> license: <license-type>```3. Run: `bun run sync-external`4. Open PR with attribution notes## Important Notes- **Never** include secrets in skill code—read from environment variables- **Never** submit PRs on your behalf automatically- Skills must be self-contained and documented- Community skills go in `Community/`; external skills use `external.yml`

Frequently asked questions