publish-skill

Convert personal Claude Code skills into distributable packages with PII audits.

243|60|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Aperivue/medsci-skills --skill publish-skill-aperivue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-skill
Source: https://github.com/Aperivue/medsci-skills/tree/main/skills/publish-skill
Command: npx skills add https://github.com/Aperivue/medsci-skills --skill publish-skill-aperivue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Convert a personal Claude Code skill into a clean, distributable package by auditing sensitive data, generalizing language and role assumptions, and ensuring license compatibility.

Core Features & Use Cases

  • PII audit to remove sensitive information and ensure privacy before distribution.
  • Generalization of language and role assumptions to make skills domain-agnostic.
  • License compatibility checks and packaging workflow to produce a ready-to-distribute skill artifact.
  • Example: Transform a private Claude skill into an OSS-ready package with docs and metadata.

Quick Start

Provide the source skill path and target package path; the workflow will audit for PII, generalize language, verify licenses, and package the skill.

Frequently Asked Questions about publish-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I package a personal Claude Code skill for open-source distribution?

To package a Claude Code skill for open-source distribution, you use a 7-phase workflow that audits sensitive data, generalizes language, validates licenses, and produces a ready-to-distribute skill artifact.

What does a PII audit check for when preparing a skill for public release?

A PII audit checks for sensitive information within your skill's code and documentation, removing personal data and ensuring privacy before the package is distributed publicly.

How do I make a private Claude skill domain-agnostic before sharing it?

You make a private Claude skill domain-agnostic by applying language generalization, which removes specific role assumptions and contextual biases during the packaging workflow.

Do I need to verify license compatibility before packaging a Claude skill?

Yes, you need to verify license compatibility before packaging a Claude skill, as the workflow uses reference licenses to validate compliance and ensure the artifact is legally distributable.

What is the best way to automate open-source packaging for Claude skills?

The best way to automate open-source packaging for Claude skills is using an enforced workflow that scripts PII audits and license checks, yielding a clean, distributable package without manual intervention.