skill-publisher-cli
Validate, version, and package SKILL.md folders for multi-registry marketplace publishing. Use when: Validate SKILL.md files against marketplace standards before shipping; Automate SemVer versioning and CHANGELOG updates for AI skills; Generate clean distribution ZIPs without git or cache junk files.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- skill-publisher-cli
- license
- MIT
- metadata
- { "author": "Nex AI", "version": "1.2", "agensi-slug": "skill-publisher-cli" }
- description
- Validate, version, and package SKILL.md folders for multi-registry marketplace publishing. Use when: Validate SKILL.md files against marketplace standards before shipping; Automate SemVer versioning and CHANGELOG updates for AI skills; Generate clean distribution ZIPs without git or cache junk files.
- compatibility
- Compatible with SKILL.md-compatible agents
02 资源文件 1
- 参考文档skill-report.json12.4 KB
03 SKILL.md 正文
Skill Publisher CLI
Free skill by Nex AI. This file is the public guide from Agensi. Scripts, extension source, and templates from the original package are not in this folder.
Professional Skill Deployment Pipeline
The Skill Publisher CLI transforms your raw AI skill folders into production-ready marketplace packages. It solves the fragmentation problem of publishing to multiple registries like skills.sh, Agensi, and Gumroad by automating validation, versioning, and packaging into a single repeatable workflow.
What it does
This skill orchestrates a suite of Python-based tools to ensure your SKILL.md files meet strict marketplace standards. At its core, it handles:
- Validation: Checks YAML frontmatter, naming conventions, and broken internal links to prevent registry rejections.
- Versioning: Manages SemVer bumps and automatically maintains a CHANGELOG.md file.
- Packaging: Generates clean, junk-free ZIP files and GitHub-ready directory structures.
- Metadata Generation: Renders READMEs and platform-specific metadata from your source files.
Supported Workflows
Built for developers who need to ship fast, it supports standard registries using a 'Dry-run first' philosophy. It ensures that no files are written or bumped until you explicitly approve the changes. The tool outputs a standardized dist/ folder containing everything needed for manual or automated uploads.
Why use this?
Instead of manually zipping files or guessing why a registry rejected your skill, this CLI provides a local "Pre-flight Check." It guarantees that every asset—from the ZIP contents to the metadata description—is perfectly formatted for the AI skill ecosystem.
Built by Nex AI. More skills and info at nex-ai.be and slopsome.com.
When to use
- Validate SKILL.md files against marketplace standards before shipping
- Automate SemVer versioning and CHANGELOG updates for AI skills
- Generate clean distribution ZIPs without git or cache junk files
- Create GitHub-ready folder structures for skills.sh compatibility
- Extract platform-specific metadata and tags from skill descriptions
Known limitations
- Requires Python 3.x for helper scripts
- Local validation only: does not auto-upload to registries
- Limited to SKILL.md project structures
Example
Request
Bump the version of the code-reviewer skill by a patch, add a changelog message about fixing the regex, and package it for distribution.
Result
Dry-run:
- Validated 'code-reviewer' (OK)
- Bump version: 0.1.0 -> 0.1.1
- Message: "Fixed regex for edge-case parsing"
- Prepare dist/code-reviewer-0.1.1.zip (excluding .git, pycache)
- Create github-tree/code-reviewer/ Ready to apply? Use --apply.
Questions
What specific problem does the Skill Publisher CLI solve for developers?
This CLI solves the problem of manual packaging and formatting errors. It automates validation, versioning, and distribution prep, ensuring your skills meet the strict submission standards of multiple registries without manual editing.
Which AI agents and registries are compatible with this tool?
The tool is built on Python and designed to be platform-agnostic for the AI ecosystem. It is compatible with any agent or framework that uses the SKILL.md standard or requires structured YAML frontmatter for marketplace listings.
How does the 'Dry-run' mode help during the publishing process?
The 'dry-run' feature allows you to simulate the entire publishing process without making permanent changes to your files. It identifies validation errors and shows you proposed version bumps before they are committed, preventing accidental data loss.
What exactly is included with my purchase of this skill?
You receive the full skill package including the orchestrator tools, pre-configured validation rules, and the CLI binary. It also includes comprehensive documentation on how to integrate the CLI into your existing CI/CD or local development workflow.
How does the skill handle versioning and changelogs?
The CLI handles SemVer (Semantic Versioning) automatically. It manages version increments in your metadata and concurrently maintains a CHANGELOG.md, ensuring your users can track features and bug fixes across every release.
Built by Nex AI. More skills, including the paid catalog: https://www.agensi.io/creators/ch1n4-g3nd4x
04 同仓库更多 Skills
serpmaven
Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.
revnu-landing-page-audit
Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.
revnu-growth-context
Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.
revnu-get-listed
Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.
revnu-ai-readiness-audit
Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.
proxy-troubleshooting
Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.