publish
Skill25 starsChanged 8 months agoMITView on GitHub
Publish a packaged product to myclaude.sh via the CLI. Shows summary, requires confirmation, runs myclaude validate + myclaude publish. Use when the creator says "publish", "ship it", "go live", or after /package.
- Installs packages
67 other projects use a version of this.
Adopted by
Most recently taken up by
- filecoin-project/filecoin-skillstheir own version, first seen Nov 16, 2026
- noelceta/content-enginetheir own version, first seen Nov 16, 2026
- vincentventalon/claude-code-video-editing-skilltheir own version, first seen Nov 15, 2026
- vincentventalon/my-claude-skillstheir own version, first seen Nov 15, 2026
- foster-systems/shelftheir own version, first seen Nov 15, 2026
- carlos2219/web-kittheir own version, first seen Nov 15, 2026
Used with
Projects with it also use clips, outliers and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MelvynxSkillclips
Turns one long video (YouTube link, podcast, webinar, livestream, or a local file) into finished vertical shorts. Use when the user says long to short, repurpose, long video to shorts, clips from my video, podcast clips, cut my YouTube video into shorts, or gives a long video link. Finds clips that stand alone (one idea, 20 to 60 seconds), scores them, cuts them and edits each one with short-editing (split-screen paper look, captions, cuts, hook, boards, 1080x1920), and writes new scripts in the studio-script format from the ideas too spread out to clip. Reads YouTube captions and chapters with yt-dlp, or transcribes a local file with the short-editing engine (whisper.cpp, free, offline).
Also in 3 projects that use this
MelvynxSkilloutliers
Finds the outlier reels of Instagram accounts or videos of TikTok accounts (3x their own account's median views or more) through Treg and turns the 5 best into remake scripts in the creator's voice. Two modes - /outliers @handle digs one account; /outliers with no account starts from the creator's own reels, uses and grows a competitor watchlist (video-agent/competitors.json, 70 % main language / 30 % second language when they watch two), ranks every account's outliers against its own median and writes 5 scripts into video-agent/scripts/. Use when the user says outliers, find outliers, what blew up for my competitors, what works in my niche, find me videos to remake, ideas from @someone, what blew up on TikTok.
Also in 3 projects that use this
khadinakbarlabsSkillkeywords
Research and prioritize SEO keywords, search intent, topic clusters, competitor keyword gaps and keyword-to-page mappings. Use when asked what to rank for, keyword opportunities, long-tail keywords, a content calendar, or a keyword plan. Uses owned Apify keyword/SERP Actors with approved budgets, or supplied exports offline. Does not invent volume or organic difficulty.
Also in 3 projects that use this
justinseger015-ctrlSkilledit
Edit a video using the video-editing orchestrator. Detects format, routes to correct editing skill, and executes the full process. Use when user says: /edit, edit video, edit clip, edit this, make it polished, finish editing, polish this video.
Also in 3 projects that use this
LangChainSkillrender
Turn an SVG design into a PNG and look at it. Use after you write or change a design, but only if execute is one of your tools.
Also in 3 projects that use this
JaimeGBASkillingest
Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base
Also in 5 projects that use this
Other versions67 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 67
- code-yeongyu/oh-my-openagent★ 71ksame name
- code-yeongyu/oh-my-opencode★ 71ksame name
- garrytan/gbrain★ 33ksame name
- TencentCloud/Octop★ 12ksame name
- harbor-framework/harbor★ 7.1ksame name
- laude-institute/harbor★ 7.1ksame name
- Q00/ouroboros★ 6.4ksame name
- paean-ai/deeptide★ 1.1ksame name
- ZimoLiao/scholaraio★ 589same name
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool★ 432same name
57 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
28 rules. 0 are common, 6 are distinctive, and 22 are very specific to this project.
0
Common
Most of the 56 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
22
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
When to use: After /package has staged .publish/ directory.
- Distinctive: line 20
When NOT to use: If product hasn't been packaged yet (run /package first).
- Very specific: line 28
Read .meta.yaml → verify state is "packaged"
- Very specific: line 29
Verify .publish/ exists with vault.yaml
- Very specific: line 30
Check CLI: which myclaude — if not found, show install instructions
- Very specific: line 31
Check CLI auth: run myclaude whoami — if "not logged in", show: "Not authenticated.
- Very specific: line 32
Read creator.yaml → load author metadata.
- Distinctive: line 43
Auth detection: use contract's auth flow pattern (whoami → check exit code + "not logged" in output)
- Very specific: line 72
If type is claude-md, append this note to the summary display before asking for confirmation:
- Very specific: line 82
Read .meta.yaml → history.version AND check if this slug+version combination was already published:
- Very specific: line 84
If state.phase == "published" AND history.version matches the current version in .publish/vault.yaml:
- Very specific: line 86
If state.phase != "published" (first publish): proceed — no version check needed.
- Distinctive: line 90
Wait for explicit "yes" from creator.
- Very specific: line 121
After the .meta.yaml state update succeeds, write up to two events to creator-memory.yaml: first_publish and first_celebration.
- Very specific: line 135
Read creator-memory.yaml. If absent or malformed, skip silently (Phase 5b of /onboard owns file creation).
- Distinctive: line 139
If none exists, append:
- Very specific: line 155
If pre_publish_count == 0 (this publish is the Creator's first ever), proceed to step 3.
- Very specific: line 169
Validation and rollback: After each append, run python scripts/creator-memory-validate.py.
- Very specific: line 204
After successful publish, generate a distribution plan informed by the Intelligence Layer.
- Very specific: line 207
Read .meta.yaml → intelligence fields.
- Very specific: line 210
If price == 0 AND value_score >= 5:
- Very specific: line 224
Read config.yaml → intelligence.distribution.channels_by_type.{type}.
- Very specific: line 253
If portfolio_role is "anchor" (first in domain): "This is your anchor product in {domain}.
- Very specific: line 254
If portfolio_role is "complement" or "extension": "Cross-promote with your existing {domain} products: {list existing slugs}.
- Distinctive: line 258
After successful publish, run competitive scan silently:
- Very specific: line 280
After publish, remind: "Your marketplace XP increases with each publish.
- Distinctive: line 289
Every line is immediately copy-pasteable
- Very specific: line 295
If myclaude CLI is not installed:
“Common” is measured: kept by at least 6 in 10 of the 56 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Publisher
Publish a packaged product to the MyClaude marketplace via CLI delegation.
When to use: After /package has staged .publish/ directory.
When NOT to use: If product hasn't been packaged yet (run /package first).
Activation Protocol
- Shared preamble: Load
references/quality/activation-preamble.md— context assembly, persona adaptation, deterministic routing rules. - Identify product:
$ARGUMENTSas slug →workspace/{slug}/ - Read
.meta.yaml→ verify state is "packaged" - Verify
.publish/exists with vault.yaml - Check CLI:
which myclaude— if not found, show install instructions - Check CLI auth: run
myclaude whoami— if "not logged in", show: "Not authenticated. Runmyclaude loginfirst." and stop. - Read
creator.yaml→ load author metadata. If missing — "Creator profile not found. Run/onboardfirst." and stop. 6b. Load proactives: Loadreferences/engine-proactive.md— wire #1 (pipeline guidance: after publish, suggest /status to track installs), #14 (feedback loop: after publish, suggest checking install data next session), #18 (WOW moment for first publish). - Load voice identity: Load
references/quality/engine-voice-core.md. Load the fullreferences/quality/engine-voice.mdonly when composing the publish celebration (Step 6) — that is a peak moment. Use publish celebration format: "Published to myclaude.sh — live now." + install command + distribution vector note. Brief, proud, specific. 7b. Exemplar load: Loadreferences/quality/exemplar-outputs.mdsections E8 and E9 only — the first-publish celebration and nth-publish compact. Your celebration MUST carry the same Frame + emotion calibration: full ceremony for first/significant publishes, compact ✦ line for expert nth publishes. Adapt to creator journey position. - CLI contract: Load
references/cli-contract.mdfor unified error handling. This skill has mixed severity — the most critical CLI surface in the pipeline. Severity map:- Blocking:
validate --json(Step 3) — abort publish if validation fails or CLI unavailable - Blocking:
publish(Step 4) — cannot proceed without CLI. Show manual alternative:myclaude.sh/publish - Blocking:
whoami(Step 5 pre-flight) — must be authenticated before publish - Silent-skip:
search(Step 8 competitive context) — skip without warning on failure - Silent-skip:
profile pull(Step 9 XP reminder) — skip without warning on failure - All queries except publish: append
2>/dev/null, 15s timeout - Auth detection: use contract's auth flow pattern (whoami → check exit code + "not logged" in output)
- Blocking:
Core Instructions
PUBLISH FLOW
Step 1 — Summary
Display what will be published:
Ready to publish:
Name: {displayName}
Slug: {slug}
Type: {type}
Version: {version}
Price: {price == 0 ? "Free" : "$" + price}
License: {license}
MCS: {level} ({score}%)
Files: {N} in .publish/
Publish to myclaude.sh? (yes/no)Step 1b — Type-Specific Constraints
If type is claude-md, append this note to the summary display before asking for confirmation:
Note: Rules files (.claude/rules/) cannot be auto-installed via the plugin system.
Buyers must manually copy the rules file to ~/.claude/rules/ or .claude/rules/ in
their project. Include this instruction in your README.md.Step 1c — Version Bump Guard
Read .meta.yaml → history.version AND check if this slug+version combination was already published:
- Glob
workspace/{slug}/.meta.yaml→ readstate.published_atandhistory.version - If
state.phase == "published"ANDhistory.versionmatches the current version in.publish/vault.yaml:- BLOCKING: "Version {version} is already published. Bump the version in
.meta.yaml → history.version(e.g., 1.0.0 → 1.0.1) before re-publishing. This prevents 71+ users from receiving a silent no-change update."
- BLOCKING: "Version {version} is already published. Bump the version in
- If
state.phase != "published"(first publish): proceed — no version check needed.
Step 2 — Confirmation
Wait for explicit "yes" from creator. Do NOT proceed without confirmation.
Step 3 — CLI Pre-flight
cd workspace/{slug}/.publish && myclaude validate --json 2>/dev/nullParse JSON result. If exit code != 0 or JSON parse fails, report: "CLI validation failed or unavailable. Verify manually or run /validate first." and abort.
Step 4 — Publish
cd workspace/{slug}/.publish && myclaude publishReport CLI output verbatim.
Step 5 — Update State
On success:
# .meta.yaml updates
state:
phase: "published"
published_at: "{ISO timestamp}"
version: "{version}"Step 5b — Seed creator-memory publish milestones (silent, idempotent)
After the .meta.yaml state update succeeds, write up to two events to
creator-memory.yaml: first_publish and first_celebration. Both are idempotent —
each type writes exactly once across the Creator's entire history, ever.
Why two events? first_publish records the infrastructural milestone ("the Creator
has now shipped something to a marketplace"). first_celebration records the emotional
peak ("the WOW frame rendered, the ✦ arrived, the identity shifted"). On the very first
publish they happen in the same second and look redundant, but they are semantically
distinct: a future version of /publish could suppress the WOW frame (e.g., --silent or
a re-publish scenario) without suppressing the milestone. Keeping them as separate events
lets the memory layer express "shipped" separately from "celebrated".
Procedure for first_publish:
- Read
creator-memory.yaml. If absent or malformed, skip silently (Phase 5b of /onboard owns file creation). - Scan
events[]for any entry withtype == "first_publish". If one exists, skip this event (idempotent). - If none exists, append:
- date: "{ISO-8601 now UTC}" type: first_publish slug: "{slug}" note: "First publish — {displayName} live at myclaude.sh/p/{slug}"
Procedure for first_celebration:
- Compute
pre_publish_count: count.meta.yamlfiles inworkspace/*/wherestate.phase == "published"EXCLUDING the product being published in this invocation. Since Step 5 just wrotephase: "published", a Glob that captures the in-flight state would return 1, not 0 — subtract 1 to get the pre-publish count. Easier approach: read the in-memory value of.meta.yaml.state.phasebefore the Step 5 write, compute the count at that moment, and carry it forward. - If
pre_publish_count == 0(this publish is the Creator's first ever), proceed to step 3. Otherwise, skip the celebration event entirely — it only fires on the first publish. Thefirst_publishevent already fired above if applicable. - Scan
creator-memory.yaml events[]for any entry withtype == "first_celebration". Idempotent guard — if one exists, skip (this should be impossible given the count check above, but belt-and-suspenders). - If none exists, append:
- date: "{ISO-8601 now UTC}" type: first_celebration slug: "{slug}" note: "First celebration — WOW frame rendered for {slug}"
Validation and rollback. After each append, run python scripts/creator-memory-validate.py.
On validation failure, roll back the append and surface an Engine-fault voice line at
the end of Step 6's output, never blocking the publish:
"(Memory layer — failed to seed first_publish/first_celebration event. The publish itself is safe; only the memory echo is missing.)"
Voice register. Silent infrastructure. Step 5b does not render any line to the
Creator — the celebration voice belongs entirely to Step 6. The payoff arrives on future
Ritual of Return invocations, where /status Layer 2 can echo the memory grounded in
the real date and slug.
Step 6 — Report
UX Stack (load before rendering report):
references/ux-experience-system.md§1 Context Assembly + §2.3 Moment Awareness (publish = peak emotion, scaled by journey) + §4.1 Celebration Triggers + §5.1 Creator Journey Narrativereferences/ux-vocabulary.md— translate all termsreferences/quality/engine-voice.md— Brand DNA + signature patterns for publish
Cognitive rendering: /publish is the HIGHEST EMOTION moment in the pipeline. But emotion scales with journey position:
- First publish ever: Full celebration. Identity moment. "Your first product is live. You're a creator now." Show the full distribution plan.
- 2nd-5th publish: Warm but briefer. "Another one live. Portfolio growing." Focus on portfolio composition.
- 6th+ publish: Peer observation. Surface only the non-obvious: market position, competitive context, portfolio gap that just closed.
- Always: The install command (
myclaude install {slug}) is the most satisfying line — it makes the product REAL. Feature it prominently. - Brand moment: This is where the creator's identity fuses with the myClaude ecosystem. Their product, our platform, shared universe.
Published! {displayName} v{version} is live on myclaude.sh
URL: https://myclaude.sh/p/{slug}
Install: myclaude install {slug}
MCS: {mcs_level} ({score}%)
Platforms: MyClaude + Anthropic Plugin + 33 Agent Skills platformsStep 7 — Intelligent Distribution (Intelligence Layer integration)
After successful publish, generate a distribution plan informed by the Intelligence Layer. Reference: config.yaml → intelligence.distribution + references/intelligence-layer.md.
7a. Load intelligence context:
Read .meta.yaml → intelligence fields. Extract: value_score, pricing_strategy, distribution_channels, market_position, portfolio_role.
7b. Free-vs-paid reflection:
If price == 0 AND value_score >= 5:
Pricing note: Your product scores {value_score}/12 — you chose free distribution.
{If first in domain: "Smart move. Free builds authority in a new domain."}
{If not first: "Consider a paid tier for your next product in {domain} — you've built presence."}If price > 0:
Premium positioning: ${price} for {pricing_strategy}-tier product.
Ensure your README clearly communicates the value proposition.
Users who need {domain} expertise will pay for verified quality (MCS-{level}).7c. Intelligent channel ranking:
Read config.yaml → intelligence.distribution.channels_by_type.{type}. Display channels ranked by impact for this product type, with specific actionable instructions:
Distribution plan for {slug} ({type}):
{For each channel in channels_by_type[type], ranked:}
{rank}. {channel_name}
{channel-specific copy-paste text — see below}Channel-specific copy (all directly copy-pasteable):
| Channel | Copy Template |
| myclaude | "Live at myclaude.sh/p/{slug}" (already done) |
| awesome-claude-code | PR title: "Add {displayName}" → github.com/hesreallyhim/awesome-claude-code |
| awesome-claude-skills | PR title: "Add {displayName}" → github.com/travisvn/awesome-claude-skills |
| "I just published {displayName} — {description}. {Free/price} on myclaude.sh/p/{slug}" | |
| "Just shipped {displayName} for Claude Code. {one-line-description} myclaude.sh/p/{slug} #ClaudeCode" | |
| domain-community | "Identify the top forum/subreddit for {domain}. Post: '{displayName} — {description}'" |
| "For {domain} professionals: {displayName} brings {capability} to Claude Code. myclaude.sh/p/{slug}" | |
| blog-post | "Write a walkthrough: problem → how {slug} solves it → architecture → install" |
| discord | "Share in Claude Code community Discord with usage example" |
| youtube | "Record 3-min walkthrough showing before/after with {slug}" |
| landing-page | "Build a landing page for premium bundles — /premium-lp can help" |
| product-hunt | "Launch on Product Hunt for comprehensive bundles — coordinate with community" |
| newsletter | "Pitch to domain-specific newsletters covering {domain}" |
7d. Portfolio distribution intelligence:
If portfolio_role is "anchor" (first in domain): "This is your anchor product in {domain}. Building visibility here creates a funnel for future {domain} products."
If portfolio_role is "complement" or "extension": "Cross-promote with your existing {domain} products: {list existing slugs}. Users who install one likely need the others."
Step 8 — Competitive Context (post-publish intelligence)
After successful publish, run competitive scan silently:
myclaude search --category {type_category} --sort downloads --limit 5 --json 2>/dev/nullIf successful, display:
Competitive landscape ({type}):
#1. {name} by @{author} — {downloads} downloads
#2. {name} by @{author} — {downloads} downloads
#3. {name} by @{author} — {downloads} downloads
Your product: {slug} (newly published)
Tip: differentiate by {suggestion based on top products' descriptions}This gives creators immediate market awareness — they see who they're competing with the moment they ship. Skip silently if CLI unavailable or search returns no results.
Step 9 — Profile XP Update
After publish, remind: "Your marketplace XP increases with each publish. Run myclaude profile pull to see your updated level."
Rules:
- {displayName} = from vault.yaml
display_nameor humanizedname - {description} = from vault.yaml
description(first sentence only if >100 chars) - {slug} = from vault.yaml
name - {type} = from vault.yaml
type - {price} = "Free" if 0, else "$X" from vault.yaml
price - This prompt is INFORMATIONAL — does not block the flow or require interaction
- Every line is immediately copy-pasteable
CLI Not Found
If myclaude CLI is not installed:
MyClaude CLI not found. Install it:
npm install -g @myclaude-cli/cli
Then run /publish again.
Alternative: upload manually at myclaude.sh/publishAnti-Patterns
- Publishing without confirmation — Always require explicit "yes".
- Publishing unpackaged product — Check .meta.yaml state first.
- Swallowing CLI errors — Report all CLI output, don't hide failures.
- Re-publishing without version bump — If already published, require version increment.
- Publishing with secrets — CLI pre-flight catches this, but mention it if found.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

