skill-authoring

Translate verification rules into Claude Code skills with SKILL.md structure.

13|4|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/memect/kc --skill skill-authoring-memect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-authoring
Source: https://github.com/memect/kc/tree/main/template/skills/zh/skill-authoring
Command: npx skills add https://github.com/memect/kc --skill skill-authoring-memect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate a verification rule into a self-contained Claude Code skill with a clear frontmatter, SKILL.md body, and optional assets.

Core Features & Use Cases

  • Create a standardized skill folder per rule, with SKILL.md describing the rule and its workflow.
  • Use the skill-creator tooling to generate and iterate on per-rule skills, along with assets/scripts/references for testing.
  • Facilitate consistent documentation and auditing across the skill development lifecycle.

Quick Start

Scaffold a new per-rule skill folder and run the bundled skill-creator workflow to generate SKILL.md and supporting assets.

Frequently Asked Questions about skill-authoring

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

FAQPage Schema
How do I turn a verification rule into a Claude Code skill?

You can create a Claude Code skill by scaffolding a standardized folder per rule, generating a SKILL.md file with frontmatter, and adding optional assets like scripts and references for testing and iteration.

What is the skill-format spec for structuring SKILL.md files?

The skill-format spec structures SKILL.md files by requiring clear frontmatter, a body describing the rule and workflow, and optional bundled assets. This per-rule granularity ensures consistent documentation and supports the skill-creator workflow.

How do I structure scripts and references for Claude Code skill testing?

Structure scripts and references by placing them as optional assets within the standardized skill folder. The skill-creator workflow generates these supporting components alongside SKILL.md to facilitate per-rule testing and iteration.

Do I need the skill-creator workflow to generate per-rule skills?

You do not need the skill-creator workflow manually, but it is bundled to scaffold and iterate on per-rule skills automatically. It generates the SKILL.md body and supporting assets to ensure consistent documentation across the lifecycle.

When should I create a separate skill folder for each verification rule?

You should create a separate skill folder for each verification rule to maintain per-rule granularity. This approach ensures self-contained skills with dedicated SKILL.md files, making auditing, testing, and iteration consistent across the lifecycle.