writing-skills

Creates and validates reusable SKILL.md documentation for agent workflows.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Jhabbig/Habbig --skill writing-skills-jhabbig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Jhabbig/Habbig/tree/main/.claude/skills/writing-skills
Command: npx skills add https://github.com/Jhabbig/Habbig --skill writing-skills-jhabbig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps when you need to create, edit, or verify a reusable skill and want the result to be discoverable, concise, and reliable for future agents.

Core Features & Use Cases

  • Skill authoring guidance for structure, naming, frontmatter, and supporting content.
  • Pressure testing and verification with subagents so weak instructions are caught before deployment.
  • Useful for documenting repeatable workflows, reference material, and guardrails that other agents should follow.

Quick Start

Describe the skill you want to write or verify, and I will help turn it into a concise, tested SKILL.md.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I create agent skills that are actually discoverable and reusable?

To create discoverable agent skills, author a concise SKILL.md entry point with required YAML frontmatter containing name and description, including only supporting reference or script directories that are actually present.

What is the best way to structure documentation for agent workflows?

The best way to structure agent workflow documentation is to use a valid skill unit containing a discoverable SKILL.md file, YAML frontmatter, and supporting reference directories, ensuring repeatable workflows are concise and reliable.

How does subagent testing improve skill authoring before deployment?

Subagent testing improves skill authoring by pressure testing and verifying instructions, catching weak documentation and guardrails so future agents reliably follow repeatable workflows before deployment.

Do I need YAML frontmatter to edit existing SKILL.md files?

Yes, you need YAML frontmatter with name and description fields when editing existing SKILL.md files to maintain a valid skill unit structure that remains discoverable for future agent workflows.

When should I not use a skill unit for documenting reference material?

You should not use a skill unit when your reference material lacks a discoverable SKILL.md entry point or required YAML frontmatter, as these are mandatory for creating a valid, reusable skill unit.