tech-planner

Identify valid Skill units and generate standardized YAML metadata blocks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Refinex-Space/Refinex-Skills --skill tech-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-planner
Source: https://github.com/Refinex-Space/Refinex-Skills/tree/main/skills/tech-planner
Command: npx skills add https://github.com/Refinex-Space/Refinex-Skills --skill tech-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify valid Skill units within a repository (defined by the mandatory presence of a SKILL.md at the root) and generate structured metadata that enables discovery, validation, and downstream tooling integration.

Core Features & Use Cases

  • Detect Skill units by root SKILL.md presence and required frontmatter (name and description)
  • Produce a consistent YAML metadata block per Skill including fields like tagline, description, request, complexity, category, keywords, dependencies, components, and toxicity_check
  • Output a machine-readable artifact that downstream tooling can index, validate, and surface in UI

Quick Start

Run the discovery to list all valid Skill units and emit their YAML metadata blocks.

Frequently Asked Questions about tech-planner

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

FAQPage Schema
How do I extract YAML frontmatter metadata from repository skill units?

Extract YAML frontmatter metadata by detecting root SKILL.md files and generating standardized blocks containing name, tagline, description, complexity, category, keywords, dependencies, and toxicity_check for valid skill units.

What is skill discovery and how does it validate repository units?

Skill discovery identifies valid repository units by confirming mandatory root SKILL.md presence and required frontmatter fields, then emitting standardized YAML metadata for indexing, validation, and downstream tooling integration.

How to generate machine-readable metadata for repository analysis?

Generate machine-readable metadata by scanning the repository for valid skill units and outputting consistent YAML blocks that downstream tools can index, validate, and surface in user interfaces.

Can I use YAML metadata blocks to flag safety concerns in repository analysis?

Yes, YAML metadata blocks include a toxicity_check field that flags potential safety concerns during repository analysis, ensuring downstream tooling can identify and handle risky content appropriately.

What fields are required in a valid SKILL.md frontmatter for skill discovery?

Valid SKILL.md frontmatter requires name and description fields for skill discovery, while the generated YAML metadata block includes additional fields like tagline, complexity, category, keywords, dependencies, and components.

Does skill discovery work with repositories that have no dependencies?

Yes, skill discovery works with repositories that have no dependencies, as the metadata extraction process detects valid skill units based solely on root SKILL.md presence and required frontmatter fields.