touying-author

Generate structured metadata for Skill units from repository content.

Updated May 29, 2026
One-click install
npx skills add https://github.com/TurkeyC/Dotfiles --skill touying-author-turkeyc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: touying-author
Source: https://github.com/TurkeyC/Dotfiles/tree/main/private_dot_copilot/skills/touying-author
Command: npx skills add https://github.com/TurkeyC/Dotfiles --skill touying-author-turkeyc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates structured metadata for Skill units by validating the presence and content of SKILL.md at Skill roots and by detecting optional resources directories.

Core Features & Use Cases

  • Detects valid Skill units by ensuring SKILL.md exists with mandatory name/description fields.
  • Detects optional directories (scripts/, references/, assets/) and records their presence as components.
  • Produces a metadata payload including dependencies, components, and toxicity_check for repository tooling.

Quick Start

Scan the repository to generate and validate Skill unit metadata for discovery and tooling.

Frequently Asked Questions about touying-author

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

FAQPage Schema
How do I generate structured metadata for Skill units from a repository?

Generate structured metadata by validating SKILL.md frontmatter for mandatory name and description fields, detecting optional directories, and compiling dependencies for repository tooling.

What is the process to validate Skill units and ensure they have mandatory metadata?

Validating Skill units requires checking for the presence of SKILL.md at the root and ensuring it contains mandatory name and description fields within its frontmatter.

How are dependencies and components like scripts and assets detected during a repository audit?

Dependencies and components are detected by scanning the repository structure to identify optional resources directories like scripts, references, and assets, recording their presence in the metadata payload.

Does extracting Skill metadata require any specific dependencies or external components?

No external dependencies or components are required to extract Skill metadata, as the process relies on scanning internal repository files and directory structures directly.

Can I use this metadata extraction approach to support dependency auditing across my codebase?

Yes, you can apply this metadata extraction across your codebase to support dependency auditing by compiling dependencies and components into a structured metadata payload for tooling.