VTEX IO's permission model can be confusing because you're juggling License Manager policies, app-to-app role grants, and outbound-access rules all in one manifest. This skill helps you map each integration or protected route to the right policy type, keep outbound rules scoped tight, and catch the silent runtime failures that happen when your code is correct but your manifest is missing a single line. It's opinionated about least privilege and won't let you merge policy changes without seeing the behavior they unlock. If you've ever debugged a 403 from a VTEX service only to discover you forgot to declare a policy, or you're adding an external API call and need to know whether that's an outbound rule or something else, this is the reference.
npx -y skills add vtex/skills --skill vtex-io-auth-and-policies --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
prisma/skills
firebase/agent-skills
Dexploarer/hyper-forge
itsmostafa/aws-agent-skills
prisma/skills