glapsfun

Use when a raw request should go to whichever tflow skill fits best — when it is unclear which family member applies, or the request needs sharpening, delegation, and an acceptance check against criteria fixed before any work starts

Use when authoring or hardening a portable Agent Skill (a SKILL.md plus its scripts and references) that must stay valid and distributable across Claude Code and Codex skill directories

Use when the gateway itself must never appear in its own routing table

Use when a non-tflow skill must be ignored by discovery

Use when alpha fixture routing applies

Use when beta fixture routing applies

Use when the user shares a raw, vague, or first-draft prompt and wants it clarified, tightened, strengthened, or made more reliable — or asks to improve, rewrite, or optimize a prompt, write a system prompt, or apply prompt-engineering techniques like few-shot examples, chain-of-thought, role framing, or XML structuring

Use when a raw Agent Skill idea must become a tested, reviewed, and documented skill through the full eight-step pipeline; for a single phase alone, use the matching phase skill directly

Use when the user reports an operational problem or incident — pods crashing or CrashLoopBackOff, latency spikes, rising error rates, missing/broken metrics, failing or stuck deployments, alerts firing, OOMKilled, service unreachable, node problems — or asks to investigate a production issue, find a root cause, plan a remediation, or write an incident report. Also invoked explicitly via /sre-agent.

Expert AWS CLI guidance. Use when the task involves aws commands or the AWS CLI — installing, updating, or pinning AWS CLI v2 (and migrating scripts off the end-of-support v1), authentication issues ("Unable to locate credentials", "ExpiredToken", "The SSO session has expired", aws configure sso and aws sso login, IAM Identity Center, access keys, assume-role, credential_process, EC2/ECS role credentials), profiles and the ~/.aws/config and ~/.aws/credentials files, AWS_PROFILE/AWS_REGION and other AWS_* env vars, scripting aws with --query JMESPath, --output json/text, --no-cli-pager, pagination and return codes, s3 vs s3api, or any AWS resource work driven through the aws CLI (EC2, S3, IAM, STS, Lambda, EKS, ECR, CloudFormation, CloudWatch Logs, SSM, DynamoDB).

Expert GitLab guidance covering the glab CLI, .gitlab-ci.yml authoring, and CI/CD pipeline design. Use when the task involves glab commands (mr, issue, ci, job, release, repo, api, variable, schedule, token, snippet, cluster, stack, duo, mcp), writing or debugging .gitlab-ci.yml pipeline YAML (stages, rules, workflow, needs, artifacts, cache, include, extends, spec inputs, id_tokens, trigger, environment, services, parallel matrix), designing CI/CD pipelines end-to-end (DAG, parent-child and multi-project pipelines, merge request pipelines, merge trains, environment promotion, review apps, rollback), CI/CD components and the catalog, GitLab Runner selection and tags, pipeline security (OIDC id_tokens, CI_JOB_TOKEN allowlists, protected branches/environments/variables, masked variables), or troubleshooting pipelines that don't trigger, jobs stuck pending, or "yaml invalid" errors.

Local-first meta-agent orchestrator for Dev and Ops tasks. Use when the user asks to run opsman, orchestrate a multi-skill task, check opsman status, or wants a test-driven, evidence-gated execution loop that discovers local skills, selects a team, plans, implements, and validates command evidence. Triggers: opsman, orchestrate, meta-agent, orchestrator, run lifecycle, evidence-gated validation, capability map, skill registry.

Expert Google Cloud CLI guidance. Use when the task involves gcloud commands or the Google Cloud SDK — installing or updating the CLI and components (bq, gsutil, kubectl, gke-gcloud-auth-plugin, alpha/beta), gcloud init, authentication issues (gcloud auth login vs application-default ADC, "could not find default credentials", service account keys, --impersonate-service-account, workload identity federation, headless/CI login), named configurations and switching projects, config properties and CLOUDSDK_* env vars, scripting gcloud with --format/--filter/--quiet, proxy or custom CA setup, or any GCP resource work driven through the gcloud CLI (compute, GKE, IAM, storage, run, logging).

