writing-skills

Author Skill unit definitions with mandatory sections and frontmatter.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/radenadri/skills-alena --skill writing-skills-radenadri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/radenadri/skills-alena/tree/main/skills/writing-skills
Command: npx skills add https://github.com/radenadri/skills-alena --skill writing-skills-radenadri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide provides the structure, standards, and testing requirements necessary to create high-quality Skill units that are consistent, auditable, and easy to reuse across the library.

Core Features & Use Cases

  • Enforces mandatory frontmatter (name, description) and required sections (Iron Law, Iron Questions, Anti-Shortcut Rules, The Process, Red Flags, Integration)
  • Guides contributors to produce verifiable, testable processes, guardrails, and clear integration notes for seamless reuse
  • Supports standardized activation and discoverability across tools and sessions

Quick Start

Draft a new SKILL.md for a target capability following the writing-skills template.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
What is the standard structure for writing a Skill unit definition?

A standard Skill unit definition requires frontmatter for name and description, alongside mandatory sections including the Iron Law, Anti-Shortcut Rules, Iron Questions, The Process, Red Flags, and Integration.

How do I create a markdown template for documentation with quality assurance guardrails?

To create documentation with quality assurance guardrails, draft a SKILL.md file following the writing-skills template, ensuring all mandatory sections and frontmatter are present for compliance.

Does auditing an existing skill definition require checking for toxicity and frontmatter presence?

Auditing an existing skill definition requires checking frontmatter presence, verifying mandatory sections like Iron Law and The Process, and running toxicity checks to ensure full compliance.

What's the best way to standardize skill formatting for reuse across a library?

Standardizing skill formatting for library reuse involves applying a master reference template that enforces mandatory sections, guardrails, and clear integration notes for seamless discoverability.

What happens if mandatory sections like Anti-Shortcut Rules or Red Flags are missing from my documentation?

Missing mandatory sections like Anti-Shortcut Rules or Red Flags means your documentation fails the quality standards compliance check, requiring you to add them for validation.

Can I use optional components directories when authoring new skills for a library?

Yes, you can use optional components directories when authoring new skills, provided the core mandatory sections and frontmatter still adhere to the master reference quality standards.