Our review
Automates publishing a marketplace skill to the documentation site: it generates the EN and ZH detail pages, updates the marketplace index and the docs.json navigation, then commits, pushes, and verifies the skill exists on main.
Strengths
- Handles the whole publication chain in one command, from reading the SKILL.md to pushing the rendered pages.
- Keeps the English and Chinese detail pages and index entries in sync.
- Edits docs.json for both navigation groups, so skills are less likely to be left unreferenced.
- Uses an existing page (trellis-meta.mdx) as the reference template, which enforces a consistent format.
Limitations
- Tightly coupled to one repository layout (marketplace/skills/, docs-site/, Mintlify docs.json) and hard to reuse elsewhere.
- The Chinese translation is generated without human review, so quality depends on the model.
- The cherry-pick to main assumes a clean working tree, can hit conflicts, and no site build is verified afterwards.
Use it when a marketplace skill needs to be released with its English and Chinese documentation pages and navigation entries.
Avoid it when the docs site does not follow this Mintlify/docs.json structure, or when the content being documented is not a marketplace skill.
Security analysis
CautionThe skill automates documentation publishing with git operations including commit, push, branch checkout, and cherry-pick. These are legitimate development workflow actions but carry meaningful risk of unintended remote changes or branch state disruption, warranting caution.
- •Executes git push to remote repositories without explicit confirmation or safeguards.
- •Performs branch manipulation (checkout main, cherry-pick, push origin main) that can alter repository state and remote history.
- •Uses shell commands despite declaring no allowed tools, which may bypass agent tool restrictions.
Examples
Publish the skill cc-codex-spec-bootstrap to the docs site.Run the publish-skill-to-docs workflow — list the skills under marketplace/skills/ and let me pick one.Sync marketplace/skills/my-new-skill to the docs site (EN + ZH pages, index, docs.json) and make sure the skill itself is on main.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
API Documentation Generator
Documentation
Automatically generates OpenAPI/Swagger API documentation.
Technical Writer
Documentation
Writes clear technical documentation following top style guides.
Review Existing Content
Documentation
Reviews documentation pages selected by the daily content-review workflow, applying high-confidence fixes and opening auditable pull requests. For the review-existing-content pipeline.