# <skill name; MUST equal the parent folder name of SKILL.md; lowercase-hyphenated>

> GENERIC form: To <verb> <what it does + when/why; dense keywords>. CRITICAL/guardrail form: 'Rosetta CRITICAL MUST skill. MUST activate when <condition>'. Budget: all skills share ~1K tokens — keep ≤ ~25 tokens and dense; over-long is ignored the same as terse, keyword-dense descriptions trigger best. EXCEPTION: disable-model-invocation:true => this description is actually user friendly.

- Skill: `griddynamics/skill-name-must-equal-the-parent-folder-name-of-skill-md-low` (Agent Skill, multi-file: 8 files)
- Install (CLI): `npx skillmds@latest add griddynamics/skill-name-must-equal-the-parent-folder-name-of-skill-md-low`
- Raw SKILL.md: https://api.skillmd.com/api/skills/griddynamics/skill-name-must-equal-the-parent-folder-name-of-skill-md-low/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: griddynamics (https://skillmd.com/u/griddynamics)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/griddynamics/skill-name-must-equal-the-parent-folder-name-of-skill-md-low

---


[ONLY FOR TEMPLATE EXECUTOR: imperative bullet points, shorter lines, distinguish references to repository files vs instructions; skill/subagent names will be in context already, so just reference it. the rest of instruction folder files: rules/templates/workflows/assets/subfolders of skill/etc must be loaded via the typed aliases (USE SKILL/FLOW, INVOKE SUBAGENT, APPLY PHASE, READ|APPLY RULE|TEMPLATE|SKILL FILE, LIST) to be used]

<[the_skill_name]>

<role>

[Optional, Define role with specialization of the agent executing this skill, use expressive language, seniority, brilliant and short]

</role>

<when_to_use_skill>

[KEEP THIS VERY SHORT. Define a problem and retrospectively introspectively validation proof that this prompt actually solves the problem, explain the scenarios, conditions, or situations where this skill should be used]

</when_to_use_skill>

<core_concepts>

- All Rosetta prep steps MUST be FULLY completed, load-context skill loaded and fully executed

[Optional, KEEP THIS VERY SHORT, Describe the fundamental concepts, principles, definitions and explanations required to properly execute the skill]

</core_concepts>

<process>

[Optional, KEEP THIS VERY SHORT, Every line is an ACTION (imperative verb) or a GATE (condition), No explaining what the agent already knows how to do, Define contracts/structures ONCE, DRY, No vague qualifiers, No patronizing, No tautology, No filler words]

</process>


<validation_checklist>

[Optional, KEEP THIS VERY SHORT, do NOT repeat the rest of the prompt, it must not just restate the same: prompt tells what to do, instead it should be proof-oriented — observable evidence that the output is correct, proof that work was done correctly]

- Checkpoint 1
- Checkpoint 2
...

</validation_checklist>

<best_practices>

[Optional, KEEP THIS VERY SHORT, do NOT repeat, List recommended practices, tips, and guidelines for effectively using this skill]

- Practice 1
- Practice 2
...

</best_practices>

<pitfalls>

[Optional section, KEEP THIS VERY SHORT, do NOT repeat, provide unexpected mistakes, edge cases, caveats, unusual, errors, gotchas, traps, non-obvious patterns or issues to take into account or avoid]

</pitfalls>

<resources>

[Optional, List helpful resources, references, or related materials, do not duplicate]

- [Type of object referenced] [Reference] [Description, optional]
...

</resources>

<templates>

[Optional, Define what this skill produces and provide templates or examples of the output format]

- [Reference]

</templates>

</[the_skill_name]>