publish-public-skills

Publish and sync shared skills to the TECHHY-VC/SKILLS GitHub repository.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill publish-public-skills-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-public-skills
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/publish-public-skills
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill publish-public-skills-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It standardizes how shared public skills are created, updated, committed, and pushed to a single canonical GitHub repository, preventing skills from being scattered across multiple repos or lost as local-only copies. ## Core Features & Use Cases - Canonical Publishing Workflow: Enforces a clean-clone, pull, edit, commit, and push sequence targeting TECHHY-VC/SKILLS as the default public destination. - Structure Validation: Requires SKILL.md and agents/openai.yaml, with optional validation when a validator is available. - Sync and Verification: Keeps local installed skill copies in sync and verifies pushes via git status, git fetch, and git ls-remote. - Use Case: After writing a new reusable skill locally, ask the agent to publish it so it lands as a focused commit on main in the shared public skills repository. ## Quick Start Use the publish-public-skills skill to add this new skill to the shared TECHHY-VC/SKILLS repository and push it to main.

Frequently Asked Questions about publish-public-skills

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

FAQPage Schema
How do I publish a skill to a shared public GitHub repository?

Start in a clean clone of TECHHY-VC/SKILLS, pull main, add the skill under skills/<skill-name>/ with SKILL.md and agents/openai.yaml, then commit with a focused message and push to origin main.

What files are required for a public skill package?

A public skill requires SKILL.md with name and description frontmatter plus an agents/openai.yaml interface file. References, assets, or scripts directories are added only when the skill actually needs them.

Can I publish public skills to a different repository?

TECHHY-VC/SKILLS is the default and only public destination. Publishing to another repository happens only when the user explicitly overrides the destination.

How do I verify a skill push to GitHub succeeded?

Check git status before committing, then confirm the commit landed remotely after pushing. If output is unclear, run git fetch, git status --short --branch, or git ls-remote origin refs/heads/main.

What happens if the push to the skills repository is blocked?

The workflow requires reporting exactly what is missing, such as authentication, remote configuration, or permissions, rather than silently failing or retrying blindly.