Vtex Io Observability and Ops
Apply when making VTEX IO services easier to observe, troubleshoot, and operate in production. Covers metrics, structured logging, failure visibility, rate-limit awareness, and production readiness checks for backend apps. Use for integration monitoring, error diagnosis, or improving the operational quality of VTEX IO services before or after release.
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-observability-and-opsgit clone --depth 1 https://github.com/vtex/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/exports/opencode/vtex-io-observability-and-ops ~/.claude/skills/vtex-io-observability-and-opsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Observability & Operational Readiness ## When this skill applies Use this skill when a VTEX IO service needs better production visibility, troubleshooting behavior, or operational safety. - Adding metrics to important client calls or flows - Improving logs for routes, workers, or integrations - Surfacing failures clearly for operations and support - Reviewing whether a service is ready for production - Monitoring rate-limit-sensitive integrations Do not use this skill for: - app policy declaration - trust-boundary modeling - frontend analytics or browser monitoring - route contract design by itself ## Decision rules - Log enough structured context to debug failures, but do not log secrets or sensitive payloads. - Use `ctx.vtex.logger` with appropriate log levels such as `info`, `warn`, and `error` instead of `console.log`, so logs are properly collected and searchable in the VTEX logging stack. - Treat `ctx.vtex.logger` as the native platform logging mechanism. If a partner needs to forward logs to its own logging system, prefer doing that through a dedicated integration app or client instead of replacing the VTEX logger pattern inside every service. - Use client-level metrics on important downstream calls so integration behavior is visible below the handler layer. - Choose metric names that reflect the integration and operation, such as `partner-get-order` or `partner-sync-catalog`, so counts, latency, and error rates can be tracked over time.
Details
- Skill name
vtex-io-observability-and-ops- Repository
- vtex/skills
- Path
exports/opencode/vtex-io-observability-and-ops/SKILL.md- Repo updated
- 14 October 2026
FAQ
What does the Vtex Io Observability and Ops skill do?
Apply when making VTEX IO services easier to observe, troubleshoot, and operate in production. Covers metrics, structured logging, failure visibility, rate-limit awareness, and production readiness checks for backend apps. Use for integration monitoring, error diagnosis, or improving the operational quality of VTEX IO services before or after release.
How do I install the Vtex Io Observability and Ops 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 Observability and Ops 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.
CI CD Github Actions
430xranx/agentbrief
When setting up, debugging, or optimizing CI/CD pipelines. Use when the user mentions 'GitHub Actions,' 'CI/CD,' 'workflow,' 'pipeline,' 'deploy,' 'release automation,' 'build failing,' 'tests not running in CI,' or needs to automate testing, building, or deployment processes.
Fmriprep
43NeuroAIHub/awesome_cognitive_and_neuroscience_skills
Preprocess task-based or resting-state fMRI data with fMRIPrep — a robust, BIDS-App preprocessing pipeline built on FSL, ANTs, FreeSurfer, AFNI, and Nilearn. Use this skill whenever the user asks to preprocess fMRI/BOLD data, run fMRIPrep on a BIDS dataset, set up Docker/Singularity/Apptainer containers for fMRIPrep, choose output spaces (MNI152NLin2009cAsym, fsaverage, fsLR/CIFTI), configure susceptibility distortion correction (SDC), extract or interpret the confounds table, resample to surface/grayordinates, cite fMRIPrep and its dependencies, or debug fMRIPrep crashes and hangs.
Monitoring Observability
430xranx/agentbrief
Set up monitoring, logging, and observability for applications and infrastructure. Use when implementing health checks, metrics collection, log aggregation, or alerting systems. Handles Prometheus, Grafana, ELK Stack, Datadog, and monitoring best practices.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.