245 skills · sorted by relevance
Switch PUA to offline mode from Codex CLI. This alias updates the offline setting and sets feedback frequency to zero while preserving other configuration fields, then reports the mode change.
Disables PUA's always-on mode from Codex CLI and sets feedback frequency to zero. The alias updates the local configuration while preserving unknown fields, then reports completion with evidence from the executed command.
Generate a PUA KPI and performance report card from Codex CLI. This command alias loads pua-pro and provides a Codex equivalent of the Claude Code /pua:kpi command through $pua-kpi.
Assess GraphQL APIs during penetration tests, from finding endpoints and mapping data structures to checking access controls, query limits, subscriptions, and uploads. Includes example queries, guidance for testing tools, and defensive controls for interpreting findings.
Configure a Next.js app using posthog-js so session recording and dead-click capture survive browser ad blockers. Aliases the three blocker-flagged JS chunks (dead-clicks-autocapture.js, recorder.js, posthog-recorder.js) to bland same-origin paths via Next.js rewrites, and monkey-patches HTMLScriptElement so posthog-js requests the aliases. TRIGGER when posthog-js session replay or dead-click capture is failing in production with ERR_BLOCKED_BY_CLIENT or 404s on /static/dead-clicks-autocapture.js / /static/recorder.js / /static/posthog-recorder.js, or when the user wants to bypass ad blockers for these specific assets. Works alongside an existing PostHog reverse proxy (managed or otherwise) — only the three blocked files divert through Next.js, all other PostHog traffic stays on the original api_host. SKIP for unrelated PostHog setup, non-Next.js apps, or when capture/decide endpoints (/e/, /decide/, /array/*/config.js) are the ones being blocked — those need a different treatment.
The English summary is being prepared. Showing the original description.
Building or editing Simulink (.slx) models that stream signals in frames using DSP System Toolbox — audio, vibration, radar, comms. Use when the prompt names a Simulink block (Discrete FIR Filter, Buffer, Unbuffer, Rate Transition, Downsample, Upsample, Sample-Rate Converter, FIR Decimation, Time Scope, Spectrum Analyzer, From Multimedia File) or an action (frame-based processing, InputProcessing, buffering, overlap, windowing, STFT, short-time Fourier, decimate, downsample, upsample, resample, multirate, anti-aliasing, tunable filter). Prevents silent numerical errors from sample-vs-frame mismatch, wrong block choice, or missing anti-aliasing.
The English summary is being prepared. Showing the original description.
Fix HTTP 500 / ClickHouse "column not found" errors when filtering by a MATERIALIZED column through a VIEW that doesn't expose it. Use when: (1) a WHERE clause references alias.column on a view but the column is MATERIALIZED on the underlying table, (2) the query works on the raw table but fails through the view, (3) adding a new filter param to an API causes 500 even though the column exists in the base table. Fix by using a subquery against the base table instead of referencing the column directly on the view. Applies to ClickHouse views over tables with MATERIALIZED or ALIAS columns.
The English summary is being prepared. Showing the original description.
Debug ClickHouse deserialization errors in Rust caused by column ORDER mismatch when using SELECT alias.* on a VIEW that adds computed columns. Use when: (1) Some query variants (e.g. sort=trending) return 500 but others (sort=recent) succeed, (2) Queries use SELECT view_alias.*, extra_cols FROM view JOIN ..., (3) The Rust Row struct has the right number and types of fields but deserialization fails anyway (wrong type error, not "not enough data"), (4) The VIEW was recently extended with a computed column (e.g. trending_score).
The English summary is being prepared. Showing the original description.
Foundations of digital signal processing — sampling, aliasing, the Nyquist criterion, quantization, convolution, the discrete Fourier transform, FFT, FIR and IIR filter design, windowing, spectral leakage, and practical issues in fixed-point versus floating-point implementation. Use when designing filters, analyzing spectra, choosing sample rates, reasoning about aliasing, or implementing DSP algorithms on a microcontroller, DSP chip, or host CPU.
The English summary is being prepared. Showing the original description.
Strategic owner of Horizon, the VNX future-state layer (roadmap -> tracks -> deliverables) and the plan-first gate. USE THIS when the user wants to plan the next VNX feature, decide what to build next, add something to the roadmap, prioritize or schedule (inplannen) work into now/next/later horizons, break a feature into deliverables, set the routing FLOOR, or run the plan-gate on a feature. The tracks DB (`vnx horizon`, alias `vnx objective`) is the source of truth; the repo ROADMAP.yaml is a generic example, not the SSOT. Plans and gates only: never dispatches, never closes open-items. The plan-gate (one seat, a second on BLOCK) runs only on an explicit plan-gate step. (Renamed from `pm` 2026-07-05 — `/pm`/`@pm` still resolve via the backward-compat alias in `.claude/skills/pm/SKILL.md`.)
The English summary is being prepared. Showing the original description.
Backward-compat alias for @horizon (this skill was renamed from `pm` to `Horizon` on 2026-07-05). USE THIS only when invoked directly as `/pm` or via an existing `@pm` delegation reference — it redirects immediately to @horizon, the strategic owner of the VNX future-state layer (roadmap -> tracks -> deliverables) and the plan-first gate. Prefer `@horizon` / `vnx horizon` for anything new; this alias exists only for transition safety.
The English summary is being prepared. Showing the original description.
Planning specialist that breaks a VNX feature or track into small, independently-shippable PRs with dependencies and per-PR task-class routing. USE THIS when the user wants to break a feature down into PRs, sequence the work, or turn a plan into a PR queue. Delegated to by @horizon (formerly @pm — @pm still resolves via alias). Works from Horizon's tracks DB (`vnx horizon`, alias `vnx objective`); the repo FEATURE_PLAN.md is a generated generic example, not the source.
The English summary is being prepared. Showing the original description.
Strategic owner of Horizon, the VNX future-state layer (roadmap -> tracks -> deliverables) and the plan-first gate. USE THIS when the user wants to plan the next VNX feature, decide what to build next, add something to the roadmap, prioritize or schedule (inplannen) work into now/next/later horizons, break a feature into deliverables, set the routing FLOOR, or run the plan-gate on a feature. The tracks DB (`vnx horizon`, alias `vnx objective`) is the source of truth; the repo ROADMAP.yaml is a generic example, not the SSOT. Plans and gates only: never dispatches, never closes open-items. The plan-gate runs one seat, a second on BLOCK, and runs only on an explicit plan-gate step. (Renamed from `pm` 2026-07-05 — `/pm`/`@pm` still resolve via the backward-compat alias in `.claude/skills/pm/SKILL.md`.)
The English summary is being prepared. Showing the original description.
Systematic checklist for diagnosing audio artifacts. Use when the user describes a sound quality problem — clicks, pops, crackling, silence, DC offset, aliasing, phase issues, or latency problems. Trigger on phrases like "why do I hear clicks?", "my output has DC offset", "there's aliasing in my oscillator", "phase is wrong in mono", "dropout when CPU spikes". Pairs with audio-dsp-review (realtime safety) and audio-numerics-review (numeric correctness) — use those to fix once the cause is found.
The English summary is being prepared. Showing the original description.
ALIAS for dag-orchestrator. The original DAG execution skill, now unified with orchestrator into dag-orchestrator. Use dag-orchestrator for the full HTDAG experience.
The English summary is being prepared. Showing the original description.
Compatibility alias for Annotated Documents. Use when explicitly invoked as $document or /kpopper:document. Follow the canonical annotated-doc skill; do not select this alias for ordinary requests.
The English summary is being prepared. Showing the original description.
Compatibility alias for kpopper Hub. Use when explicitly invoked as $page or /kpopper:page. Follow the canonical hub skill; do not select this alias for ordinary requests.
The English summary is being prepared. Showing the original description.
Change the public agent-facing CLI surface while preserving registry-backed discovery, JSON envelopes, aliases, docs, and tests.
The English summary is being prepared. Showing the original description.
Audit and improve stable names, aliases, vocabulary, field casing, routes, ports, packages, and agent-search discoverability.
The English summary is being prepared. Showing the original description.
Rework an existing NV oOS Pro toolkit from a single-tenant demo into a universal product — currency-neutral schema with legacy aliases, a Tenant Profile + token renderer shared across the two assistant-delivery surfaces (packs via Portability vs blueprints via Blueprint Installer), demo-mode inversion, a universal single-folder ingestor (header-alias dictionary + dry_run + JSON), report export to CSV/PDF (DomPDF vs html_to_pdf choice), the add-a-tool drift checklist (TOOLS_LIST, coverage manifest, admin tool list, presets), and the re-seed-on-settings-save gotcha. Use when asked to 'universalise', 'de-demo', 'multi-tenant', 're-tenant', 'remove LKR/Surf Club', 'point the toolkit at a single Drive folder', 'export reports as CSV/PDF', or 'avoid re-installing assistants on save'. First case study: food-beverage (F&B Management, 2026-10-16). Complements mcp-ai-wpoos-toolkit-creation (build new) and mcp-ai-wpoos-toolkit-audit (harden existing).
The English summary is being prepared. Showing the original description.
Add projections to collections to rename fields or map nested JSON paths to flat column names. Use when renaming fields for destination conventions, flattening nested paths to columns, or creating field aliases. Use when user says "rename field", "flatten nested JSON", "map JSON path to column", "field alias", or "projection".
The English summary is being prepared. Showing the original description.
Use when working with Azure Dns — azure DNS management covering public and private DNS zones, record sets, virtual network links, DNSSEC, and alias records. Use when managing Azure DNS zones, configuring DNS records, setting up private DNS for VNets, managing alias records for Azure resources, or troubleshooting DNS resolution.
The English summary is being prepared. Showing the original description.
Inspects URL paths and proposes, tests, orders, and applies project-level path cleaning rules so dynamic segments (numeric IDs, UUIDs, slugs, dates) collapse into readable aliases. Use when the user says "clean the paths", "normalize URLs", "group similar pages", "too many distinct paths", "/users/123 and /users/456 are the same page", "set up path cleaning", or asks why a Web analytics or Paths breakdown is fragmented across thousands of nearly-identical URLs. Covers regex syntax (re2), alias placeholder convention, rule ordering, the test workflow, and applying rules via the project-settings-update MCP tool.
The English summary is being prepared. Showing the original description.
ALIAS for dag-orchestrator. The original DAG execution skill, now unified with orchestrator into dag-orchestrator. Use dag-orchestrator for the full HTDAG experience.
The English summary is being prepared. Showing the original description.