publish-skill

Publish a local skill from dotfiles to a public GitHub repository.

1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/chrisliu298/dotfiles --skill publish-skill-chrisliu298
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-skill
Source: https://github.com/chrisliu298/dotfiles/tree/main/.claude/skills/publish-skill
Command: npx skills add https://github.com/chrisliu298/dotfiles --skill publish-skill-chrisliu298

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publishing a local skill from ~/dotfiles/agents/extensions/skills/<name>/ to a public GitHub repo lets teams reuse and share skills while keeping the local version as the source of truth. The published repo acts as a standalone distribution while the local copy remains the authoritative source.

Core Features & Use Cases

  • Publish workflow: validates the local skill, copies it to a new GitHub-ready folder, and creates a public repository for others to install.
  • Documentation & licensing: generates a README and MIT license scaffold to accompany the published skill, preserving provenance.
  • Lifecycle management: keeps the local directory as the source of truth and supports re-publishing when updates occur.
  • Use case: a team wants to share a locally developed skill across multiple machines by publishing to a public GitHub repo.

Quick Start

Publish a local skill by running publish-skill <skill-name> to publish it into a public GitHub repository.

Frequently Asked Questions about publish-skill

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

FAQPage Schema
How do I publish a local skill from my dotfiles to a public GitHub repository?

To publish a local skill to a public GitHub repository, run the publish-skill command with the skill name. It validates the local skill, copies it to a GitHub-ready folder, generates a README and MIT license, and initializes the git repository for public sharing.

What is the best way to share locally developed skills across multiple machines?

The best way to share locally developed skills across machines is publishing them to a public GitHub repository. This creates a standalone distribution repo while keeping the local dotfiles directory as the authoritative source of truth for future updates.

Do I need to install external dependencies to publish skills to GitHub via CLI?

You do not need external dependencies to publish skills beyond standard shell tooling and the gh CLI. The publishing process validates your gh CLI authentication before proceeding to ensure seamless repository creation and git operations.

Can I regenerate README and LICENSE files when re-publishing an updated local skill?

Yes, you can regenerate README and LICENSE files during re-publishing. The lifecycle management feature supports re-publishing updated local skills by copying the new version and scaffolding fresh MIT license and README documentation to preserve provenance.

Why does my local skill need validation before copying to a public GitHub repo?

Your local skill needs validation before copying to a public GitHub repo to ensure the skill structure is correct and ready for distribution. This prevents publishing incomplete or broken skills by checking prerequisites before creating the public repository.

What's the difference between the local dotfiles skill and the published GitHub repo?

The local dotfiles skill remains the authoritative source of truth, while the published GitHub repo acts as a standalone distribution. Re-publishing updates the public repository from the local copy, ensuring teams always install from the latest validated distribution.