your-skill-name

Translate Skill Units into structured JSON metadata with safety fields.

7|1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/julianobarbosa/claude-code-skills --skill your-skill-name-julianobarbosa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: your-skill-name
Source: https://github.com/julianobarbosa/claude-code-skills/tree/main/templates/skill-template
Command: npx skills add https://github.com/julianobarbosa/claude-code-skills --skill your-skill-name-julianobarbosa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This is a boilerplate Skill template to guide the creation of Claude Skills with a consistent structure.

Core Features & Use Cases

  • Boilerplate structure: Provides a repeatable metadata format.
  • Guidance for new Skills: Helps teams kick off new Skill units quickly.

Quick Start

Use this template to generate a new Skill unit named "example-skill".

Frequently Asked Questions about your-skill-name

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

FAQPage Schema
How do I create a structured metadata template for a Claude Skill?

This template provides a boilerplate structure with consistent metadata format, including request, description, is_toxic, and toxic_reason fields. Use it as a starting point to generate per-skill embeddings and safety metadata for RAG systems, ensuring valid JSON output with required fields for Skill retrieval.

What is the purpose of translating Skill Units into structured metadata?

Translating Skill Units into structured metadata generates decision signatures and safety fields used by RAG systems. This process creates per-skill embeddings that enable accurate retrieval and capability matching when users search for Claude Skills.

Can I use this template to kickstart a new Skill quickly?

Yes. This boilerplate template guides consistent Skill creation by providing a repeatable metadata structure and format. Teams can use it to generate new Skill units rapidly while maintaining required JSON output fields and language constraints.

What metadata fields must my Skill include?

Your Skill must deliver valid JSON with four required fields: request, description, is_toxic, and toxic_reason. These fields support RAG system embeddings and safety classification, enabling proper retrieval and risk assessment.

Why is YAML configuration important for Skill templates?

YAML provides human-readable configuration for Skill documentation and boilerplate structures. Using YAML alongside JSON output ensures both readability during development and structured formatting required by RAG retrieval systems.