promote-skill
- Repo stars 301
- License MIT
- Author updated Live
- Author repo marketplace
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 98 / 100 · audit passed
- Author / version / license
- @aiskillstore · v1.0.0 · MIT
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Env read
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: promote-skill
description: Use when publishing a SKILL.md-style agent skill across uGig, sh1pt, GitHub/gists, and follow-on…
category: ai
runtime: no special runtime
---
# promote-skill output preview
## PART A: Task fit
- Use case: Use when publishing a SKILL.md-style agent skill across uGig, sh1pt, GitHub/gists, and follow-on skill marketplaces such as ClawHub, Goose, LobeHub, Kilo, Skillstore, FreeMyGent, ClawMart, Manus, VS Code Agent Skills, and Moltbook..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Overview / When to Use / Inputs to collect or infer” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Use when publishing a SKILL.md-style agent skill across uGig, sh1pt, GitHub/gists, and follow-on skill marketplaces such as ClawHub, Goose, LobeHub, Kilo, Skillstore, FreeMyGent, ClawMart, Manus, VS Code Agent Skills, and Moltbook.”.
- **02** When the source has headings, the agent prioritizes “Overview / When to Use / Inputs to collect or infer” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands, read environment variables; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands, read environment variables; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source mentions slash commands such as `/skills`, `/tmp`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands, read environment variables.
Start with a small task and check whether the result follows “Overview / When to Use / Inputs to collect or infer”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: promote-skill
description: Use when publishing a SKILL.md-style agent skill across uGig, sh1pt, GitHub/gists, and follow-on…
category: ai
source: aiskillstore/marketplace
---
# promote-skill
## When to use
- Use when publishing a SKILL.md-style agent skill across uGig, sh1pt, GitHub/gists, and follow-on skill marketplaces su…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Overview / When to Use / Inputs to collect or infer” and keep inference separate from source facts.
- read files, write/modify files, run shell commands, read environment variables; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "promote-skill" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Overview / When to Use / Inputs to collect or infer
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands, read environment variables | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Promote Skill
Overview
Use this skill to turn a local SKILL.md into a public marketplace listing and promotion checklist. The workflow is agent-friendly:
- Validate and sanitize the skill source.
- Create a public source URL, preferably a GitHub repo or public gist raw URL.
- Publish to uGig first because uGig imports the raw
SKILL.md, scans it, and exposes a "Publish Everywhere" checklist. - Use sh1pt as the cross-marketplace promotion manifest/command generator.
- Work through other marketplaces by CLI, PR, account submission, or manual upload depending on the platform.
Never include credentials, cookies, private env values, or personal secrets in a public skill file or marketplace listing.
When to Use
Use this when the user says:
- "publish this skill"
- "promote this skill"
- "put it on uGig / ClawHub / LobeHub / Goose / Kilo"
- "make a public SKILL.md"
- "publish everywhere"
- "create a promote-skill workflow"
Do not use this for job applications themselves; use job-board specific skills for that.
Inputs to collect or infer
Required:
- Local
SKILL.mdpath or directory containing it. - Public-safe title, slug, tagline, description, category, tags.
- Price in sats;
0means free.
Optional:
- Existing public raw
SKILL.mdURL. - GitHub repo/gist preference.
- uGig credentials or already-authenticated browser profile.
- Marketplace-specific credentials/API keys for platforms that need them.
Safety checklist before publishing
Run a secrets scan before any public upload:
grep -RInE 'password|passwd|secret|token|api[_-]?key|BEGIN .*PRIVATE|private[_-]?key|cookie|credential' SKILL.md . 2>/dev/null || trueThen manually inspect hits. Mentions of environment variable names are fine; real values are not.
For paid listings, remember: marketplaces that import from a public raw URL may expose the artifact publicly. If the artifact is not intended to be free, verify access-gating from an anonymous browser before claiming it is paywalled.
uGig workflow
Preferred CLI path once ugig supports skills new:
ugig skills new \
--title "My Skill" \
--description "Public credential-free SKILL.md for ..." \
--tagline "Short marketplace tagline" \
--category Automation \
--price 0 \
--tags "skills,automation,agents" \
--source-url "https://raw-or-gist-url/SKILL.md"ugig skills create is an alias for ugig skills new. If the installed CLI is older or does not support the needed fields, use the uGig browser form:
https://ugig.net/dashboard/skills/newKnown form fields:
- Skill File URL: raw/direct public
SKILL.mdURL. - Title.
- Tagline.
- Description.
- Price:
0for free. - Category.
- Tags: keep combined tags short; supported-agent chips may count toward the maximum.
- ClawHub URL: fill after publishing to ClawHub.
Verification:
- Listing URL is
/skills/<slug>. - Page says
Freeor the expected price. - Security scan says
Clean. - Medium warning for environment variable access is expected if the skill documents env vars.
- Source URL is correct and contains no secrets.
sh1pt workflow
The sh1pt CLI should provide top-level skill promotion commands:
sh1pt skills new --skill-file ./SKILL.md --source-url "https://raw-or-gist-url/SKILL.md" --price 0
sh1pt skills publish --all --dry-run
sh1pt skills publish --marketplace ugig clawhub goose
sh1pt skills marketplacesExpected behavior:
sh1pt skills newcreatessh1pt.skill.jsonby reading frontmatter from the localSKILL.mdand filling title/slug/description/tags/price/source URL.sh1pt skills publish --all --dry-runprints exact commands or manual steps for every known marketplace.- Non-dry runs should not blindly execute unknown third-party CLIs until credentials/API setup is verified; print commands and mark manual/action-required states.
Implementation locations vary by project. In a typical sh1pt-style monorepo, add the command module under the CLI package and register it from the CLI entrypoint.
Marketplace matrix
| Marketplace | Method | Publish pattern |
|---|---|---|
| uGig | CLI/API or browser | ugig skills new ... --source-url <raw SKILL.md> |
| ClawHub | CLI | clawhub publish . --slug <slug> --version 1.0.0 |
| skills.sh | Auto-indexed | Push public GitHub repo containing SKILL.md |
| LobeHub Skills | Submit | Use site submission; install command shown as npx @lobehub/cli skill install <slug> |
| Goose Skills | PR / install URL | goose skill add <raw SKILL.md URL>; submit PR if directory requires it |
| Kilo Marketplace | PR | Fork + PR with valid SKILL.md; install command kilo skill install <slug> |
| Skillstore | GitHub repo | Submit repo/raw URL for security analysis |
| FreeMyGent | Upload | Upload skill.md, set price, connect wallet |
| ClawMart | API | clawmart publish . --name <slug> |
| Manus Agent Skills | Account | Free account required; submit through account UI |
| VS Code Agent Skills | GitHub | Publish via extension-indexed GitHub repo/PR |
| Moltbook / NormieClaw | Submit | Submit, set price, pass quality check |
Public source choices
Quick gist:
gh gist create ./SKILL.md --public --desc "<skill title>"
gh api gists/<gist-id> --jq '.files["SKILL.md"].raw_url'Better for auto-indexers:
mkdir -p /tmp/<slug>
cp ./SKILL.md /tmp/<slug>/SKILL.md
cd /tmp/<slug>
git init
git add SKILL.md
git commit -m "Add <slug> skill"
gh repo create <owner>/<slug>-skill --public --source=. --pushPrefer a repo over a gist when targeting skills.sh, VS Code Agent Skills, Goose/Kilo PRs, or marketplaces that require repository metadata.
Common pitfalls
- Using a human gist page instead of the raw URL. Use
gist.githubusercontent.com/.../raw/.../SKILL.mdfor import. - Publishing credentials in examples. Use placeholder env var names only.
- Too many tags on uGig. Keep tags under 10 and leave supported-agent chips blank if validation complains.
- Assuming "Publish Everywhere" means automatic publication. It is a per-marketplace checklist; many require account registration, API keys, or PRs.
- Calling unknown CLIs live without checking auth. Prefer dry-run until
command -v, login status, and target repo/account are verified.
Final report format
Published:
- uGig: https://ugig.net/skills/<slug>
- GitHub source: https://github.com/<owner>/<repo>
- Raw SKILL.md: https://...
Ready/manual next:
- ClawHub: <command or login needed>
- Goose: <PR/command>
- LobeHub: <submission URL>
Security:
- Secret scan: clean / reviewed
- uGig scan: Clean; env-var warning expected
Decide Fit First
Design Intent
How To Use It
Boundaries And Review