skillsmith

Draft Hackify-conformant SKILL.md files with required frontmatter and validation rules.

3|Updated May 11, 2026
One-click install
npx skills add https://github.com/nadyshalaby/hackify --skill skillsmith-nadyshalaby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skillsmith
Source: https://github.com/nadyshalaby/hackify/tree/main/skills/skillsmith
Command: npx skills add https://github.com/nadyshalaby/hackify --skill skillsmith-nadyshalaby

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill authorizes new skills for Hackify when you need a fresh SKILL.md that follows Hackify's binding contracts instead of a generic Claude Code skill.

Core Features & Use Cases

  • Hackify-specific skill authoring: Produces new skills under skills/<slug>/SKILL.md that match the required frontmatter schema and body structure.
  • Contract enforcement: Builds around the 7-section sub-agent contract, the 4-section Wizard contract, the name regex, and the mandatory OUTPUT word-cap.
  • Self-validation: Checks the authored skill against the 9-check checklist before writing it to disk.
  • Use case: Use this when you want to create a new Hackify-conformant skill such as a workflow helper, review helper, or meta-skill.

Quick Start

Use the skillsmith skill to create a new hackify skill for a changelog-writing workflow.

Frequently Asked Questions about skillsmith

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

FAQPage Schema
How do I create a new Hackify skill that passes validation checks?

To create a Hackify skill, draft a new SKILL.md file under skills/<slug>/ with required frontmatter, body sections, and validation rules, then run the 9-check checklist and validate-dod.sh contract checks before writing to disk.

What is a Hackify-conformant skill and when do I need one?

A Hackify-conformant skill is a SKILL.md file matching Hackify's binding contracts, including the 7-section sub-agent contract and 4-section Wizard contract. You need one when building workflow helpers, review helpers, or meta-skills for Hackify.

Does Hackify skill authoring require specific frontmatter and metadata formats?

Hackify skill authoring requires strict frontmatter schema adherence, including a name regex check and a mandatory OUTPUT word-cap. The SKILL.md file must match Hackify's discovery triggers and embedded prompt contracts to pass validation.

How do I validate Hackify skills before writing them to disk?

Validate Hackify skills by applying in-memory self-validation against a 9-check checklist and running the validate-dod.sh contract checks. This ensures the authored skill adheres to Hackify's discovery triggers and embedded prompt contracts before writing.

Can I use generic Claude Code skill formats instead of Hackify contracts?

Generic Claude Code skill formats lack Hackify's binding contracts, such as the 7-section sub-agent contract, 4-section Wizard contract, and mandatory OUTPUT word-cap. Use Hackify-specific authoring to ensure skills pass the validate-dod.sh checks.

Why does my authored skill fail the Hackify validate-dod.sh contract checks?

Skills fail validate-dod.sh checks when they violate the name regex, mandatory OUTPUT word-cap, or the required 7-section sub-agent and 4-section Wizard contracts. Ensure in-memory self-validation passes the 9-check checklist before writing to disk.