ck:template-skill

Convert SKILL.md frontmatter into a complete Skill Unit metadata YAML.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/droppii/droppii-agents --skill ck-template-skill-droppii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:template-skill
Source: https://github.com/droppii/droppii-agents/tree/main/cursor/skills/template-skill
Command: npx skills add https://github.com/droppii/droppii-agents --skill ck-template-skill-droppii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Skill authors need a consistent starting structure to rapidly define new capabilities without duplicating boilerplate.

Core Features & Use Cases

  • Provides a ready-to-fill frontmatter schema, a placeholder instruction body, and consistent metadata formatting.
  • Supports optional directories (scripts/, references/, assets/) when present to extend functionality.
  • Use Case: Teams rapidly scaffold new skills for internal tooling, experiments, or onboarding.

Quick Start

Create a new skill folder following this template and replace placeholders with your own name, description, and body.

Frequently Asked Questions about ck:template-skill

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

FAQPage Schema
How do I generate a complete Skill Unit metadata entry from SKILL.md frontmatter?

To generate a Skill Unit metadata entry, you convert SKILL.md frontmatter into a complete YAML file by populating required fields and formats, ensuring optional directories like scripts/ or assets/ extend the components field correctly.

What is the best way to scaffold a new skill boilerplate without duplicating structures?

The best way to scaffold new skill boilerplate is using a starter template that provides a ready-to-fill frontmatter schema and placeholder instruction body, allowing teams to rapidly define new capabilities without duplicating structures.

How do optional directories influence the components field in a skill YAML file?

Optional directories influence the components field by extending its functionality; when directories like references/ or scripts/ are present, they populate additional components within the final skill YAML metadata entry.

Can I use this skill template for internal tooling and onboarding experiments?

Yes, you can use this skill template for internal tooling, experiments, or onboarding. It provides a consistent starting structure to rapidly scaffold new skills by replacing placeholders with your own name and description.

What required fields must be populated when converting SKILL.md frontmatter to YAML?

Converting SKILL.md frontmatter to YAML requires populating specific required fields with correct formats. The template clarifies these fields to ensure the final YAML metadata entry is correctly populated for your sample skill.