имя-скилла

Provides a Markdown template for authoring SKILL.md files with frontmatter and structured sections.

Updated Apr 27, 2024
One-click install
npx skills add https://github.com/IgorGribowsky/rts-sandbox --skill skill-igorgribowsky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: имя-скилла
Source: https://github.com/IgorGribowsky/rts-sandbox/tree/main/rts-sandbox-src/.claude/templates
Command: npx skills add https://github.com/IgorGribowsky/rts-sandbox --skill skill-igorgribowsky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Standardizing how new agent skills are authored is difficult when every contributor invents their own format. This template defines a fixed SKILL.md structure with YAML frontmatter (name, description) and prescribed body sections so every skill in the project is discoverable and consistent. ## Core Features & Use Cases - Skill Authoring Template: Supplies a ready-to-copy SKILL.md skeleton with trigger-based description guidance, ordered work steps, pitfalls section, and fact-based verification checklist. - Companion Document Templates: Ships alongside templates for tasks, mechanics, milestones, handoffs, and open questions, giving a complete documentation system for an AI-assisted game development workflow. - Use Case: When adding a new capability to the agent, copy the skill template into .claude/skills/<name>/SKILL.md, fill in the trigger-oriented description and numbered procedure, and the skill becomes discoverable by the agent. ## Quick Start Copy the skill template into a new folder under .claude/skills and fill in the name, description, work steps, and pitfalls sections for the new capability.

Frequently Asked Questions about имя-скилла

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

FAQPage Schema
How do I create a new agent skill with a SKILL.md file?

Create a folder under .claude/skills named after the skill and place a single SKILL.md inside it. Copy the template, fill in the name and a trigger-based description, then write the ordered work steps, pitfalls, and verification sections.

What should a skill description contain for discoverability?

The description should state when the skill is needed using triggers, such as "when editing prefabs" or "when building a screen", rather than describing the topic. Skills are selected by description without reading the full file.

Can a skill include extra files like Specific.md or Journal.md?

No. The template explicitly forbids companion files: project specifics live in docs/ and the journal lives inside the task file. A skill is exactly one SKILL.md file to avoid extra reads on every launch.

What is the difference between a skill and process documentation?

A skill holds domain knowledge loaded on demand, while process lives in commands, rules live in CLAUDE.md, and mechanics live in scripts. If a new skill turns out to be process-oriented, the template says it should not exist.

When should this skill template not be used?

Do not use it for general task workflow or approval rules, since those belong in CLAUDE.md and must not be duplicated. It is only for self-contained subject-matter knowledge triggered by specific work types.