ck:template-skill

Scaffold a new Skill unit with SKILL.md metadata and instruction structure.

Updated May 10, 2026
One-click install
npx skills add https://github.com/dthuy62/kollet-app --skill ck-template-skill-dthuy62
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:template-skill
Source: https://github.com/dthuy62/kollet-app/tree/main/.opencode/skills/template-skill
Command: npx skills add https://github.com/dthuy62/kollet-app --skill ck-template-skill-dthuy62

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a minimal starting point for creating a valid skill directory, so authors can define a reusable skill without building the structure from scratch.

Core Features & Use Cases

  • Skill Scaffold: Supplies a basic SKILL.md layout with frontmatter and a body section ready to customize.
  • Reusable Template: Helps standardize how new skills are authored, documented, and organized.
  • Use Case: A builder can copy this template, replace the placeholder content, and turn it into a production-ready skill for a specific workflow.

Quick Start

Use this skill as the foundation for a new skill and replace the placeholder metadata and instructions with your own workflow-specific content.

Frequently Asked Questions about ck:template-skill

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

FAQPage Schema
How do I scaffold a new skill with YAML frontmatter and markdown?

To scaffold a new skill, copy the template to generate a valid SKILL.md entry point containing required YAML frontmatter with name and description fields, plus a markdown body section ready for customization and operational guidance expansion.

What minimal metadata is needed for a valid SKILL.md file?

A valid SKILL.md file requires YAML frontmatter with name and description attributes, accompanied by a markdown body that can be expanded into operational guidance for the skill's workflow-specific instructions.

Does skill authoring require building the directory structure from scratch?

Skill authoring does not require building the directory structure from scratch because this template provides a minimal starting point with the required metadata and instruction structure, allowing authors to define reusable skills by replacing placeholder content.

What's the best way to standardize how new skills are documented and organized?

Standardize new skill documentation by applying this reusable template to establish a consistent SKILL.md layout with frontmatter and body sections, ensuring authors follow the same metadata and instruction structure across repository templates.

Can I use this skill template for rapid prototyping workflows?

You can use this skill template for rapid prototyping workflows because it scaffolds a new Skill unit with required metadata and instruction structure, enabling quick iteration by replacing placeholder content with workflow-specific operational guidance.