skill-writter

Create agent skills with valid YAML frontmatter and trigger descriptions.

3|Updated Apr 21, 2024
One-click install
npx skills add https://github.com/gabrielfruet/.dotfiles --skill skill-writter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-writter
Source: https://github.com/gabrielfruet/.dotfiles/tree/main/pi/agent/skills/skill-writter
Command: npx skills add https://github.com/gabrielfruet/.dotfiles --skill skill-writter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Poorly formatted agent skills with mismatched names, vague trigger descriptions, or non-compliant frontmatter fail to load when needed or are never discovered by the agent, leading to broken workflows and wasted development time.

Core Features & Use Cases

  • Frontmatter Enforcement: Guides creation of valid YAML frontmatter with matching name and description fields that align with directory naming conventions.
  • Trigger Optimization: Teaches how to write specific, actionable "Use when..." trigger descriptions to ensure skills load at the correct time without false matches.
  • Content Best Practices: Provides rules for concise, maintainable skill content (under 50 lines, minimal code examples, no redundant information) to keep skills efficient and easy to update.
  • Use Case: If you need to build a skill that automates formatting Markdown documents for your team's internal wiki, this skill ensures it has a valid name, a clear trigger so the agent loads it when you ask to format wiki pages, and follows all required formatting rules.

Quick Start

Use the skill-writter skill to create a new skill that triggers when you ask to draft client follow-up emails.

Frequently Asked Questions about skill-writter

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

FAQPage Schema
Why does my agent skill fail to load when its trigger conditions are met?

Agent skills fail to load when triggered due to incorrect YAML frontmatter, mismatched naming conventions between the name field and directory, or vague trigger descriptions that prevent proper discovery. Ensuring valid frontmatter and specific "Use when..." phrasing resolves loading failures.

How do I write trigger descriptions for agent skills so they activate at the right time?

Writing trigger descriptions for agent skills requires specific, actionable "Use when..." phrasing that defines exact invocation conditions. Optimized trigger descriptions prevent false matches and ensure the agent discovers and loads the skill only when the specified task automation context applies.

What are the formatting requirements for valid YAML frontmatter in agent skills?

Valid YAML frontmatter in agent skills requires matching name and description fields that align with directory naming conventions, concise content under 50 lines, and minimal redundant code examples. Meeting these parsing standards ensures correct loading during workflow delegation and task automation.

Can I use long markdown files with code examples when creating agent skills for document processing?

Agent skills for document processing require concise content under 50 lines with minimal code examples. Exceeding content limits or including redundant information breaks skill loading standards, making maintainability and efficient parsing difficult during workflow creation.

What is the best way to structure a new agent skill for task automation workflows?

The best way to structure an agent skill for task automation is enforcing valid YAML frontmatter with matching name fields, applying specific "Use when..." trigger optimization, and keeping content under 50 lines to align with agent skill loading and parsing standards.

Do I need to match the skill name in the frontmatter to the directory name?

Yes, the skill name in the YAML frontmatter must match the directory naming convention exactly. Mismatched names cause the agent skill to become undiscoverable, leading to broken workflows and failed task automation when trigger conditions are met.