Vtex Io Rbac
Apply when controlling access to VTEX IO app resources using role-based or resource-based policies. Covers policies.json for role-based access control, service.json policies for resource-based access, VRN syntax for principals, the difference between app-to-app and user/integration access, and GraphQL @auth directives. Use when deciding how to secure routes and restrict which apps, users, or integrations can access your endpoints.
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-rbacgit clone --depth 1 https://github.com/vtex/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/exports/opencode/vtex-io-rbac ~/.claude/skills/vtex-io-rbacPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# VTEX IO access control (RBAC) ## When this skill applies Use this skill when you need to **control who can access** your VTEX IO app's routes and resources: - Deciding between **role-based** (`policies.json`) and **resource-based** (`service.json` policies) access control - Securing **REST endpoints** so only specific apps, users, or API keys can call them - Setting up **GraphQL authorization** with the `@auth` directive - Understanding **VRN** (VTEX Resource Name) syntax for declaring principals - Debugging **403 Forbidden** errors caused by missing or misconfigured policies Do not use this skill for: - General service architecture (use `vtex-io-service-apps`) - PCI compliance and payment security (use `payment-pci-security`) - Route prefix and CDN behavior (use `vtex-io-service-paths-and-cdn`) ## Decision rules ### Role-based vs resource-based policies | | Role-based (`policies.json`) | Resource-based (`service.json` policies) | | -------------------------- | ----------------------------------------------------------------------- | -------------------------------------------------------------------------- | | **Who can call?** | Only other IO apps (by themselves or on behalf of other apps) | Apps, users, and integrations (API keys) |
Details
- Skill name
vtex-io-rbac- Repository
- vtex/skills
- Path
exports/opencode/vtex-io-rbac/SKILL.md- Repo updated
- 14 October 2026
FAQ
What does the Vtex Io Rbac skill do?
Apply when controlling access to VTEX IO app resources using role-based or resource-based policies. Covers policies.json for role-based access control, service.json policies for resource-based access, VRN syntax for principals, the difference between app-to-app and user/integration access, and GraphQL @auth directives. Use when deciding how to secure routes and restrict which apps, users, or integrations can access your endpoints.
How do I install the Vtex Io Rbac 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 Rbac 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.
Vtex Io Service Configuration Apps
47vtex/skills
Apply when designing VTEX IO configuration apps with the configuration builder or when a service app must receive structured configuration through runtime context. Covers the separation between service apps and configuration apps, schema.json and configuration.json, settingsType, and reading injected configuration through ctx.vtex.settings. Use for shared service configuration, decoupled configuration lifecycle, or reviewing whether app settings should be replaced by a configuration app.
Vtex Io Events and Workers
47vtex/skills
Apply when designing or implementing asynchronous processing in VTEX IO services through events, workers, and background handlers. Covers event handler structure, idempotency, retry-safe processing, and moving expensive work out of request-response routes. Use for event-driven integrations, delayed processing, or background jobs in VTEX IO apps.
App Project Kickoff
44SamueleBassoli/hermes-fleet-apps
Use when the owner wants an app built or an old tool rewritten.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.