How do I install the skill?

Run npx skillmds@latest add griddynamics/skill-name-must-equal-the-parent-folder-name-of-skill-md-low in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with ?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

griddynamics (@griddynamics) published this skill. Their other Agent Skills are listed on their SkillMD profile.

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

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.

griddynamics Updated Sep 17, 2026

File contents

[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]>

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

[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]

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]

[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]

[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 ...

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

Practice 1
Practice 2 ...

[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]

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

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

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

[Reference]

</[the_skill_name]>

---name: skill-name-must-equal-the-parent-folder-name-of-skill-md-lowdescription: 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.---[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]>

Frequently asked questions

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

File contents

Related skills

Frequently asked questions

How do I install the <skill name; MUST equal the parent folder name of SKILL.md; lowercase-hyphenated> skill?

What does the <skill name; MUST equal the parent folder name of SKILL.md; lowercase-hyphenated> skill do?

Is <skill name; MUST equal the parent folder name of SKILL.md; lowercase-hyphenated> safe to use?

Which AI agents work with <skill name; MUST equal the parent folder name of SKILL.md; lowercase-hyphenated>?

Is <skill name; MUST equal the parent folder name of SKILL.md; lowercase-hyphenated> free to use?

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