Vtex Io Service Runtime
Apply when designing or implementing the runtime structure of a VTEX IO backend app under node/. Covers the Service entrypoint, typed context and state, service.json runtime configuration, and how routes, events, and GraphQL handlers are registered and executed. Use for structuring backend apps, defining runtime boundaries, or fixing execution-model issues in VTEX IO services.
Install
/plugin marketplace add vtex/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vtex/skills --skill vtex-io-service-runtimegit clone --depth 1 https://github.com/vtex/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/exports/opencode/vtex-io-service-runtime ~/.claude/skills/vtex-io-service-runtimePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Service Runtime & Execution Model ## When this skill applies Use this skill when the main decision is how a VTEX IO backend app runs inside the `node` builder: how the `Service` entrypoint is structured, how runtime configuration is declared, and how routes, events, or GraphQL handlers are registered into the service. - Creating a new backend app under `node/` - Structuring `node/index.ts` as the service entrypoint - Defining typed `Context`, `State`, and params contracts for handlers - Configuring `service.json` for timeout, memory, workers, and replicas - Troubleshooting runtime issues caused by service registration or execution model mismatches - Registering GraphQL handlers at the runtime level, while keeping schema and resolver design in a separate skill Do not use this skill for: - deciding the app contract in `manifest.json` - designing custom clients or integration transport layers - detailed HTTP route handler behavior - event-specific business workflows - GraphQL schema or resolver modeling beyond runtime registration ## Decision rules - Treat `node/index.ts` as the runtime composition root of the backend app. - Use the `Service` definition to register runtime surfaces such as routes, events, and GraphQL handlers, not to hold business logic directly. - Keep runtime wiring explicit: context typing, client typing, route registration, and event registration should be visible at the service boundary.
Details
- Skill name
vtex-io-service-runtime- Repository
- vtex/skills
- Path
exports/opencode/vtex-io-service-runtime/SKILL.md- Repo updated
- 14 October 2026
FAQ
What does the Vtex Io Service Runtime skill do?
Apply when designing or implementing the runtime structure of a VTEX IO backend app under node/. Covers the Service entrypoint, typed context and state, service.json runtime configuration, and how routes, events, and GraphQL handlers are registered and executed. Use for structuring backend apps, defining runtime boundaries, or fixing execution-model issues in VTEX IO services.
How do I install the Vtex Io Service Runtime skill?
Claude Code plugin: /plugin marketplace add vtex/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Vtex Io Service Runtime popular?
It lives in vtex/skills, which has 47 GitHub stars and 9 forks.
Related skills
Architecture Well Architected Commerce
47vtex/skills
Apply when scoping, reviewing, or documenting cross-cutting VTEX commerce architecture across storefront, IO, headless, marketplace, payments, or any other VTEX module. Grounds work in the Well-Architected Commerce framework—Technical Foundation (reliability, trust, integrity; security, infrastructure, compliance), Future-proof (innovation, simplicity, efficiency; scalable and adaptable solutions), and Operational Excellence (accuracy, accountability, data-driven improvement; process and customer experience). Routes implementation detail to product tracks (IO caching and paths, Master Data str
Faststore Storefront
47vtex/skills
Core coding rules and workflow for developing VTEX FastStore storefronts. Use when starting any FastStore development task, writing TypeScript/React components, creating section overrides, extending the BFF, or styling. Covers all primary conventions, safety rules, and the development workflow used across every FastStore project.
Headless Bff Architecture
47vtex/skills
Apply when designing or modifying a BFF (Backend-for-Frontend) layer, middleware, or API proxy for a headless VTEX storefront. Covers BFF middleware architecture, public vs private API classification, VtexIdclientAutCookie management, API key protection, and secure request proxying. Use for any headless commerce project that must never expose VTEX_APP_KEY or call private VTEX APIs from the browser.
Build Method
44SamueleBassoli/hermes-fleet-apps
Use when building or designing software. The method.
Vtex Io Service Paths and Cdn
47vtex/skills
Apply when defining service.json routes, choosing public vs segment vs private URL prefixes for VTEX IO services, or setting HTTP cache headers that interact with the VTEX edge and CDN. Covers path patterns, cookie visibility, edge caching behavior, and aligning Cache-Control with data sensitivity. Use for Node or .NET IO backends where request path and response headers determine CDN safety.
Code Generated Video
44SamueleBassoli/hermes-fleet-apps
Use when a short teaser is asked for in the ff-tracking style: every pixel and sound from code.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.