my-skill

Provides templates for authoring Claude Code skills, subagents, commands, rules, and settings.

10|3|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill my-skill-cynthia1070711
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: my-skill
Source: https://github.com/Cynthia1070711/PHYCOOL_Tools/tree/main/config-templates/claude/skills/cc-config-author/assets
Command: npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill my-skill-cynthia1070711

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Creating Claude Code configuration files (skills, subagents, slash commands, path-scoped rules, settings.json) requires knowing exact frontmatter fields, token budgets, naming rules, and platform pitfalls. This template pack gives you copy-ready starting points with the constraints documented inline, so new configuration files follow best practices from the start. ## Core Features & Use Cases - Skill template: A SKILL.md skeleton with frontmatter rules (name format, description style, 300/500-line body limits) and sections for triggers, steps, references, and negative constraints. - Subagent template: An agent definition covering model selection, tool scoping, explicit skill preloading, output format, and hand-back conditions. - Command, rule, and settings templates: A slash command with argument substitution examples, a path-scoped rule file, and a full settings.json with permissions, environment variables, and PreToolUse/PostToolUse/Stop/SessionStart hooks. - Use Case: When adding a new skill to a Claude Code project, copy the skill template into .claude/skills/<name>/, fill in the trigger scenarios and steps, and the result already complies with naming, length, and structure conventions. ## Quick Start Copy the skill template from the assets directory into .claude/skills/ under a new name and fill in the trigger scenarios and core steps for your task.

Frequently Asked Questions about my-skill

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

FAQPage Schema
How do I create a new Claude Code skill?

Copy the skill template into .claude/skills/<your-skill-name>/ and fill in the frontmatter and body. The name must be lowercase with hyphens, under 64 characters, and the description should state what the skill does plus when it triggers.

How do I write a Claude Code subagent definition?

Copy the subagent template to .claude/agents/<your-agent>.md and define its role, workflow, and output format. Subagents do not inherit parent skills or hooks, so required skills must be listed explicitly in the frontmatter.

What are the naming rules for Claude Code skills?

Skill names must be lowercase with hyphens, at most 64 characters, and cannot contain reserved words like claude, anthropic, or system. The description should be third person, under 1024 characters, and include trigger phrases.

Do path-scoped rules in Claude Code trigger on file writes?

No. Rules with paths frontmatter only load when files are read, not when the Write tool creates them. File creation constraints need a PostToolUse hook as a fallback enforcement mechanism.

What is the recommended length for a SKILL.md file?

The soft limit is 300 lines and the hard limit is 500 lines. Content beyond that should be split into files under a references/ directory and loaded on demand via progressive disclosure.