This skill should be used when the user asks to automate Claude Code headlessly, run claude -p in CI or scripts, parse json or stream-json output, use --bare, configure non-interactive permissions, compare CLI vs TypeScript or Python Agent SDK usage, wire MCP or hooks for automation, resume sessions programmatically, or harden reproducible Claude Code automation.

This skill should be used when the user asks to scaffold or verify a Claude Agent SDK app in Python or TypeScript — routing to the agent-sdk-dev plugin under toolkit governance.

This skill should be used when the user asks to audit, improve, or update CLAUDE.md files with session learnings — routing to the claude-md-management plugin under toolkit governance.

This skill should be used when the user asks to commit, push and open a PR, or clean gone git branches — routing to the commit-commands plugin under toolkit governance.

This skill should be used when the user asks to scaffold a Claude Code plugin, design plugin structure, develop a command/agent/hook/MCP/skill, validate a plugin, or review a skill — routing to the plugin-dev plugin under toolkit governance.

This skill should be used when the user asks to review a PR or diff for code quality, comments, tests, error handling, type design, or simplification — routing to pr-review-toolkit's specialized agents under toolkit governance.

This skill should be used when the user asks to create a skill from scratch, optimize an existing skill, run skill evals, or benchmark skill performance — routing to the skill-creator plugin under toolkit governance.

Design current Claude Code hooks with nested matcher-entry schema, five handler types, matcher/if boundaries, permissions-aware policy, portable scripts, MCP timing checks, and deterministic validation.

Deploy and operate on Hostinger: shared and VPS hosting, Git/SFTP/PM2 deployment, MySQL/MariaDB, auto-renewing SSL, DNS and email via hPanel. [EXPLICIT] One of the three target platforms (Firebase + Vercel + Hostinger). Trigger: 'hostinger', 'shared hosting', 'hpanel', 'vps deploy', 'pm2', 'mariadb'.

Infrastructure and platform architecture — compute, network, storage, HA/DR, IAM, cloud landing zones, and cost optimization. Use when the user asks to 'design cloud infrastructure', 'plan network topology', 'define HA/DR strategy', 'set up cloud landing zones', 'optimize cloud costs', or mentions VPC, Kubernetes, serverless, multi-AZ, IAM, reserved instances, or chaos testing. [EXPLICIT]

Pre-processing layer that analyzes raw user input — detecting surface errors, performing root-cause analysis (5 Whys), impact tracing (7 So-Whats), and intent gap analysis — then reformulates into a precise, actionable prompt.

System integration patterns — point-to-point, ESB, iPaaS, event mesh, API contract management, data mapping. Use when the user asks to 'design integrations', 'map system connections', 'define API contracts', 'plan event-driven integration', or mentions ESB, iPaaS, MuleSoft, API gateway, event mesh, data mapping. [EXPLICIT]

Investigacion adaptativa: mapeo barato, budget de exploracion acotado y re-plan disciplinado solo al invalidar la hipotesis.

Seleccion de built-in tools con estrategia Grep then Read then Edit, failure modes y sin Read masivo upfront.

Confidence calibration contra labeled set y stratified sampling por document_type; accuracy desglosada, nunca agregada.

Mitigación material de context dilution: selección de contexto para editing/compaction y validación de ventana, thinking, media y overflow sin umbrales porcentuales inventados.

Evaluacion critica: cross-check numerico declarado vs calculado, mismatch flag con ambos valores, sin corregir en silencio.

Cross-cutting reliability patterns for PubNub apps. Covers reconnect with exponential backoff + jitter, idempotent publish with client-generated message IDs, dedup-on-merge for live + history streams, queue-and-retry for offline writes, and schema versioning of message envelopes. Use during design reviews, when planning offline support, or during incident response when network or delivery reliability is the concern.

Logging, testing, cost hygiene, incident triage, and usage metrics for PubNub apps. Covers the correlation fields every send/receive must log, the test pyramid for real-time apps, payload + fan-out cost hygiene, the incident triage runbook, and PubNub usage metrics for billing reconciliation. Use during code reviews, when planning monitoring, when triaging incidents, or when investigating PubNub cost overruns.

Manages PubNub apps, keysets, and environment separation. Covers the publish/subscribe/secret key model, dev/staging/prod isolation, key rotation hygiene, demo-key boundaries, and custom origin configuration. Use when setting up a new PubNub project, separating environments, rotating keys, configuring demo or production keysets, or asking about apps, keysets, or custom origins.