# Recommended Skills: Hermes Phase 0 — Gateway API + Telemetry

> Auto-generated by Pipeline Skill Advisor (advise_skills MCP tool). 11 Apply/Reference matches + 5 Consider tier across 735 scanned skills.

> **Per-slice anticipated overlap** (informational; each slice's harness:planning run will re-scan to confirm):
>
> - **S1 (Auth foundation + OpenAPI):** `ts-zod-integration` (schemas as single source of truth), `node-crypto-patterns` (HMAC + timingSafeEqual + token hashing), `gof-chain-of-responsibility` (auth → scope-check → audit middleware chain), `owasp-security-headers` (response hardening on the new /api/v1 surface).
> - **S2 (Versioned API surface):** `ts-zod-integration` (route schema generation), `microservices-api-gateway` (versioning, deprecation header discipline), `ts-template-literal-types` (typed route paths), `gof-facade-pattern` (route wrappers around existing handlers).
> - **S3 (Webhook subscriptions + signing):** `node-crypto-patterns` (HMAC SHA-256 signing), `events-event-schema` (GatewayEvent envelope shape), `gof-visitor-pattern` (event-type dispatch to delivery worker).
> - **S4 (Delivery durability):** `ts-performance-patterns` (queue worker concurrency cap), `gof-chain-of-responsibility` (retry-ladder state machine), `gof-flyweight-pattern` (delivery row reuse across retries).
> - **S5 (Telemetry export):** `ts-performance-patterns` (async exporter without blocking dispatch hot path), `events-event-schema` (OTLP span attribute conventions), `ts-utility-types` (discriminated trace-kind unions), `ts-testing-types` (typed fixtures for OTel collector integration tests).
>
> **Workflow skills not in the relevance scan** but always apply at slice-plan time: `harness:soundness-review`, `harness:planning`, `harness:execution`, `harness:verification`, `harness:integration`, `harness:tdd`, `harness:perf`, `harness:architecture-advisor`, `harness:enforce-architecture`, `harness:security-review` (especially S1 and S3).
>
> **Flag `angular-standalone-components`, `nuxt-deployment-config`, `svelte-routing-pattern`** — surfaced by the scan due to general TypeScript stack signals but **not applicable** (harness dashboard is React, not Angular/Nuxt/Svelte). Ignore in slice plans.

## Apply (invoke during execution)

| Skill                | Purpose                                                                            | When                   | Relevance |
| -------------------- | ---------------------------------------------------------------------------------- | ---------------------- | --------- |
| `ts-zod-integration` | Stack: typescript; Domain: api, auth, data, design, infra, perf, security, testing | Architecture decisions | 0.62      |

## Reference (load as context)

| Skill                         | Purpose                                                                                            | When                   | Relevance |
| ----------------------------- | -------------------------------------------------------------------------------------------------- | ---------------------- | --------- |
| `ts-performance-patterns`     | Stack: typescript; Domain: api, auth, data, design, infra, perf, security, testing                 | During implementation  | 0.57      |
| `gof-facade-pattern`          | Stack: typescript; Domain: api, auth, data, design, infra, perf, security, testing                 | Architecture decisions | 0.56      |
| `gof-chain-of-responsibility` | Stack: typescript; Domain: api, auth, data, design, infra, perf, security, testing                 | Architecture decisions | 0.54      |
| `gof-visitor-pattern`         | Stack: typescript; Domain: api, auth, data, design, infra, perf, security, testing                 | Architecture decisions | 0.54      |
| `ts-testing-types`            | Stack: typescript; Domain: api, auth, data, design, infra, perf, security, testing                 | Testing                | 0.54      |
| `ts-utility-types`            | Stack: typescript; Domain: api, auth, data, design, infra, perf, security, testing                 | During implementation  | 0.53      |
| `node-crypto-patterns`        | Keywords: hmac; Stack: typescript; Domain: api, auth, data, design, infra, perf, security, testing | During implementation  | 0.52      |
| `gof-flyweight-pattern`       | Stack: typescript; Domain: api, auth, data, design, infra, perf, security, testing                 | Architecture decisions | 0.49      |
| `microservices-api-gateway`   | Stack: typescript; Domain: api, auth, data, design, infra, perf, security, testing                 | Architecture decisions | 0.49      |
| `ts-template-literal-types`   | Stack: typescript; Domain: api, auth, data, design, infra, perf, security, testing                 | Architecture decisions | 0.49      |

## Consider

| Skill                           | Purpose                                                                            | When                   | Relevance |
| ------------------------------- | ---------------------------------------------------------------------------------- | ---------------------- | --------- |
| `angular-standalone-components` | Stack: typescript; Domain: api, auth, data, design, infra, perf, security, testing | During implementation  | 0.35      |
| `events-event-schema`           | Stack: typescript; Domain: api, auth, data, design, infra, perf, security, testing | Architecture decisions | 0.35      |
| `nuxt-deployment-config`        | Stack: typescript; Domain: api, auth, data, design, infra, perf, security, testing | During implementation  | 0.35      |
| `owasp-security-headers`        | Stack: typescript; Domain: api, auth, data, design, infra, perf, security, testing | During implementation  | 0.35      |
| `svelte-routing-pattern`        | Stack: typescript; Domain: api, auth, data, design, infra, perf, security, testing | During implementation  | 0.35      |

---

_Scanned 735 skills in 1138ms. Signals: 6 keywords, 2 stack markers, 8 domains._
