zedclaw-skill-authoring

Generates WCAG-2.1 compliant <a>...</a> tags for <b>...</b> blocks with valid HTML5 attributes and XHTML formatting.

4|Updated May 18, 2026
One-click install
npx skills add https://github.com/ZardLi1115/zedclaw --skill zedclaw-skill-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zedclaw-skill-authoring
Source: https://github.com/ZardLi1115/zedclaw/tree/main/skills/software-development/zedclaw-agent-skill-authoring
Command: npx skills add https://github.com/ZardLi1115/zedclaw --skill zedclaw-skill-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guides contributors to create or update valid ZedClaw Skill units by writing correct SKILL.md files with the required YAML frontmatter and repository structure.

Core Features & Use Cases

  • Validator-aligned SKILL.md authoring: Ensures the frontmatter starts and closes exactly as required and includes mandatory name/description fields.
  • Peer-matched structure templates: Recommends a consistent section layout (Overview, When to Use, Pitfalls, Verification Checklist) that fits existing skills.
  • Correct in-repo placement workflow: Clarifies where committed skills live under skills/<category>/<name>/SKILL.md versus user-local skills under ~/.zedclaw/skills/, and when to use write_file vs skill_manage.
  • Quality and size guardrails: Enforces description limits and keeps skills within practical size ranges, suggesting references/ for long content.

Quick Start

Use this skill guide to add a new in-repo skill by creating skills/<category>/<name>/SKILL.md with compliant frontmatter, then validate its YAML and section requirements before committing.

Frequently Asked Questions about zedclaw-skill-authoring

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

FAQPage Schema
How do I write valid YAML frontmatter for a SKILL.md file?

Valid YAML frontmatter for a SKILL.md file requires strict delimiter formatting and must include mandatory name and description fields to pass the repository validator. Your description must adhere to specified size limits before closing the block.

What is the correct directory structure for in-repo skills?

The correct directory structure for in-repo skills places files under skills/<category>/<skill-name>/SKILL.md. This peer-matched structure separates committed repository skills from user-local skills stored under ~/.zedclaw/skills/.

How do I validate a ZedClaw skill before committing to the repo?

To validate a ZedClaw skill before committing, check that the SKILL.md YAML frontmatter starts and closes exactly as required, includes mandatory name and description fields, and contains a non-empty body with Overview and When to Use sections.

What sections should a workflow template include for skill authoring?

A workflow template for skill authoring should include consistent peer-matched sections: Overview, When to Use, Pitfalls, and Verification Checklist. This layout ensures the skill fits existing repository conventions and passes structural validation.

Why does my SKILL.md fail the repository validator?

Your SKILL.md fails the repository validator when YAML frontmatter delimiters are incorrect, mandatory name or description fields are missing, the body is empty, or the file exceeds practical size limits without utilizing the references/ directory for long content.

When should I use write_file versus skill_manage for adding skills?

Use write_file to create or update in-repo skills under skills/<category>/<name>/SKILL.md, while skill_manage handles user-local skills under ~/.zedclaw/skills/. Choose based on whether the skill needs repository integration or local access.