TEMPLATE-RENAME-ME

Create a standardized Claude Code skill scaffold with SKILL.md and manifest.yaml.

8|Updated May 13, 2026
One-click install
npx skills add https://github.com/byteplus-sa/polym --skill template-rename-me
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: TEMPLATE-RENAME-ME
Source: https://github.com/byteplus-sa/polym/tree/main/skills/_template
Command: npx skills add https://github.com/byteplus-sa/polym --skill template-rename-me

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill scaffold helps contributors create a correctly structured, discoverable skill by providing required manifests, entry-point instructions, and validation smoke tests.

Core Features & Use Cases

  • Standardized Skill entry point: Defines the skill name and description in SKILL.md frontmatter so it can be discovered and routed reliably.
  • Installation & operational guidance template: Includes sections for when to use the skill, prerequisites, quickstart, lazy-loaded references, and an IO contract that matches manifest.yaml.
  • Contribution readiness: Provides a CHANGELOG and a smoke test to ensure the skill directory has the required files and frontmatter formatting.

Quick Start

Replace this entire template with your skill content by updating SKILL.md and manifest.yaml to match your skill name, description, IO contract, and triggers.

Frequently Asked Questions about TEMPLATE-RENAME-ME

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

FAQPage Schema
How do I scaffold a new Claude Code skill with the correct manifest and frontmatter?

Standardized skill entry points require a root SKILL.md with YAML frontmatter for name and description, plus a matching manifest.yaml specifying version, stage, owners, and io_contract to ensure reliable discovery and routing.

What metadata is required in manifest.yaml for skill routing and versioning?

Manifest.yaml metadata for skill routing and versioning requires fields for name, version, stage, owners, and io_contract. These fields ensure the skill is correctly staged, owned, and routed based on its defined triggers.

Can I validate my skill directory structure and frontmatter formatting before publishing?

You can validate your skill directory structure and frontmatter formatting by running the included smoke test, which checks that all required files and metadata fields are present and correctly formatted for contribution readiness.

What is an IO contract and why do I need one for a Claude Code skill?

An IO contract defines the input and output behavior for a skill, required in manifest.yaml to establish a consistent operational boundary and ensure the skill integrates reliably with the routing system.

Does a standardized skill scaffold include operational guidance and prerequisites?

A standardized skill scaffold includes installation and operational guidance templates, providing sections for when to use the skill, prerequisites, quickstart instructions, and lazy-loaded references for contributors.