nozich-agent-skill-authoring

Standardize and verify SKILL.md frontmatter for Nozich Skill units.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/anilcan-kara/nozich-agent --skill nozich-agent-skill-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nozich-agent-skill-authoring
Source: https://github.com/anilcan-kara/nozich-agent/tree/main/skills/software-development/nozich-agent-skill-authoring
Command: npx skills add https://github.com/anilcan-kara/nozich-agent --skill nozich-agent-skill-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating and maintaining in-repo SKILL.md with consistent frontmatter and validation to ensure skill discovery and quality controls across Nozich Agent skills.

Core Features & Use Cases

  • Standard frontmatter blueprint and required fields (name, description, version, author, license, metadata).
  • In-repo vs user-local SKILL.md: guidance on placement and lifecycle.
  • Validator-driven enforcement via tools/skill_manager_tool.py to ensure correct structure, field presence, and size limits.

Quick Start

Create or update the in-repo SKILL.md at skills/software-development/nozich-agent-skill-authoring/SKILL.md following the frontmatter and structure guidelines.

Frequently Asked Questions about nozich-agent-skill-authoring

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

FAQPage Schema
How do I validate in-repo SKILL.md frontmatter for Nozich Agent?

To validate in-repo SKILL.md frontmatter, apply the skill validator to check required fields like name and description, ensure optional metadata is correct, and verify the Markdown body is non-empty and under size limits.

What is the correct directory structure for authoring in-repo skills?

The correct directory structure for authoring in-repo skills requires placing SKILL.md files under skills/<category>/<name>/, with two allowed sibling directories for supporting content to ensure consistent discovery.

Does SKILL.md frontmatter require specific fields for Nozich Agent skill discovery?

SKILL.md frontmatter requires name and description fields for Nozich Agent skill discovery. Optional metadata includes version, author, and license to standardize validation across the repository.

What's the best way to standardize SKILL.md files across a repository?

The best way to standardize SKILL.md files is using validator-driven enforcement via the skill manager tool to check frontmatter field presence, structural correctness, and file size limits for consistent quality control.

Why does my in-repo SKILL.md fail validation during skill discovery?

In-repo SKILL.md validation fails when required frontmatter fields like name or description are missing, the Markdown body is empty, or the entire file exceeds the specified size limits enforced by the validator.

Can I use user-local SKILL.md instead of in-repo SKILL.md for Nozich Agent?

You can use user-local or in-repo SKILL.md depending on your lifecycle needs. In-repo files under skills/<category>/<name>/ ensure repository-wide discovery and standardized validation, while user-local files serve individual workflows.