cst-naming

Name: cst-naming
Availability: InStock
Author: Captain

Standardize skill IDs and key bindings for CaptainSkillTree projects.

1|Updated Jul 15, 2025

Search Tags:#consistency #guidelines #naming #expert-skill #skill-id #skill-binding

Ready to run

npx skills add https://github.com/KorCaptain/Valheim_Captain_SkillTree --skill cst-naming

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cst-naming
Source: https://github.com/KorCaptain/Valheim_Captain_SkillTree/tree/main/.claude/skills/cst-naming
Command: npx skills add https://github.com/KorCaptain/Valheim_Captain_SkillTree --skill cst-naming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes skill and key-binding naming to ensure consistent IDs, reducing confusion and integration errors across CaptainSkillTree development.

Core Features & Use Cases

Standardized expert skill IDs contain expert (e.g., sword_expert_damage).
General skills follow the {weapon}Step{tier}{name} format (e.g., bow_Step6_critboost).
Root nodes use the {category}_root pattern to organize skill trees.
Enforces step levels from Step1 to Step7 and clear key-binding mappings (R, G, H, Y).

Quick Start

Create a new expert skill ID sword_expert_damage following the {type}expert{attr} convention.

Frequently Asked Questions about cst-naming

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

FAQPage Schema

How do I format skill IDs and key bindings for CaptainSkillTree projects?▼

Format skill IDs for CaptainSkillTree by applying specific naming rules: use the {weapon}_Step{tier}_{name} pattern for general skills, insert _expert_ for expert skills, and apply {category}_root for root nodes. Key bindings map to R, G, H, and Y.

What is the correct naming convention for expert skill IDs?▼

The correct naming convention for expert skill IDs requires inserting _expert_ into the identifier, typically following the {type}_expert_{attr} format like sword_expert_damage, to clearly differentiate expert skills from general ones.

How do I structure root node identifiers in a skill tree?▼

Structure root node identifiers in a skill tree using the {category}_root naming pattern. This convention organizes skill trees by ensuring the base node clearly denotes its category within the YAML frontmatter hierarchy.

What step level range is enforced for skill naming?▼

Skill naming enforces step levels from Step1 to Step7. This range standardizes tier progression within the {weapon}_Step{tier}_{name} format to maintain consistency across general skill identifiers.

Why do I need standardized naming rules for skill IDs?▼

Standardized naming rules for skill IDs reduce confusion and prevent integration errors across CaptainSkillTree development. Consistent identifiers, formats, and binding keys satisfy YAML frontmatter requirements and ensure reliable skill creation.