← all publishers

twingate-solutions

@twingate-solutions source repo

10 published skills

  1. Twingate API · twingate-solutions bundle
    Twingate GraphQL API, CLI tools, and automation. Load when the user wants to automate Twingate via the API, write scripts against the GraphQL endpoint, generate or manage API tokens, use the Twingate CLI tools, or build automation pipelines. Also trigger on 'GraphQL', 'X-API-KEY', 'Twingate API', 'api/graphql', 'service account key', 'connector token provisioning', 'rate limiting', or any Twingate admin API mention. Also activate for: AWS tag-driven resource automation (EC2/ECS/RDS tag sync, Lambda, EventBridge/CloudWatch Events), a web UI for the Twingate CLI (tgcli-web, FastAPI, Docker/Kubernetes), the Twingate GitHub Action for CI runners, Jupyter/Python API tutorials, or generating a network health/insights report from a Network Events export.
    0
    installs
  2. Twingate Idfw · twingate-solutions bundle
    Use for the Twingate Identity Firewall (IDFW) and Twingate Gateway — protocol-level identity enforcement for SSH, the Kubernetes API, AND self-hosted/internal web apps, not just network access. LOAD when the user wants to grant, secure, SSO into, or audit a self-hosted/internal web app — identity forwarding/injection into HTTP requests, per-request audit trails. Gateway = Layer 7 reverse proxy injecting ES256 JWTs (Gateway Access Tokens) or trusted headers: JWKS verification, request-header injection, framework middleware (Express, Django, Next.js, Auth.js), no-code SSO (Grafana, Jenkins). Covers Gateway deployment; SSH privileged access with short-lived certs; vendor/contractor access; Certificate Authorities (X.509/SSH CA, local or Vault); kubectl via the Gateway; Terraform/Ansible automation; session recording (.cast playback, scanning for dangerous commands/leaked secrets). Assume this skill for "can Twingate pass the user's identity to my app?", "audit who used this app", or "SSO for my internal tool".
    0
    installs
  3. Twingate Pulumi · twingate-solutions bundle
    Use when the user writes, debugs, or reviews Twingate Pulumi code in any language (TypeScript, Python, Go, C#/.NET). Activate on mentions of Pulumi, pulumi-twingate, @pulumi/twingate, or pulumi_twingate, or when an existing Pulumi stack needs to add Twingate resources. Also trigger when the user is migrating from Terraform to Pulumi for Twingate, or building a multi-language Pulumi stack that needs Twingate provisioning. Also trigger for local-plugin build/install errors (`pulumi plugin install`, 404 on `pulumi up`/`pulumi preview`, `+dirty`/alpha version strings), or requests for SE reference quick-start Pulumi scripts per cloud.
    0
    installs
  4. Twingate Identity · twingate-solutions bundle
    Use when the user asks about IdP integration, SCIM provisioning, security policies, device trust, groups, users, or access control in Twingate. Activate for: SAML, SCIM, Okta, Entra ID, Google Workspace, JumpCloud, OneLogin, Keycloak, device trust, device posture, MFA enforcement, groups, JIT access, ephemeral access, auto-lock, offboarding, deprovisioning, multi-IdP deployments, or security policy configuration. Also activate for identity automation tooling: automating device trust from an MDM or EDR inventory (Jamf, Kandji, Intune, CrowdStrike, SentinelOne, FleetDM, Automox, JumpCloud, Mosyle, Datto RMM), migrating group access between IdPs, self-service or Slack-based group access requests, and location-based group switching.
    0
    installs
  5. Twingate Architect · twingate-solutions bundle
    Use when the user asks how Twingate works, wants to design or evaluate a Twingate deployment, needs to understand components (Controller, Client, Connector, Relay), or is planning a ZTNA rollout. Activate for: zero trust, ZTNA, remote access architecture, network design with Twingate, VPN replacement, microsegmentation, split DNS, NAT traversal, P2P vs Relay, Remote Network topology, Resource definition strategy, or deployment sequencing. Also activate for community/reference deployment patterns: exposing a self-hosted AI chat assistant (OpenClaw, WhatsApp/Telegram bots) with no public inbound ports, private Railway/PaaS app deployment with zero-ingress, or "what does the twingate-assistant plugin itself do" meta-questions.
    0
    installs
  6. Twingate Terraform · twingate-solutions bundle
    Use when the user writes, debugs, or reviews Twingate Terraform configuration. Activate for any .tf file that touches Twingate resources, the Twingate Terraform provider, IaC provisioning of Remote Networks, Connectors, Resources, Groups, or Service Accounts, provider version questions, and terraform apply errors involving Twingate. Also trigger when existing AWS, Azure, GCP, or Kubernetes Terraform stacks need to add Twingate. Also trigger for provider source/schema questions (`internal/provider/`), `group_ids` / `access` block migration errors, provider release version and changelog questions, or requests for SE reference quick-start Terraform modules per cloud.
    0
    installs
  7. Twingate Connectors · twingate-solutions bundle
    Use when the user needs to deploy, configure, upgrade, or troubleshoot Twingate Connectors on any platform. Activate for: Docker connector, Linux connector, systemd connector, ECS connector, Azure Container Instances, GCE, Helm chart connector, connector tokens, connector HA, connector health, connector metrics, connector logging, connector upgrades, DEAD_NO_RELAYS, DEAD_NO_HEARTBEAT, or connector placement questions. Also activate for connector deployment tooling and unofficial platform support: Raspberry Pi, Ubiquiti/UniFi (UDM Pro, UDM SE, UXG) gateways, Unraid, Home Assistant, Steam Deck / Decky Loader, Hyper-V, Chocolatey packaging, custom or hardened connector containers, GitHub Codespaces, Coder workspaces, render.com, Spacelift CI runners, connector log shipping to S3, connector fleet autoscaling, Grafana connector dashboards, PagerDuty connector alerting, or Docker container auto-updating for connector hosts.
    0
    installs
  8. Twingate Kubernetes · twingate-solutions bundle
    Use when the user deploys Twingate in Kubernetes, uses the Twingate Helm chart or operator, manages TwingateResource or TwingateRemoteNetwork CRDs, routes traffic from cluster pods outward through Twingate, gates kubectl access via Twingate, or integrates Twingate into a GitOps workflow. Also trigger when an existing K8s stack needs connector deployment, token secret management, or declarative Twingate resource definitions. Also trigger for Helm chart `values.yaml` fields, operator CRD kinds (`TwingateConnector`, `TwingateResource`, `TwingateResourceAccess`, `TwingateGroup`, `TwingateGateway`, `TwingateCertificateAuthority`), kubeconfig sync automation, or running the Twingate headless client as a Kubernetes sidecar container.
    0
    installs
  9. Twingate Dns Security · twingate-solutions bundle
    Twingate Internet Security — DNS filtering, exit networks, browser security, and DNS-over-HTTPS. Load when the user mentions DNS filtering, content filtering, internet security, exit networks, egress routing, browser security, NextDNS, DoH, DNS categories, or profile priority. Also trigger on 'Internet Security', 'DNS Security Profile', 'fixed egress IP', or 'SaaS allowlisting' in a Twingate context. Also activate for DNS conflicts and symptom-shaped DNS queries: a third-party DNS filter or AV product conflicting with Twingate (Cisco Umbrella, DNSFilter, AdGuard, Avast Real Site Protection), CGNAT range conflicts (`100.96/12`), multiple-network-interface DNS resolution problems, "all nameservers have failed", DNS request delays on Linux, a Docker container's second DNS query returning the wrong IP, or a personal/DIY exit-network VPN built on Twingate.
    0
    installs
  10. Twingate Troubleshoot · twingate-solutions bundle
    Use when the user reports connectivity issues, access failures, DNS resolution problems, or any error with Twingate. Activate for: "can't connect", "not working", "resource not found", "access denied", DEAD connector, DNS not resolving, device-trust blocks, security policy issues, P2P failure, or any Twingate diagnostics. Also activate for symptom-shaped queries: exact client error text ("unknown network name", "too many open files", "setup wizard ended prematurely", "unable to join network"), OS-specific client bugs on Windows, macOS, Linux (Fedora, Ubuntu, NixOS), ChromeOS, or Android Auto; client crashes, freezes, or unresponsiveness; version-specific regressions (a specific build misbehaving); TAP/virtual network adapter issues; device posture, screen-lock, or disk-encryption failures; third-party AV/EDR/VPN/DNS-filtering conflicts (CrowdStrike, Zscaler, Elastic AV, Avast, consumer VPNs); packet capture, system reports, client/connector logs; and engaging or escalating to Twingate technical support.
    0
    installs