Menú
Run grpcurl checks from inside the Docker Compose network (useful when host-to-container ports are blocked).
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Generate and complete reusable security test documents under docs/security/ based on the current project implementation and/or a confirmed plan. Use when a developer asks to complete security test docs, add missing security scenarios, or establish a security test baseline for the project.
Generate and maintain reusable UI/UX test documents under docs/uiux/ based on the current project UI implementation and the design-system constraints. Use when a developer asks to complete UI/UX test docs, add missing UI/UX scenarios, align UI constraints, or wants UI consistency/a11y/responsive regression checks during development.
Guide for working with the Agent Orchestrator — a CLI tool for AI-native SDLC automation. Use when writing or editing YAML manifests (Workspace, Agent, Workflow, StepTemplate, ExecutionProfile, SecretStore, EnvStore, Trigger, CRD), running orchestrator CLI commands, designing workflow step pipelines, writing CEL prehook/finalize expressions, configuring triggers (cron/event-driven task creation), or configuring self-bootstrap workflows. Triggers: any mention of orchestrator config, YAML manifests with "orchestrator.dev/v2", workflow steps, prehooks, finalize rules, task create/start/pause, orchestrator run, step filtering, direct assembly, agent capabilities, StepTemplate prompts, execution profiles, sandbox configuration, secret management, or trigger/cron scheduling.
Govern feature request (FR) documents through their full lifecycle — from planning to implementation to closure. Use when the user asks to govern/治理 a feature request, close an FR, check FR status, or says "治理FR", "/fr-governance". Scans docs/feature_request/ for open FR docs, plans implementation, executes governance, and self-checks closure.
Generate or update QA/security/UIUX test documentation after confirmed feature implementation plans or completed refactors. Use this skill AFTER plan approval or code completion to: (1) add new QA test docs for new behavior, (2) generate design docs, and (3) run repo-wide cross-doc impact analysis (docs/qa/, docs/security/, docs/uiux/, docs/guide/ and its translations, docs/design_doc/, docs/showcases/, root Markdown including CHANGELOG.md, and .claude/skills/) to update stale steps, expectations, and assertions. Triggers when users ask to create QA docs, update test docs after implementation, or sync QA/security/UIUX docs after behavior changes.
Govern and periodically remediate QA documentation quality across docs/qa, docs/security, and docs/uiux. Use when users ask to audit QA docs, run recurring documentation checks, fix doc drift after refactors, enforce scenario limits/checklists/UI entry visibility, or synchronize README/manifest/changelog consistency.
| name | grpc-regression |
| description | Run grpcurl checks from inside the Docker Compose network (useful when host-to-container ports are blocked). |
When host -> container gRPC access is blocked or flaky, run grpcurl from an ephemeral Docker container on the same Docker Compose network.
# Smoke checks (customize via env vars)
.claude/skills/tools/grpc-smoke.sh
# Example: list services (works only if server reflection is enabled)
.claude/skills/tools/grpcurl-docker.sh -plaintext my-grpc:50051 list
# Example: call a method using a mounted proto
.claude/skills/tools/grpcurl-docker.sh \
-import-path /proto -proto my.proto \
-d '{"hello":"world"}' \
my-grpc:50051 my.pkg.Service/MyMethod
Use this pattern when reflection is disabled and service auth is enabled:
.claude/skills/tools/grpcurl-docker.sh \
-cacert /certs/ca.crt -cert /certs/client.crt -key /certs/client.key \
-H "x-api-key: ${GRPC_API_KEY:-dev-grpc-api-key}" \
-import-path /proto -proto my.proto \
-d '{"identity_token":"dummy","tenant_id":"dummy","service_id":"dummy"}' \
my-grpc:50051 my.pkg.Service/MyMethod
Recommended negative/positive regression checks:
GRPC_NETWORK: Docker network name. If unset, auto-detect from running Compose containers (fallback: require explicit GRPC_NETWORK).GRPC_COMPOSE_FILE: Compose file path used for auto-detect (defaults to docker/docker-compose.yml if present).GRPC_IMAGE: grpcurl image (default: fullstorydev/grpcurl)GRPC_MOUNT_PROTO: Host path to mount to /proto:ro (optional). Relative paths are resolved from repo root.GRPC_API_KEY: Optional API key value for secured endpoints.