skill-publisher-cli
Plan SKILL.md Releases and Distribution Packages
Preparing skill releases requires consistent metadata, version history, and clean package contents. This documentation guide outlines a reviewable workflow, but does not include executable publishing tools.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "skill-publisher-cli" from https://skillstore.io/skills/nexaiguy-skill-publisher-cli.md and its manifest at https://skillstore.io/api/skills/nexaiguy-skill-publisher-cli/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "skill-publisher-cli". What can I use directly from this public package?
Expected outcome:
- Available: a guide covering validation, versioning, packaging, and metadata preparation.
- Not included: helper scripts, extension source, templates, or a runnable CLI.
- Use the guide for planning; obtain and review separate tools before expecting automation.
Using "skill-publisher-cli". Plan a patch release from 0.1.0 for a regex fix without changing files.
Expected outcome:
- Proposed version: 0.1.1.
- Proposed changelog entry: Fixed regex for edge-case parsing.
- Package plan: exclude Git metadata and Python cache folders.
- Status: proposal only; no validation executed or archive created.
- Approval is required before applying changes.
Security Audit
SafeAll four static findings are false positives: inline Markdown formatting, attribution links, and a catalog URL contain no executable commands or reconnaissance. No evidence found of prompt injection, credential access, or data exfiltration in SKILL.md. The package contains only documentation, so its advertised automation cannot be verified.
Risk Factors
โ๏ธ External commands (1)
๐ Network access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/nexaiguy-skill-publisher-cli/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/nexaiguy-skill-publisher-cli?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/nexaiguy-skill-publisher-cli?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/nexaiguy-skill-publisher-cli/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/nexaiguy-skill-publisher-cli.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
nexaiguy. (2026). skill-publisher-cli security audit report (audit version 1) [Author version 1.2]. Skillstore. https://skillstore.io/skills/nexaiguy-skill-publisher-cli/audits/1BibTeX citation
@techreport{nexaiguy-nexaiguy-skill-publisher-cli-2026,
author = {nexaiguy},
title = {skill-publisher-cli security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/nexaiguy-skill-publisher-cli/audits/1},
note = {Author version 1.2}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "skill-publisher-cli security audit report (audit version 1)"
version: "1.2"
type: report
authors:
- name: "nexaiguy"
date-released: "2026-11-02"
url: "https://skillstore.io/skills/nexaiguy-skill-publisher-cli/audits/1"
identifiers:
- type: other
value: "skillstore:nexaiguy-skill-publisher-cli:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Prepare a first skill release
Create a release checklist covering frontmatter, naming, internal links, and package exclusions before preparing a marketplace submission.
Coordinate a maintenance update
Plan a patch version change and changelog entry with an approval checkpoint before modifying release files.
Standardize release requirements
Use the documented workflow as requirements for separately implemented validation and packaging tools across a team.
Try These Prompts
Summarize the documented checks for a first SKILL.md release. Identify which steps require tools missing from this package.
Review my supplied SKILL.md and directory listing for frontmatter, naming, internal links, and packaging exclusions. Report missing evidence without changing files.
Using my supplied metadata, plan a patch release for a regex fix. Draft the changelog and package checklist; request approval before edits.
Design a dry-run-first workflow for our SKILL.md repository. Separate documented requirements from missing tooling, and specify approval gates, validation checks, and packaging exclusions.
Best Practices
- Confirm which executable tools are available before requesting automated release actions.
- Review proposed version changes, changelog entries, and package contents before approving writes.
- Check current destination registry requirements independently before submitting a release.
Avoid
- Assuming the public guide includes the advertised scripts or CLI binary.
- Treating an illustrative dry-run result as proof that validation or packaging actually occurred.
- Publishing an archive without reviewing excluded files, metadata, and the intended version.