cst-workflow

Register localization keys and validate CaptainSkillTree skills before build.

1|Updated Jul 15, 2025
One-click install
npx skills add https://github.com/KorCaptain/Valheim_Captain_SkillTree --skill cst-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cst-workflow
Source: https://github.com/KorCaptain/Valheim_Captain_SkillTree/tree/main/.claude/skills/cst-workflow
Command: npx skills add https://github.com/KorCaptain/Valheim_Captain_SkillTree --skill cst-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines starting or modifying a skill by providing a repeatable development workflow that aligns localization, configuration, and validation.

Core Features & Use Cases

  • Ensures a consistent, end-to-end process: register localization keys, implement effects, update tooltips, and translate configurations.
  • Provides built-in validation steps (e.g., pre-build localization checks) and references to development guidelines to reduce errors.
  • Use Case: A team adds a new skill and executes a release-ready workflow from creation to verification.

Quick Start

Register localization keys first, then follow the documented development workflow from configuration to validation and run the pre-build localization validation script.

Frequently Asked Questions about cst-workflow

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

FAQPage Schema
What is a repeatable skill development workflow for localization and configuration?

A repeatable skill development workflow aligns localization key registration, configuration updates, and pre-build validation to ensure a consistent, end-to-end process from creation to verification. It reduces errors by providing built-in validation steps and development guideline references.

How do I validate localization keys before building a skill?

To validate localization keys before building, run the pre-build localization validation script provided by the workflow. This step checks that all registered keys and translated configurations are correctly aligned, reducing errors before the final verification stage.

What are the requirements for skill configuration and SKILL.md frontmatter?

The skill configuration requires the SKILL.md frontmatter to include a name and description. Optionally, you can rely on scripts, references, and assets directories within the skill structure to support the development workflow.

Can I use this workflow to modify existing skills, or is it only for new skill creation?

You can use this workflow for both modifying existing skills and creating new ones. It provides a repeatable development process that covers updating tooltips, translating configurations, and running validation steps regardless of whether the skill is new or established.

What steps are involved in an end-to-end skill development workflow?

The end-to-end skill development workflow involves registering localization keys first, then implementing effects, updating tooltips, translating configurations, and finally running a pre-build validation script to verify the release-ready output.

Why does my skill development workflow need built-in validation steps?

Built-in validation steps are needed in a skill development workflow to catch localization and configuration errors early. Running a pre-build validation script ensures that all keys are registered and translated correctly before final verification.