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 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 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 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 operate Claude Code /goal, write a goal completion condition, compare /goal with /loop, Stop hooks, or auto mode, diagnose a stuck goal loop, set stop conditions, resume or clear an active goal, or define safe continuation gates for autonomous Claude Code sessions.

Generative AI architecture — RAG patterns, LLM orchestration, multi-model tiering, agent workflow design, vector database architecture, knowledge connectors, and GenAI quality assurance. This skill should be used when the user asks to 'design RAG architecture', 'architect LLM system', 'select vector database', 'design AI agents', 'implement knowledge retrieval', 'plan GenAI quality', or mentions RAG, embeddings, vector search, LLM orchestration, agent framework, context-aware generation, hallucination reduction, or multi-model routing. [EXPLICIT]

Functional specifications. MVP modules, 8+ use cases, business rules, acceptance criteria. Data models (relational/NoSQL). [EXPLICIT]

Build on Firebase: Auth, Cloud Functions, Firestore security rules and query optimization, Hosting, Storage, scheduled jobs, emulator suite, and cost control. [EXPLICIT] One of the three target platforms (Firebase + Vercel + Hostinger). Trigger: 'firebase', 'firestore', 'cloud functions', 'firebase auth', 'firebase hosting', 'security rules'.

Cloud financial operations assessment and strategy using FinOps Foundation framework. Use when the user asks to 'assess cloud costs', 'optimize cloud spending', 'FinOps assessment', 'cloud cost analysis', 'rightsizing', 'reservation strategy', 'showback/chargeback model', 'cloud unit economics', 'cost allocation', or mentions 'cloud financial management', 'cost optimization', 'FinOps maturity'. [EXPLICIT]

Performs 7-dimension technical feasibility assessment covering architecture, team capability, timeline, cost, risk, integration, and scalability. [EXPLICIT] Produces go/no-go recommendations with confidence levels. [EXPLICIT] Trigger: 'feasibility', 'technical assessment', 'go/no-go', 'viability'

Event-driven architecture — event catalog, schema registry, eventual consistency, saga, CQRS, event sourcing. Use when the user asks to 'design event-driven system', 'build event catalog', 'implement CQRS', 'design saga patterns', 'set up schema registry', 'implement event sourcing', or mentions Kafka, RabbitMQ, Pulsar, event bus, dead-letter queue, consumer groups, or event replay. [EXPLICIT]

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.

Builds real-time analytics and automation with PubNub Illuminate. Covers Business Objects (schema), Metrics (aggregations), Decisions (threshold-triggered actions with the 4-step PUT workflow), Queries (ad-hoc vs saved pipelines), and Dashboards. Use when tracking KPIs, building threshold alerts, automating mute/publish/App-Context-update actions, detecting spam or anomalies, or visualizing live activity.

Retrieves historical PubNub messages via Message Persistence (Storage & Playback). Covers timetoken-based pagination, per-channel ordering guarantees, offline catch-up flows, retention configuration, and the "catch-up tool not a data lake" principle. Use when fetching past messages, paginating with timetokens, building offline-resume UI, retrieving messages with actions, or configuring retention.

Routes PubNub events to external systems with no code via Events & Actions (E&A). Covers event listeners (Messages, Users, Channels, Push, Memberships), action targets (Webhook, SQS, Kinesis, S3, Kafka, IFTTT, AMQP), filter types (basic vs JSONPath), retry policy, envelopes, and batching. Use when integrating PubNub with Lambda, Kafka, SQS, S3, EventBridge, an analytics pipeline, or any external system.

Routes PubNub questions to the correct documentation source, MCP tool, and specialist skill. Classifies intent (chat vs non-chat, conceptual vs implementation, runtime testing vs analytics) and points the agent to the right next step. Use when a user mentions PubNub for the first time, asks "where do I start", "which docs", "what should I use", or any time the appropriate next skill is unclear.

Manages PubNub App Context (Objects API) for users, channels, and memberships. Covers user/channel metadata, custom fields, membership management, querying with filters, and referential integrity. Use when storing user profiles, channel metadata (name, topic, mute flags), tracking who is in which channel, or working with the Objects/App Context API.

Use when the user asks to create, edit, update, design, or configure a Harness Chaos Experiment — including faults, probes, actions, experiment YAML, fault injection, pod-delete, or resilience tests. Do not use for Chaos steps inside a pipeline or a DRTest stage; use chaos-dr-test for those. Do not use to run an experiment, list past runs, or inspect run results — call the Chaos MCP tools directly for those (see Performance Notes). Trigger phrases: chaos experiment, chaos engineering, resilience test, fault injection, pod-delete, chaos hub template.