package-publisher
SolidPublish packages to language-specific registries
Install
Quality Score: 92/100
Skill Content
Details
- Author
- a5c-ai
- Repository
- a5c-ai/babysitter
- Created
- 4 months ago
- Last Updated
- today
- Language
- JavaScript
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
publish-skill
Use when the user wants to publish a new agent skill (a directory containing `pyproject.toml` + `src/<pkg>/skill_files/SKILL.md`) to the company's private AWS Agent Registry + CodeArtifact. Walks build → CodeArtifact upload → CreateRegistryRecord → optional submit-for-approval. Requires AWS credentials with codeartifact:PublishPackageVersion and bedrock-agentcore:Create* on the target registry. Refuses to run if those permissions are absent. Triggers on phrases like "publish this skill", "register this in our skill registry", "把这个 skill 发布出去", "推到 skills registry".
publish-skill
Convert a personal agent skill into a distributable, open-source-ready skill. Runs PII audit, generalization, license compatibility check, cross-platform adapter review, and packaging workflow.
publish-skill
Publish a Claude Code skill to GitHub as a polished, adoptable open-source repo, AND diagnose `claude plugin install` failures on a published skill. Use when the user says "publish this skill", "put this on GitHub", "share this skill", "release this skill publicly", "open source my skill", "make this skill installable", "create a GitHub repo for my skill", "package this skill for the marketplace", or wants to update an existing published skill repo. Also trigger when the user says "submit to awesome-claude-skills", "add my skill to the awesome list", "how do I let others install my skill?", "I finished my skill, now what?", "push my skill to a public repo", "generate a README and publish", "bump the version and republish", or "turn my local skill into a polished repo". ALSO trigger on `claude plugin install` failures and diagnostic questions: `Plugin X not found in any configured marketplace`, `Plugin X not found in marketplace Y`, `Invalid schema: plugins.0.source: Invalid input`, `Failed to add marketplace:
release
Prepare dynobox packages for release to npm. Use this skill whenever the user asks to release, publish, ship, bump, or cut a version of any dynobox package — including dry runs, version bumps, changelog updates, and git tagging. Also trigger when the user asks about the release process or wants to verify publish readiness.
npm-publish-config
Configure npm publishing with proper bin entry, files, and registry settings.