
Publish Skill
- 10 installs
- 22 repo stars
- Updated May 28, 2026
- acedergren/agentic-tools
publish-skill is a Claude Code skill that scaffolds, evaluates, and publishes a new skill to a GitHub repo installable via npx skills add.
About
publish-skill is a Claude Code skill for authoring a new skill and publishing it to a GitHub repo so it installs via npx skills add. It covers scaffolding with npx skills init, spec-compliant frontmatter, skill-judge evaluation, commit, push, and install verification. A developer uses it when adding a skill to the agentic-tools repo and wanting it to trigger correctly. It documents the exact install commands for the repo.
- Scaffolds, evaluates, commits, and publishes a new skill installable via npx skills add
- Enforces two-field frontmatter (name + description with WHAT/WHEN/KEYWORDS)
- Requires a skill-judge score of at least 84/120 before pushing
Publish Skill by the numbers
- 10 all-time installs (skills.sh)
- Ranked #523 of 782 Skill Development skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
publish-skill capabilities & compatibility
- Capabilities
- skill authoring · skill publishing · skill evaluation · install verification
- Works with
- github
- Use cases
- documentation
- Pricing
- Free
What publish-skill says it does
Add a new skill to `acedergren/agentic-tools` and make it installable via `npx skills add`.
Never push a skill without running `/skill-judge` first
npx skills add https://github.com/acedergren/agentic-tools --skill publish-skillAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 10 |
|---|---|
| repo stars | ★ 22 |
| Last updated | May 28, 2026 |
| Repository | acedergren/agentic-tools ↗ |
What it does
Scaffold, evaluate, and publish a new Claude Code skill to a GitHub repo installable via npx skills add.
Who is it for?
Authoring a new skill and making it installable via npx skills add from a GitHub repo.
Skip if: Non-skill code publishing or skills that have not passed skill-judge evaluation.
When should I use this skill?
Creating a new skill and publishing it to a GitHub repo for installation via npx skills add.
What you get
A spec-compliant, evaluated skill committed and pushed so it installs via npx skills add.
- scaffolded SKILL.md
- committed and pushed skill
- install verification
By the numbers
- Frontmatter must have exactly two fields
- Target skill-judge score of at least 84/120
- SKILL.md under 300 lines
Files
Publish Skill
Add a new skill to acedergren/agentic-tools and make it installable via npx skills add.
Workflow
1. Scaffold
cd ~/Projects/agentic-tools/skills
npx skills init <skill-name>
# Creates skills/<skill-name>/SKILL.md2. Write the skill
Edit skills/<skill-name>/SKILL.md. Frontmatter must have exactly two fields:
---
name: skill-name-with-hyphens # lowercase, letters/numbers/hyphens, ≤64 chars
description: "Use when [trigger conditions]. [WHAT]. Keywords: ..."
---Description rules — all three required:
- WHAT: what does it do?
- WHEN: starts with "Use when..."
- KEYWORDS: searchable terms at the end
3. Evaluate before committing
Run /skill-judge on the new skill. Target ≥ 84/120 (C grade) before pushing.
Key checks:
- No "What is X" explanations Claude already knows
- Has explicit NEVER list with reasons
- SKILL.md < 300 lines (heavy reference →
references/subdir) - No extra frontmatter fields (license, metadata, version)
4. Commit and push
git add skills/<skill-name>/
git commit -m "feat(skills): add <skill-name> skill"
git push origin main5. Verify installable
npx skills add acedergren/agentic-tools@<skill-name> -g -yIf the skill isn't found, check:
- Directory name matches
namefield in frontmatter - SKILL.md is at
skills/<skill-name>/SKILL.md(not nested deeper)
Install Commands for This Repo
# Single skill
npx skills add acedergren/agentic-tools@<skill-name> -g
# All skills
npx skills add acedergren/agentic-tools --all -g -y
# List available without installing
npx skills add acedergren/agentic-tools -lNEVER
- Never push a skill without running `/skill-judge` first — a skill that fails evaluation won't trigger correctly because its description lacks WHAT/WHEN/KEYWORDS
- Never use extra frontmatter fields — only
nameanddescriptionare valid;license,metadata,versioncause parse errors in some agents - Never put "When to use" only in the body — the agent only reads the description to decide whether to load; body content is invisible at trigger time
- Never name a skill with spaces or special chars —
my skill!breaks install; usemy-skill
Related skills
FAQ
What frontmatter fields must a skill have?
Exactly two: name (lowercase hyphens, up to 64 chars) and description that states WHAT it does, WHEN to use it, and KEYWORDS; extra fields cause parse errors in some agents.
What score must a skill reach before publishing?
Run /skill-judge and target at least 84/120 (a C grade) before pushing.