software-design

Detect valid Skill units in repositories and generate normalized YAML-ready metadata from SKILL.md files.

Updated May 17, 2022
One-click install
npx skills add https://github.com/kanade0404/dotfiles --skill software-design-kanade0404
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-design
Source: https://github.com/kanade0404/dotfiles/tree/main/.opencode/skills/software-design
Command: npx skills add https://github.com/kanade0404/dotfiles --skill software-design-kanade0404

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you inspect a repository, find valid Skill units, and turn each one into normalized metadata that can be indexed and shared.

Core Features & Use Cases

  • Detects root-level SKILL.md files and validates the required frontmatter fields.
  • Summarizes each skill’s purpose, available components, and safety posture into structured output.
  • Useful for repository audits, skill catalogs, and automated skill ingestion pipelines.

Quick Start

Ask the assistant to analyze the repository and generate metadata for every valid Skill unit it finds.

Frequently Asked Questions about software-design

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

FAQPage Schema
How do I detect valid Skill units in a repository and generate normalized metadata?

Repository analysis for skill detection scans directories for root-level SKILL.md files, validates required YAML frontmatter fields, and generates normalized metadata for each valid unit.

What is the process for validating YAML frontmatter during a directory scan?

YAML frontmatter validation checks root-level SKILL.md files for required fields while applying strict component detection and toxicity screening to produce clean, structured metadata.

Can I use repository analysis to build an automated skill ingestion pipeline?

Yes, repository analysis supports automated skill ingestion pipelines by emitting clean, YAML-ready metadata output from validated SKILL.md files for downstream indexing and catalogs.

Does skill detection work with repositories containing optional scripts and references?

Skill detection works with repositories containing optional scripts, references, and assets by specifically identifying valid Skill units defined by root-level SKILL.md files during the directory scan.

What are the limitations of automated toxicity checks during skill metadata generation?

Toxicity checks during skill metadata generation are limited to screening the validated content of root-level SKILL.md files and do not deeply analyze optional scripts or external repository assets.