writing-great-skills

Guide authors to write and edit SKILL.md files with consistent frontmatter and validation.

3|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/vtgiang-dotcom/Solo-Code-Harness --skill writing-great-skills-vtgiang-dotcom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-great-skills
Source: https://github.com/vtgiang-dotcom/Solo-Code-Harness/tree/main/.gemini/antigravity/skills/writing-great-skills
Command: npx skills add https://github.com/vtgiang-dotcom/Solo-Code-Harness --skill writing-great-skills-vtgiang-dotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reference for authoring and editing skills in this harness. Use when: create skill, edit skill, write SKILL.md, improve a skill, skill too long, skill not triggering, add a new capability to the harness.

Core Features & Use Cases

The guide ensures that skill authors have a single source of truth by directing edits to SKILL.md, enforces that the frontmatter includes name and description, and provides best-practice structure (leading words, completion criteria, and safety checks) to maintain consistency and predictability across the harness. It also outlines a workflow: edit the skill, run make generate to update generated assets, and run validation checks before committing. Use cases include creating a new skill, modifying an existing one, and pruning no-ops to keep skills concise.

Quick Start

Edit the SKILL.md frontmatter and body for the target skill, then run make generate to produce harness outputs.

Frequently Asked Questions about writing-great-skills

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

FAQPage Schema
How do I write a SKILL.md file to create a new skill for the harness?

To write a SKILL.md file, edit the frontmatter to include at least a name and description, then structure the body with leading words, completion criteria, and safety checks. Run make generate to produce harness outputs.

What is the required frontmatter structure for a skill in this harness?

The required frontmatter structure mandates at least a name and a description field. This ensures the skill is properly indexed and triggers predictably within the harness environment.

Why does my skill not trigger correctly in the harness?

Your skill might not trigger due to missing frontmatter or an overly verbose body. Ensure the SKILL.md frontmatter includes a name and description, and prune no-ops to keep the body concise.

What is the best way to update an existing skill without breaking the repository?

The best way to update a skill is to edit only the SKILL.md file, run make generate to update generated assets, and execute validation checks before committing to ensure repository consistency.

When should I prune or restructure a skill that has become too long?

You should prune a skill when it becomes too long or contains no-ops. Restructure the SKILL.md body to maintain concise leading words and clear completion criteria, ensuring predictability across the harness.

Does the skill authoring workflow require running validation checks before committing?

Yes, the workflow requires running validation checks before committing. After editing SKILL.md and running make generate, validation enforces consistent frontmatter and body structure compliance.