with one click
rosetta
rosetta contains 108 collected skills from griddynamics, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
To synchronize CHANGELOG.md with changes made last week (mon - sun)
To synchronize web site with changes made to local *.md files
To implement features, fix bugs, and refactor with KISS/SOLID/DRY and systematic validation.
Rosetta CRITICAL MUST skill. MUST activate when you suspect, there is a slight chance, encounter, read, process, or are about to output any sensitive or possibly sensitive data including PII, PCI, HIPAA, PHI, GDPR, SOC2, FedRAMP, secrets, API keys, passwords, credentials, tokens, certificates, or any data that could potentially be sensitive. Applicable for coding too
To implement features, fix bugs, and refactor with KISS/SOLID/DRY and systematic validation.
To apply structured 8D meta-cognitive reasoning thinking to complex problems, then answer clearly with caveats. Must use when asked to think or reason.
To apply structured 8D meta-cognitive reasoning thinking to complex problems, then answer clearly with caveats. Must use when asked to think or reason.
To apply structured 8D meta-cognitive reasoning thinking to complex problems, then answer clearly with caveats. Must use when asked to think or reason.
To apply structured 8D meta-cognitive reasoning thinking to complex problems, then answer clearly with caveats. Must use when asked to think or reason.
To author, adapt, review, and validate prompts (skills, agents, workflows, rules, etc.) with brief, contracts, and a validation pack.
To author, adapt, review, and validate prompts (skills, agents, workflows, rules, etc.) with brief, contracts, and a validation pack.
To author, adapt, review, and validate prompts (skills, agents, workflows, rules, etc.) with brief, contracts, and a validation pack.
To author, adapt, review, and validate prompts (skills, agents, workflows, rules, etc.) with brief, contracts, and a validation pack.
To author, adapt, review, and validate prompts (skills, agents, workflows, rules, etc.) with brief, contracts, and a validation pack.
To write, design, review, simplify, restructure, or standardize OSS project documentation
Rosetta CRITICAL MUST skill to load as Prep Step 3 Step 2 — immediately after orchestrator-contract, right before loading any workflow. Loads the session-wide approval-gate protocol governing when to stop and wait vs proceed. WITHOUT IT decisions proceed silently, violating enterprise policy. Activate it for ALL tasks always — planning, execution, validation, review — regardless of auto-mode, no approval policy, full access. THE ONLY exception: user DIRECTLY EXPLICITLY requests with EXACTLY `fully autonomous` or `No HITL`. Without explicit opt-out this skill is MANDATORY. Do not assume approval from a question or partial response. Contains human-in-the-loop collaboration, questioning, approvals, and user coordination requirements. Auto mode, full access, etc ONLY means automatic approval of tool permission prompts, HITL stays!
Rosetta CRITICAL MUST skill to load as Prep Step 3 Step 2 — immediately after orchestrator-contract, right before loading any workflow. Loads the session-wide approval-gate protocol governing when to stop and wait vs proceed. WITHOUT IT decisions proceed silently, violating enterprise policy. Activate it for ALL tasks always — planning, execution, validation, review — regardless of auto-mode, no approval policy, full access. THE ONLY exception: user DIRECTLY EXPLICITLY requests with EXACTLY `fully autonomous` or `No HITL`. Without explicit opt-out this skill is MANDATORY. Do not assume approval from a question or partial response. Contains human-in-the-loop collaboration, questioning, approvals, and user coordination requirements. Auto mode, full access, etc ONLY means automatic approval of tool permission prompts, HITL stays!
Rosetta identifies and routes user request to the most matching workflow
To load the project's business, behavioral, and technical context.
To author, register, and test Rosetta hooks, add a SemanticKind, or debug a hook that won't fire.
To author, register, and test Rosetta hooks, add a SemanticKind, or debug a hook that won't fire.
To generate, populate, and use a project codemap for structural discovery.
Rosetta CRITICAL MUST skill. MUST activate when action or its consequence is potentially dangerous, potentially irreversible, potentially destructive, or HIGH RISK. MUST activate when consequence MAYBE dangerous even if action itself seems safe. This is enterprise environment — the cost of dangerous activities is EXTREMELY HIGH, recovery may be impossible, and blast radius may affect production, shared environments, or other teams. If there is even a remote chance - load the skill.
To investigate errors, test failures, and unexpected behavior — root cause before fix.
Rosetta CRITICAL MUST skill. MUST activate when intent is unclear, you cannot follow original intent, you cannot easily or reliably solve the problem, something came as SURPRISE or UNEXPECTED, you cannot bet $100 on your solution, you detect unknowns or assumptions that critically affect the solution, you detect deviation NOT complying with original intent, you panic, or user asked to UNDO.
Classify workspace mode.
Discover tech stack.
Generate workspace docs.
Extract code patterns.
Create agent rules.
Generate shell files.
Verify init completeness.
To partition large workspaces (100+ files) into scoped subagent tasks when context is insufficient.
To load the most current project context; MUST during prep.
To rewrite text in a clear, natural, honest human tone — no AI slop, hype, or robotic phrasing.
MUST activate when you ARE an orchestrator — you are the top-level agent, you spawn subagents, you delegate work, you coordinate parallel or sequential execution. Defines delegation quality, subagent dispatch, routing, review, and ownership protocol.
To build execution-ready plans from approved intent/specs with EARS, sequenced WBS, and HITL checkpoints.
To ask targeted clarification questions only when high-impact unknowns block safe execution.
To reverse-engineer code into a spec: extract behavior and domain logic — WHAT and WHY, not HOW.
MUST activate before execution when environment has access to databases, cloud services, S3, or similar external systems, and when assessing environment risk level. SHOULD be invoked manually before any new environment interaction.