vtex-io-security-boundaries — Claude Code skill: setup & use
Guides coding assistants when auditing route exposure and data boundaries in VTEX IO apps. Prevents tenant leaks and enforces payload validation.
npx skills add vtex/skills --skill vtex-io-security-boundaries -a claude-codeWhat vtex-io-security-boundaries does
This skill guides assistants through inspecting service exposure in VTEX IO backends. It treats any route marked with public: true in service.json as exposed to the open web. Obscure route paths offer zero protection. Handlers must inspect incoming bodies, query parameters, and secret headers before passing payloads to internal handlers.
The instructions establish explicit development rules. Services must filter outgoing responses so upstream records never return raw payloads to callers. Logic handling tenant data must verify ctx.vtex.workspace and ctx.vtex.account to avoid cross-tenant contamination. Standard runtime console.log calls are banned in favor of structured logging via ctx.vtex.logger.
Permissions inside manifest.json and identity token selection stay out of scope. Those checks belong in companion VTEX skills.
What it helps with
- validate incoming webhook payloads before executing domain methods
- isolate data across tenant accounts and isolated workspaces
- trim raw downstream payloads to stop internal field leaks
- replace unformatted console.log statements with ctx.vtex.logger
Example prompts for the agent
- Review our service.json routes to make sure no internal endpoints are public
- Add early payload and signature validation to this incoming webhook handler
- Strip sensitive fields from this response object before returning it to the caller
How to install vtex-io-security-boundaries
1Skills CLI (Vercel)
npx skills add vtex/skills --skill vtex-io-security-boundaries -a claude-code2Manually: put the files in place
~/.claude/skills/vtex-io-security-boundaries/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/vtex-io-security-boundaries/
1Skills CLI (Vercel)
npx skills add vtex/skills --skill vtex-io-security-boundaries -a codex2Manually: put the files in place
.agents/skills/vtex-io-security-boundaries/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add vtex/skills --skill vtex-io-security-boundaries -a cursor2Manually: put the files in place
.cursor/skills/vtex-io-security-boundaries/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install vtex/skills vtex-io-security-boundaries2Manually: put the files in place
.github/skills/vtex-io-security-boundaries/SKILL.md1Skills CLI (Vercel)
npx skills add vtex/skills --skill vtex-io-security-boundaries -a gemini-cli2Platform CLI
gemini skills install https://github.com/vtex/skills --path skills/vtex-io-security-boundariesManually: put the files in place
.devin/skills/vtex-io-security-boundaries/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add vtex/skills --skill vtex-io-security-boundaries -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about vtex-io-security-boundaries
How to install vtex-io-security-boundaries in Claude Code?
Run npx skills add vtex/skills --skill vtex-io-security-boundaries -a claude-code. The file will be written to ~/.claude/skills/vtex-io-security-boundaries/SKILL.md.
What does vtex-io-security-boundaries do?
It provides rules for securing VTEX IO service routes, catching accidental data exposure, and enforcing boundary input checks.
How does this differ from vtex-io-auth-and-policies?
This skill evaluates what data safely crosses app boundaries, whereas vtex-io-auth-and-policies configures permission policies in manifest.json.