Expert GitHub guidance covering the gh CLI, GitHub Actions, and repository management. Use when the task involves gh commands (repo, pr, issue, run, workflow, release, api, secret, ruleset, extension), writing or debugging GitHub Actions workflow YAML, designing CI/CD pipelines and deployment processes (stages, environment promotion, blue/green, canary, rollback), workflow triggers, matrix builds, caching, reusable workflows, building custom actions (composite, TypeScript/JavaScript, Docker, action.yml), Actions security (SHA pinning, permissions, script injection, pull_request_target, OIDC, secrets), or managing repos with branch protection, rulesets, CODEOWNERS, labels, releases, GHCR packages, webhooks, or the REST/GraphQL API.

Expert guide for agentgateway, the Linux Foundation AI-native proxy data plane (Rust, originally built by Solo.io, also used as kgateway's data plane). Covers MCP (Model Context Protocol) tool federation and multiplexing, A2A (agent-to-agent) proxying, multi-provider LLM/AI gateway routing (virtual models, weighted/failover/conditional routing, cost tracking), general HTTP/gRPC traffic management, security policies (JWT, OIDC, API key, CEL-based authorization, backend auth, rate limiting, TLS), observability (metrics, OpenTelemetry tracing, logging, admin UI), standalone binary/Docker configuration, and Kubernetes installation via Helm charts, Gateway API, and the AgentgatewayBackend/AgentgatewayPolicy CRDs. Use when the user mentions agentgateway, agentgateway.dev, MCP proxy/gateway/federation, A2A agent proxying, LLM gateway routing, AI gateway, virtual models, or asks an AI Gateway/MCP/LLM/agent-connectivity question that kgateway's own docs point elsewhere for.

Generic fallback implementer for opsman runs. Make the smallest code or configuration change that satisfies predefined acceptance checks — edit source files, fix bugs, add features or endpoints, refactor, update configuration, write or adjust tests — when no domain-specific skill matches the task. Triggers: implement, fix, add, change, modify, refactor, patch, write code, bug, feature, script, configuration, test.

Basic fixture skill

Skill api-design for testing.

Skill frontend-design for testing.

Skill shared for testing.

Skill code-review for testing.

Skill convex-best-practices for testing.

Skill kubernetes-ops for testing.

Skill writing for testing.

Turn a development goal into a dense sddx spec — binary success criteria, a mandatory oracle, stop rules — and register it as a task. Use when the user wants to plan or spec out a task before executing it.

Flagship sddx flow — decompose a goal into oracle-backed task specs and run them through TDD loops in parallel git worktrees, each ending in a verified, hash-chained receipt. Use for multi-task goals or any task that should run isolated from the current checkout.

Run a single sddx task through the PLAN → RED → GREEN → REFACTOR → VERIFY loop. Use when the user asks to execute one small, well-scoped task with spec-driven TDD.

Execute a task's oracle and, on pass, produce the hash-chained receipt and atomic commit. Use when an sddx task reaches VERIFY or the user asks to verify a task.

Ship a done goal as one PR of cherry-picked commits. Use when asked to open a PR for /sddx:run goals.

Verify the receipt hash chain, commit bindings, and (optionally) commit signatures. Use when the user asks to audit sddx receipts or check the integrity of completed work.

Regenerate .sddx/BOARD.md and show task status across the repo and its worktrees. Use when the user asks for sddx status, the board, or task progress.

Manage the full release lifecycle for the Rune task runner — cut a release, ship a version, publish a tag, promote a release candidate, decide the version bump, preview the changelog, trigger the GitHub Release workflow, watch it, verify the published artifacts, or recover a failed/partial release. Use this whenever the user mentions releasing, shipping, cutting a version, tagging, bumping the version, an rc / release candidate, promoting an rc to stable, the changelog, GoReleaser, or the Release workflow — even if they don't say "release-guru". Rune-specific: knows the stable-tag-derived versioning, the pre-1.0 bump rules, git-cliff changelog, and the cosign/attestation verification.