Sap API Style
secondsky/sap-skills
This skill provides comprehensive guidance for documenting SAP APIs following the SAP API Style Guide standards.
Workflow for converting, modernizing, upgrading, or re-architecting code (e.g.
Install Modernization Flow
$ npx skills add griddynamics/rosetta --skill modernization-flow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install griddynamics/rosetta modernization-flow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/griddynamics/rosetta.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/core-antigravity/skills/modernization-flow .claude/skills/modernization-flow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "modernization-flow" agent skill from https://github.com/griddynamics/rosetta/tree/main/plugins/core-antigravity/skills/modernization-flow into .claude/skills/modernization-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "modernization-flow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/griddynamics/rosetta/tree/main/plugins/core-antigravity/skills/modernization-flowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add griddynamics/rosetta --skill modernization-flow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install griddynamics/rosetta modernization-flow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/griddynamics/rosetta.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/core-antigravity/skills/modernization-flow .agents/skills/modernization-flow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "modernization-flow" agent skill from https://github.com/griddynamics/rosetta/tree/main/plugins/core-antigravity/skills/modernization-flow into .agents/skills/modernization-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "modernization-flow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add griddynamics/rosetta --skill modernization-flow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install griddynamics/rosetta modernization-flow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/griddynamics/rosetta.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/core-antigravity/skills/modernization-flow .cursor/skills/modernization-flow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "modernization-flow" agent skill from https://github.com/griddynamics/rosetta/tree/main/plugins/core-antigravity/skills/modernization-flow into .cursor/skills/modernization-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "modernization-flow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/griddynamics/rosetta.git --path plugins/core-antigravity/skills/modernization-flow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add griddynamics/rosetta --skill modernization-flow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install griddynamics/rosetta modernization-flow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/griddynamics/rosetta.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/core-antigravity/skills/modernization-flow .gemini/skills/modernization-flow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "modernization-flow" agent skill from https://github.com/griddynamics/rosetta/tree/main/plugins/core-antigravity/skills/modernization-flow into .gemini/skills/modernization-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "modernization-flow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install griddynamics/rosetta modernization-flowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add griddynamics/rosetta --skill modernization-flow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/griddynamics/rosetta.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/core-antigravity/skills/modernization-flow .github/skills/modernization-flow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "modernization-flow" agent skill from https://github.com/griddynamics/rosetta/tree/main/plugins/core-antigravity/skills/modernization-flow into .github/skills/modernization-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "modernization-flow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add griddynamics/rosetta --skill modernization-flow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install griddynamics/rosetta modernization-flow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/griddynamics/rosetta.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/core-antigravity/skills/modernization-flow .opencode/skills/modernization-flow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "modernization-flow" agent skill from https://github.com/griddynamics/rosetta/tree/main/plugins/core-antigravity/skills/modernization-flow into .opencode/skills/modernization-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "modernization-flow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
modernization-flow- GitHub stars
- 353
- Token cost
- ~1.7k tokens
- SKILL.md length
- 770 words
- Files
- 9
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Workflow for converting, modernizing, upgrading, or re-architecting code (e.g.
- Works in 3 steps: All Rosetta prep steps MUST be FULLY… → USE SKILL load-project-context,… → MUST ALWAYS use todo tasks ledger, ASAP.…
- Tasks that involve Legacy modernization
- SKILL.md covers Context, Modernization Flow - Phase…, State File Format and Important Notes
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Modernization Flow is an agent skill from griddynamics/rosetta. Workflow for converting, modernizing, upgrading, or re-architecting code (e.g. C++→Java, monolith→microservices), etc.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files (for example `phases/modernization-flow-analysis.md`, `phases/modernization-flow-crossproject.md` and `phases/modernization-flow-grouping.md`).
It sits in Backend & APIs, covering Legacy modernization and Microservices. It works with C++ and Java. The repository describes itself as: An instruction layer for AI coding agent. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Legacy modernization
- Tasks that involve Microservices
Example prompts
- “/modernization-flow”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- All Rosetta prep steps MUST be FULLY completed
- USE SKILL load-project-context, orchestration, hitl
- MUST ALWAYS use todo tasks ledger, ASAP. Phases are sequential. Independent tasks can run in parallel.
What it can do on your machine
Read from SKILL.md and the folder at commit 5441232. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Modernization Flow loads about 1.7k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 770 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from griddynamics/rosetta at commit 5441232, republished under its Apache-2.0 licence (© griddynamics). 770 words, ~1,713 tokens.
Download SKILL.mdSave it as
.claude/skills/modernization-flow/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- modernization-flow
- description
- Workflow for converting, modernizing, upgrading, or re-architecting code (e.g. C++→Java, monolith→microservices), etc.
Modernization Flow - Execute Phases Sequentially
Context
This modernization process is designed to systematically analyze, specify, and implement code modernization/migration projects. The process is divided into phases that MUST be executed one-by-one.
Critical Requirements
- ONE PHASE AT A TIME: Read one phase file, execute it completely, update state file, then move to next phase.
- DO NOT SKIP PHASES: Each phase builds on the previous one.
- STATE TRACKING: After each phase, update
agents/modernization-flow-state.mdwith completion status, keep this document concise. - USER CONFIRMATION: Wait for user confirmation before proceeding to next phase.
- Make sure to have todo tasks for each phase! Do not skip phases!
- REMEMBER Do not put decisions/recommendations/suggestions/implementation code for the next phases in the output documents! The decisions are made at phase 6 and review at phase 7 AFTER full analysis. Respect that.
- MUST Create and update files that ARE EXPLICITLY stated here, ASK for permission to create any other file!
- MUST use grep/search on large files to read "table of contents" and then use line ranges to read what is needed.
- MUST use only applicable phases according to the target of the modernization (acquire user approval first and store it in state), as those phases are for multi-project cross-tech modernization. Do not take shortcuts within the phase!
- Prioritize ACCURACY over SPEED!
- THIS is very large workflow: MUST use best matching available separate subagents for each phase, top level agent is orchestrator, orchestrator must be smart with reading/writing files (avoid, fallback to grep and reading line-ranges, as those are very large)
- Phase subagents must contain additionally: "MUST APPLY PHASE <phase.md> — FULLY EXECUTE ALL STEPS", goal, context, original user request, inputs, expected outputs, and summary in the format useful for orchestrator, subagents must be informed they are used as subagents.
User Customizations
- If user did not specify any preferences perform all steps except optional.
- User CAN customize and ask only for specific steps OR steps could have been done already OR towards specific goal OR for specific case, in this case LISTEN and ADOPT to the user.
- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use
Phase 2andPhase 6, unless you discover dependencies and project becomes bigger. - If there is no need to rewrite code (example: upgrade .NET 6 to .NET 8), then take original and target code specs LIGHTLY, only document WHAT IS NECESSARY TO CHANGE (example: new way to use app builder).
Show full SKILL.md (358 more words)Show less
Modernization Flow - Phase Overview
Phase 0: Prerequisites
- All Rosetta prep steps MUST be FULLY completed
- USE SKILL
load-project-context,orchestration,hitl - MUST ALWAYS use todo tasks ledger, ASAP. Phases are sequential. Independent tasks can run in parallel.
Phase 1: Existing Library Analysis for Reusing in Target State [modernization-flow-reuse.md]
- APPLY SKILL FILE
phases/modernization-flow-reuse.md - Execute phase instructions
- Update
agents/modernization-flow-state.mdwith brief state - Validate by listing files in respective folders
Phase 2: Old Code Analysis, Generating Original Specs [modernization-flow-analysis.md]
- APPLY SKILL FILE
phases/modernization-flow-analysis.md - Execute phase instructions
- Update
agents/modernization-flow-state.mdwith brief state - Validate by listing files in respective folders
Phase 3: Pre-Modernization Test Coverage (OPTIONAL) [modernization-flow-testing.md] NOTE: Execute this phase if user explicitly approves it
- APPLY SKILL FILE
phases/modernization-flow-testing.md - Execute phase instructions
- Update
agents/modernization-flow-state.mdwith brief state - Validate by listing files in respective folders
Phase 4: Class Group Analysis [modernization-flow-grouping.md]
- APPLY SKILL FILE
phases/modernization-flow-grouping.md - Execute phase instructions
- Update
agents/modernization-flow-state.mdwith brief state - Validate by listing files in respective folders
Phase 5: Cross-Project Analysis [modernization-flow-crossproject.md]
- APPLY SKILL FILE
phases/modernization-flow-crossproject.md - Execute phase instructions
- Update
agents/modernization-flow-state.mdwith brief state - Validate by listing files in respective folders
Phase 6: Implementation Mapping, Generating Target Specs [modernization-flow-mapping.md]
- APPLY SKILL FILE
phases/modernization-flow-mapping.md - Execute phase instructions
- Update
agents/modernization-flow-state.mdwith brief state - Validate by listing files in respective folders
Phase 7: Final Review [modernization-flow-review.md]
- APPLY SKILL FILE
phases/modernization-flow-review.md - Execute phase instructions
- Update
agents/modernization-flow-state.mdwith brief state - Validate by listing files in respective folders
Phase 8: Implementation [modernization-flow-implement.md]
- APPLY SKILL FILE
phases/modernization-flow-implement.md - Get explicit human approval
- Follow approved target specs
- Implement one project at-a-time
- Maintain backward compatibility
- Write comprehensive tests
- Achieve 80% code coverage
State File Format
Create/update agents/modernization-flow-state.md briefly after each phase using sample:
# Modernization State
**Last Updated**: [Date and Time]
**Current Status**: [Phase Number or COMPLETE]
**Project**: [Project/Feature Name]
## Phase Completion Status
- [x] Phase 1: Existing Library Analysis - Completed [Date]
- [ ] Phase 2: Old Code Analysis - Not Started
- [ ] Phase 3: Test Coverage (OPTIONAL) - Not Started / Skipped
- [ ] Phase 4: Class Group Analysis - Not Started
- [ ] Phase 5: Cross-Project Analysis - Not Started
- [ ] Phase 6: Implementation Mapping - Not Started
- [ ] Phase 7: Final Review - Not Started
- [ ] Implementation Phase - Not Started
## Phase Details
### Phase 1
- Completed: [Date/Time]
- Files Created: [List files]
- Projects Analyzed: [List projects]
- Notes: [Any relevant notes]
[Add similar sections for each completed phase]Important Notes
- Sequential Execution Required: Phases build on each other and must be done in order
- No Assumptions: If information is missing, track it in spec files
- User Guidance: Ask questions to resolve critical unknowns
- Evidence-Based: All findings must reference actual code
- Get Approval: Implementation phase requires explicit human approval
© griddynamics, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 8 other files in plugins/core-antigravity/skills/modernization-flow of griddynamics/rosetta.
- SKILL.md
- phases/modernization-flow-analysis.md
- phases/modernization-flow-crossproject.md
- phases/modernization-flow-grouping.md
- phases/modernization-flow-implement.md
- phases/modernization-flow-mapping.md
- phases/modernization-flow-reuse.md
- phases/modernization-flow-review.md
- phases/modernization-flow-testing.md
Open the folder on GitHubat commit 5441232
Compare with similar skills
Modernization Flow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Modernization Flow this skillgriddynamics/rosetta | 353 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Sap API Stylesecondsky/sap-skills | 460 | — | ~4.4k | Automated safety check: Pass | GPL-3.0 | |
| Project Workflow Analysis Blueprint Generatorgithub/awesome-copilot | 40k | 1 repos | ~2.7k | Automated safety check: Pass | MIT | |
| Developing Softwaretelagod/code-abyss | 244 | — | ~410 | Automated safety check: Pass | MIT | |
| Dr Jskilljdubois/dr-jskill | 342 | — | ~4.6k | Automated safety check: Notes | Apache-2.0 | |
| Rsid SDKrealsenseai/RealSenseID | 122 | — | ~4.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Project Workflow Analysis Blueprint Generator
github/awesome-copilot
Comprehensive technology-agnostic prompt generator for documenting end-to-end application workflows.
Developing Software
telagod/code-abyss
Software development knowledge reference covering Python, Go, Rust, TypeScript, Java, C++, and Shell.
Dr Jskill
jdubois/dr-jskill
Creates Java + Spring Boot projects: Web applications, full-stack apps with Vue.js or Angular or React or vanilla JS, PostgreSQL, REST APIs, and Docker.
Rsid SDK
realsenseai/RealSenseID
RealSenseID face authentication SDK reference. An agent skill from realsenseai/RealSenseID.
- Official
Temporal Developer
temporalio/skill-temporal-developer
Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Ruby, and Rust.
More from griddynamics/rosetta
All 12 skills in this repoCollect GitHub Stats
griddynamics/rosetta
Collect GitHub repo health/usage stats into merged JSON. An agent skill from griddynamics/rosetta.
External Lib Flow
griddynamics/rosetta
Workflow for onboarding an external private library so AI can use it without source access.
Specflow Use
griddynamics/rosetta
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
Harness
griddynamics/rosetta
To build an AI harness: run, observe, validate, automate repeated work faster — CLI/MCP actions, devcontainers, skills, subagents, hooks, pipelines, automations.
Coding Agents Farm
griddynamics/rosetta
To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.
Coding Agents Hooks Authoring
griddynamics/rosetta
To author, register, and test Rosetta hooks, add a SemanticKind, or debug a hook that won't fire.
Related
Categories
Questions about Modernization Flow
What does Modernization Flow do?
Workflow for converting, modernizing, upgrading, or re-architecting code (e.g. Modernization Flow is an agent skill from griddynamics/rosetta.g.
When should I use Modernization Flow?
Modernization Flow fits situations like: tasks that involve Legacy modernization; tasks that involve Microservices.
How do I install Modernization Flow in Claude Code?
Run `npx skills add griddynamics/rosetta --skill modernization-flow -a claude-code`. Or copy the skill folder (plugins/core-antigravity/skills/modernization-flow in griddynamics/rosetta) into .claude/skills/modernization-flow in your project. Claude Code loads it when a task matches its description.
How do I install Modernization Flow in Codex?
Run `npx skills add griddynamics/rosetta --skill modernization-flow -a codex`. Or copy the skill folder (plugins/core-antigravity/skills/modernization-flow in griddynamics/rosetta) into .agents/skills/modernization-flow in your project. Codex loads it when a task matches its description.
Can I use Modernization Flow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add griddynamics/rosetta --skill modernization-flow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/modernization-flow, .gemini/skills/modernization-flow, .github/skills/modernization-flow and .opencode/skills/modernization-flow in your project.
What does Modernization Flow need to run?
SKILL.md names no scripts, command-line tools or credentials: Modernization Flow is instructions for the agent only.
Does Modernization Flow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Modernization Flow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Modernization Flow use?
Modernization Flow is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Modernization Flow use?
About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Modernization Flow?
Skills that share tags, products or a category with Modernization Flow: Sap API Style (secondsky/sap-skills, 460 stars), Project Workflow Analysis Blueprint Generator (github/awesome-copilot, 40k stars), Developing Software (telagod/code-abyss, 244 stars) and Dr Jskill (jdubois/dr-jskill, 342 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Modernization Flow?
griddynamics (a GitHub organization) maintains it in griddynamics/rosetta, which has 353 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on September 29, 2026.
Source: griddynamics/rosetta on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.