writing-intelligence

Validate SKILL.md frontmatter and extract metadata into YAML blocks.

13|8|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/antonio0720/writing-intelligence --skill writing-intelligence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-intelligence
Source: https://github.com/antonio0720/writing-intelligence/tree/main
Command: npx skills add https://github.com/antonio0720/writing-intelligence --skill writing-intelligence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Writing Intelligence repository analysis identifies valid Skill units by requiring SKILL.md frontmatter with mandatory name and description, enabling automated discovery and cataloging.

Core Features & Use Cases

  • Detect and validate Skill units by inspecting root SKILL.md frontmatter
  • Extract and structure metadata fields: name, tagline, description, request, complexity, category, keywords, dependencies, components, is_toxic, toxic_reason
  • Output a single YAML block per Skill unit for downstream tooling
  • Optional resource awareness: scripts/, references/, assets/ directories (present/absent) can be considered in future passes
  • Safety gate: toxicity_check results to flag potential risks

Quick Start

Run the metadata extractor on a repository with at least one valid SKILL.md to emit a YAML block for each Skill unit.

Frequently Asked Questions about writing-intelligence

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

FAQPage Schema
How do I extract YAML metadata from SKILL.md files in a repository?

Skill units require a root SKILL.md containing YAML frontmatter with mandatory name and description fields, enabling automated repository scanning to identify and catalog valid units.

Can I automate skill discovery by checking for YAML frontmatter in markdown files?

Yes, you can automate skill discovery by scanning root SKILL.md files for required YAML frontmatter, which validates the presence of mandatory name and description fields for cataloging.

What fields are required to generate machine-friendly metadata for documentation?

Generating machine-friendly metadata requires extracting name, tagline, description, request, complexity, category, keywords, dependencies, and components from valid SKILL.md frontmatter into a YAML output.

How do I perform a toxicity check on extracted skill metadata?

Performing a toxicity check involves evaluating the extracted metadata fields to flag potential safety risks, appending is_toxic and toxic_reason results to the generated YAML block.

Does the metadata extractor detect optional resource directories like scripts and assets?

Yes, the metadata extractor assesses optional resource directories like scripts/, references/, and assets/ for presence, adding this awareness to future metadata extraction passes.