titan-agent-skill-authoring

Generate validated SKILL.md files with required YAML frontmatter for Titan Agent in-repo skills.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures Titan Agent skills are authored in a way that passes the repo validator, is discoverable, and loads reliably by providing the exact required SKILL.md frontmatter and structure.

Core Features & Use Cases

  • Valid SKILL.md authoring: Defines the required YAML frontmatter constraints (must include name and description, description length limit, and correct file formatting rules).
  • In-repo workflow guidance: Clarifies how to create vs patch skills and when to use write_file versus skill_manage, specifically for committed skills under skills/.
  • Peer-matched structure and verification: Recommends a consistent section layout and provides a checklist to catch common mistakes before committing.

Quick Start

Use the titan-agent-skill-authoring skill to create a new in-repo skill at skills/<category>/<name>/SKILL.md by writing a correctly formatted YAML frontmatter with a clear, trigger-based description and then following the recommended sections order.

Frequently Asked Questions about titan-agent-skill-authoring

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

FAQPage Schema
What is the required YAML frontmatter for a SKILL.md file?

The required YAML frontmatter for a SKILL.md file must include name and description fields enclosed in delimiters. The description must adhere to a specified length limit to pass the repo validator.

How do I create an in-repo skill under skills/<category>/<name>/SKILL.md?

To create an in-repo skill, write a correctly formatted SKILL.md file with valid YAML frontmatter and a non-empty operational body. Use write_file for new skills or skill_manage to patch existing committed skills.

Why does my SKILL.md fail the repo validator during skill authoring?

Skill authoring fails the repo validator when SKILL.md files have missing YAML frontmatter fields, incorrect delimiters, descriptions exceeding length constraints, or an empty operational body.

What sections should I include when authoring a software-development skill?

Authoring a software-development skill requires a consistent section layout matched to peer conventions. The file must contain a non-empty operational body with actionable content following the YAML frontmatter.

When should I use write_file versus skill_manage for in-repo workflows?

Use write_file when creating a new in-repo skill at skills/<category>/<name>/SKILL.md. Use skill_manage when you need to patch or edit an existing committed skill to apply updates.

Is there a verification checklist for SKILL.md formatting constraints?

Yes, a verification checklist catches common SKILL.md formatting mistakes before committing. It validates frontmatter delimiters, required fields, description length, and the presence of an operational body.