skill-template

Provides a reusable template for authoring new Agent Skills with SKILL.md frontmatter.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill skill-template-lgj-jonathan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-template
Source: https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills/tree/main/context-engineering/template
Command: npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill skill-template-lgj-jonathan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating a new Agent Skill from scratch often leads to inconsistent structure, missing frontmatter, and bloated instruction files. This template standardizes how new skills are authored so they are discoverable and perform well in context engineering workflows. ## Core Features & Use Cases - Standardized SKILL.md Structure: Provides ready-made sections for activation triggers, core concepts, examples, guidelines, and gotchas. - Authoring Best Practices: Embeds guidance on token efficiency, third-person descriptions, and when to move content into references/ files. - Use Case: When adding a new skill to a context engineering collection, copy this template, fill in the frontmatter name and description, and replace each placeholder section with skill-specific content. ## Quick Start Use the skill template to scaffold a new Agent Skill for my context engineering collection.

Frequently Asked Questions about skill-template

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

FAQPage Schema
How do I create a new Agent Skill from a template?

Copy the template directory, rename it, and edit SKILL.md. Fill in the name and description in the YAML frontmatter, then replace each placeholder section with content specific to your skill's domain and activation triggers.

What should a SKILL.md file contain?

A SKILL.md file must contain YAML frontmatter with a name and description, followed by a Markdown body with operational instructions. Recommended sections include when to activate, core concepts, examples, guidelines, and gotchas.

How long should a SKILL.md file be?

Keep the SKILL.md body under 500 lines for optimal performance. Move detailed reference material into separate files inside a references/ directory and link to them from the main file.

Why should skill descriptions be written in third person?

The description is injected into the system prompt for skill discovery, and inconsistent point-of-view causes discovery problems. Write declarative phrases like "Processes Excel files" instead of "I can help you process Excel files."

When should I move content to the references directory?

Move content to references/ when a topic is too detailed for the main body or only needed in specific scenarios. Link to it from SKILL.md so the content loads on demand rather than consuming context on every activation.