Automated summary
Syncs a marketplace skill to the documentation site by creating detail pages (EN/ZH), updating the index, and modifying the docs.json navigation file.
Strengths
- Fully automates the documentation publishing pipeline.
- Handles Chinese localization automatically.
- Manages git branch operations and cherry-picking if required.
Limitations
- Requires the docs-site repository to be cloned and configured locally.
- Assumes the documentation page format already exists.
- Does not validate the skill content or metadata.
When you have developed or updated a marketplace skill and need to publish its official documentation to the site.
For minor documentation edits unrelated to a specific marketplace skill.
Security analysis
CautionThe skill performs legitimate documentation site updates using bash and git commands. No destructive, exfiltrating, or obfuscated actions are present. However, because it uses powerful tools (bash, git) that could modify files and push code, it warrants caution.
- •Uses bash to execute file operations and git commands
Examples
Publish the 'cc-codex-spec-bootstrap' skill to the docs site.List available marketplace skills for documentation publishing.Publish Skill to Docs Site
Sync a marketplace skill to the documentation site. Creates skill detail pages (EN/ZH), updates the marketplace index, and updates docs.json navigation.
Arguments
$ARGUMENTS— Skill directory name undermarketplace/skills/(e.g.,cc-codex-spec-bootstrap). If omitted, list available skills and ask.
Steps
Step 1: Identify the Skill
# If no argument, list available skills
ls marketplace/skills/
Read the skill's SKILL.md to extract:
- name (from frontmatter)
- description (from frontmatter)
- What the skill does (from body)
- Prerequisites / tools needed
- What files are included
cat marketplace/skills/<skill-name>/SKILL.md
Step 2: Check Existing Docs
Verify the skill doesn't already have docs pages:
ls docs-site/skills-market/<skill-name>.mdx 2>/dev/null
If pages already exist, ask user if they want to update them.
Step 3: Create EN Detail Page
Create docs-site/skills-market/<skill-name>.mdx.
Follow the format of existing skill pages (see docs-site/skills-market/trellis-meta.mdx as reference):
---
title: '<skill-name>'
description: '<one-line description>'
---
<what the skill does - 1-2 paragraphs>
## Install
```bash
npx skills add mindfold-ai/Trellis/marketplace --skill <skill-name>
Or install all available skills:
npx skills add mindfold-ai/Trellis/marketplace
Options:
| Flag | Description |
| --- | --- |
| -g | Install globally (~/.claude/skills/) |
| -a claude-code | Target a specific agent |
| -y | Non-interactive mode |
Verify Installation
...
Usage
<example prompts>What's Included
<table of directories/files> ```Step 4: Create ZH Detail Page
Create docs-site/zh/skills-market/<skill-name>.mdx with Chinese translation of the EN page.
Step 5: Update Index Pages
Add the skill to the Official Skills table in both:
docs-site/skills-market/index.mdxdocs-site/zh/skills-market/index.mdx
Step 6: Update docs.json
Add the new page to both EN and ZH Skills navigation groups in docs-site/docs.json:
- EN:
"skills-market/<skill-name>"in the Skills pages array - ZH:
"zh/skills-market/<skill-name>"in the ZH Skills pages array
Step 7: Commit and Push Docs
cd docs-site
git add skills-market/<skill-name>.mdx zh/skills-market/<skill-name>.mdx \
skills-market/index.mdx zh/skills-market/index.mdx docs.json
git commit -m "docs: add <skill-name> skill to marketplace"
git push
Step 8: Ensure Skill on Main Branch
If the marketplace skill isn't on main yet (e.g., committed on a feature branch):
# Check if skill exists on main
git log main --oneline -- marketplace/skills/<skill-name>/ | head -1
If not on main, cherry-pick the commit:
# Find the commit that added the skill
git log --oneline -- marketplace/skills/<skill-name>/ | head -1
# Cherry-pick to main
git stash
git checkout main && git pull
git cherry-pick <commit-hash>
git push origin main
git checkout - && git stash pop
Step 9: Confirm
Report:
- Docs-site pages created (EN + ZH)
- Index pages updated
- docs.json updated
- Docs-site pushed
- Marketplace skill available on main
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/publish-skill-to-docs-site-mrwake6b/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/publish-skill-to-docs-site-mrwake6b' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/publish-skill-to-docs-site-mrwake6b/download' --output '.skill-downloads/publish-skill-to-docs-site-mrwake6b/SKILL.md.part' && mv '.skill-downloads/publish-skill-to-docs-site-mrwake6b/SKILL.md.part' '.skill-downloads/publish-skill-to-docs-site-mrwake6b/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/publish-skill-to-docs-site-mrwake6b/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.