Vtex Io Security Boundaries
Apply when reviewing or designing security-sensitive boundaries in VTEX IO apps. Covers public versus private exposure, trust assumptions at route and integration boundaries, sensitive data handling, validating what crosses the app boundary, and avoiding leakage across accounts, workspaces, users, or integrations. Use for route hardening, data exposure review, or evaluating whether a service boundary is too permissive.
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-security-boundariesgit clone --depth 1 https://github.com/vtex/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/exports/opencode/vtex-io-security-boundaries ~/.claude/skills/vtex-io-security-boundariesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Security Boundaries & Exposure Review ## When this skill applies Use this skill when the main question is whether a VTEX IO route, integration, or service boundary is safe. - Reviewing public versus private route exposure - Validating external input at service boundaries - Handling tokens, account context, or sensitive payloads - Avoiding cross-account, cross-workspace, or cross-user leakage - Hardening integrations that expose or consume sensitive data Do not use this skill for: - policy declaration syntax in `manifest.json` - service runtime sizing - logging and observability strategy - frontend browser security concerns - deciding which VTEX auth token should call an endpoint ## Decision rules - Use this skill to decide what data and input may safely cross the app boundary, not which policies or tokens authorize the call. - Treat every public route as an explicit trust boundary. - In `service.json`, changing a route from `public: false` to `public: true` is a boundary change and should trigger explicit security review. - Use `public: true` for routes that must be callable from outside VTEX IO, such as partner webhooks or externally consumed integration endpoints. Treat them as internet-exposed boundaries. - Use `public: false` for routes that are meant only for VTEX internal flows or other IO apps, but do not treat them as implicitly safe. They still require validation and scoped assumptions.
Details
- Skill name
vtex-io-security-boundaries- Repository
- vtex/skills
- Path
exports/opencode/vtex-io-security-boundaries/SKILL.md- Repo updated
- 14 October 2026
FAQ
What does the Vtex Io Security Boundaries skill do?
Apply when reviewing or designing security-sensitive boundaries in VTEX IO apps. Covers public versus private exposure, trust assumptions at route and integration boundaries, sensitive data handling, validating what crosses the app boundary, and avoiding leakage across accounts, workspaces, users, or integrations. Use for route hardening, data exposure review, or evaluating whether a service boundary is too permissive.
How do I install the Vtex Io Security Boundaries 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 Security Boundaries 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.
Secure Build
44SamueleBassoli/hermes-fleet-apps
Use when writing, auditing or deploying code: security defaults and a review pass.
Masterdata Storage Strategy
47vtex/skills
Apply when deciding whether VTEX Master Data is the right storage for a given workload, designing JSON Schemas with v-indexed, v-cache, v-security, and v-triggers, planning entity capacity and lifecycle, or auditing existing Master Data usage. Covers when to use MD versus Catalog, OMS, VBase, or external databases, schema design best practices, indexing strategy, trigger patterns, and operational considerations. Use before creating any new Master Data entity.
Security Review
48frankxai/claude-skills-library
Scan a port or a diff before it lands, and apply the narrow deny list for this machine. Use before copying upstream skills, hooks, or commands into a repo or into the live Claude directory.
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.