cnife-skills-repo

Audit and repair skill repositories by validating SKILL.md metadata and Python compliance.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/CNife/skills --skill cnife-skills-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cnife-skills-repo
Source: https://github.com/CNife/skills/tree/main/utility/cnife-skills-repo
Command: npx skills add https://github.com/CNife/skills --skill cnife-skills-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers keep the CNife skills repository consistent, discoverable, and ready to publish by validating structure, frontmatter, scripts, and documentation.

Core Features & Use Cases

  • Enforces required SKILL.md frontmatter and repository conventions.
  • Defines quality gates for Python scripts, pre-commit hooks, and markdown linting.
  • Supports creating, updating, publishing, and bulk-auditing skills across the repository.
  • Use it when adding a new skill, fixing validation issues, or coordinating a repo-wide audit and repair cycle.

Quick Start

Use this skill to review the repository layout, validate the targeted skill, and tell me what must be fixed before publishing.

Frequently Asked Questions about cnife-skills-repo

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

FAQPage Schema
How do I validate a skills repository for publish readiness?

To validate a skills repository for publish readiness, enforce required SKILL.md frontmatter checks, Python script PEP 723 compliance, and ruff linting to ensure structural consistency before publishing.

What's the best way to audit and repair a skills repository?

The best way to audit and repair a skills repository is by running a bulk validation cycle that checks README-to-directory consistency, frontmatter metadata, and pre-commit hooks to identify and fix structural issues.

How do I check SKILL.md frontmatter when adding a new skill?

Checking SKILL.md frontmatter when adding a new skill requires validating that both the name and description fields are present and correctly formatted to meet the repository's quality gates.

Does this repository auditing workflow support ruff and PEP 723 compliance?

Yes, this repository auditing workflow supports ruff and PEP 723 compliance by applying quality gates that validate Python scripts against these standards during the skill creation and repair process.

Why does my skills repository fail validation before publishing?

Your skills repository fails validation before publishing when SKILL.md frontmatter is missing required fields, Python scripts lack PEP 723 metadata, or README-to-directory consistency checks detect mismatches.

Can I use pre-commit hooks to maintain skills repository consistency?

Yes, you can use pre-commit hooks to maintain skills repository consistency by defining quality gates that automatically enforce markdown linting and ruff compliance during routine repository maintenance.