newskill

Create or repair skill hub registration entries across folder, README, marketplace, and trigger eval surfaces.

8|1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/duthaho/skillhub --skill newskill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: newskill
Source: https://github.com/duthaho/skillhub/tree/main/.claude/skills/newskill
Command: npx skills add https://github.com/duthaho/skillhub --skill newskill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you add a new skillhub skill or repair an existing one that has drifted across its registration surfaces, so the folder, README, marketplace, and trigger rules stay in sync.

Core Features & Use Cases

  • Scaffold a skill: Create a new skill folder with valid frontmatter and the right registration entries.
  • Repair drift: Find and fix missing README rows, marketplace listings, or trigger eval cases for an existing skill.
  • Validate completeness: Use the validator as the source of truth to confirm every required surface agrees before shipping.

Quick Start

Ask Claude Code to run the newskill workflow for a chosen skill name and category, then validate that every registration surface matches.

Frequently Asked Questions about newskill

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

FAQPage Schema
How do I fix skill registration drift across folder, README, and marketplace surfaces?

Skill registration drift is repaired by detecting missing or inconsistent entries across folder, README, marketplace, and trigger eval surfaces, then correcting them using validator-based verification to enforce frontmatter consistency before release.

What's the best way to scaffold a new skillhub skill without missing registration entries?

Scaffolding a new skillhub skill requires creating a folder with valid frontmatter and generating the correct registration entries across README, marketplace, and trigger eval surfaces, followed by validator-based completeness checks before shipping.

Why does my skill fail validation when frontmatter is inconsistent across registration surfaces?

Frontmatter inconsistency causes validation failures because the validator checks that every required registration surface — folder, README, marketplace, and trigger eval — agrees on metadata fields before allowing release.

Can I use the newskill workflow to check trigger eval cases for an existing skill?

Yes, the newskill workflow validates trigger eval cases for existing skills by using the validator as the source of truth to confirm every required surface agrees and no drift has occurred since the original registration.

Do I need strict frontmatter consistency before shipping a skill to the marketplace?

Strict frontmatter consistency is required before shipping because the validator enforces that folder, README, marketplace, and trigger eval surfaces all match; any drift must be corrected and re-validated prior to release.

What's the difference between scaffolding a new skill and repairing drift in an existing one?

Scaffolding creates a new skill folder with valid frontmatter and all registration entries from scratch, while drift repair finds and fixes missing README rows, marketplace listings, or trigger eval cases for an already registered skill.