update-skill

Standardize SKILL.md frontmatter and structure for the Warp repository.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/lalaABC/waprcn --skill update-skill-lalaabc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-skill
Source: https://github.com/lalaABC/waprcn/tree/main/.agents/skills/update-skill
Command: npx skills add https://github.com/lalaABC/waprcn --skill update-skill-lalaabc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps authors maintain consistent skill units by enforcing required frontmatter and structure, simplifying creation and revision of SKILL.md in the Warp skills repository.

Core Features & Use Cases

  • Validates SKILL.md frontmatter and structure to ensure compliance with naming rules and discovery prompts.
  • Guides creation or revision of SKILL.md, including frontmatter, body content, and references to optional directories (scripts/, references/, assets/).
  • Use cases include adding new skills or updating existing ones across the repository to maintain consistency.

Quick Start

Draft or revise the SKILL.md frontmatter to match the required fields, then flesh out the body with structured guidance.

Frequently Asked Questions about update-skill

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

FAQPage Schema
How do I validate SKILL.md frontmatter and structure for consistency?

To validate SKILL.md frontmatter, standardize the required name and description fields alongside the body structure to ensure compliance with naming rules and discovery prompts across the Warp repository.

What is the required frontmatter format for creating a new skill?

The required frontmatter format for a new skill includes standardized name and description fields, which enforce consistent skill units and ensure discoverability across the repository.

How do I organize optional directories like scripts and assets when updating a skill?

When updating a skill, organize optional directories by referencing scripts, references, and assets within the SKILL.md body to maintain clear guidance and structural compliance.

Can I use this to revise existing skill documentation across the Warp repository?

Yes, you can revise existing skill documentation across the Warp repository by applying safety validations and enforcing the required frontmatter and body structure to maintain consistency.

What's the best way to ensure my YAML frontmatter follows skill creation best practices?

The best way to ensure YAML frontmatter follows best practices is to enforce required structural fields and run safety validations during the creation or revision process.