writing-skills

Create and validate writing-skills SKILL.md files against MTK CSO standards.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing high-quality SKILL.md templates that comply with MTK's CSO framework and validate structure before shipping.

Core Features & Use Cases

  • Enforces required frontmatter (name, description) and mandated sections (Overview, When To Use, Workflow, Verification)
  • Guides rationalization and testing practices, including Phase-based workflow and verification checks
  • Acts as a blueprint for scalable skill creation and governance within MTK

Quick Start

Follow the anatomy and validation steps to create and ship a new writing-skills SKILL.md.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I validate a SKILL.md file against MTK CSO standards?

Validating a SKILL.md file against MTK CSO standards requires checking that frontmatter contains name and description fields, and that required sections like Overview, When To Use, Workflow, and Verification are explicitly defined.

What is the CSO trigger pattern for skill descriptions?

The CSO trigger pattern is a specific formatting rule applied to the description field in SKILL.md frontmatter that ensures the description correctly signals when the skill should activate within MTK workflows.

How do I structure documentation for MTK skill-writing workflows?

Structuring documentation for MTK skill-writing workflows involves creating a SKILL.md with mandated sections including Overview, When To Use, Workflow, and Verification, while explicitly defining dependencies, components, and safety checks.

Do I need to define dependencies and components for every MTK skill?

You need to explicitly define dependencies and components for every MTK skill because MTK CSO standards require these elements in the SKILL.md file to ensure proper rationalization and safety checks.

What's the best way to automate writing-skills creation for MTK?

Automating writing-skills creation for MTK is best achieved by using a blueprint that enforces frontmatter requirements and Phase-based verification checks, ensuring scalable skill creation and governance within the MTK toolkit.

When should I not use automated SKILL.md templates for documentation?

You should not use automated SKILL.md templates when your documentation requirements fall outside the MTK CSO framework, as the template strictly enforces specific sections and validation rules that may not apply to non-MTK contexts.