{
  "markdown": "# twingate-assistant\n\nA Claude Code plugin that gives Claude Code deep Twingate ZTNA expertise — architecture design, deployment playbooks, IaC generation, and troubleshooting. Once installed, every Claude Code session can act as a Twingate solutions engineer: it assesses your environment, designs Remote Networks, generates Terraform or Pulumi, and walks you through deployments on AWS, Azure, GCP, or Kubernetes.\n\n---\n\n## Install\n\nIn Claude Code, add the marketplace and install the plugin:\n\n```bash\n/plugin marketplace add Twingate-Solutions/twingate-assistant\n/plugin install twingate-assistant@twingate-solutions\n```\n\nThat's all. The plugin loads automatically in every future Claude Code session.\n\nTo update later, re-run the same `/plugin install` command — it pulls the latest version.\n\n---\n\n## Use it\n\nThe plugin adds two things to Claude Code:\n\n- **Skills** — domain expertise that loads automatically when relevant topics come up (e.g. mention \"connector\" and `twingate-connectors` activates).\n- **Agents** — orchestrators you invoke explicitly by name for end-to-end workflows.\n\n### Plan a new deployment\n\n```text\nUse the twingate-se agent to help me deploy Twingate to my AWS environment.\n```\n\nThe senior SE agent runs a structured environment assessment, produces a network design, and generates IaC.\n\n### Document an existing deployment\n\nIf Twingate is already in place, create a context file once so future sessions skip re-asking:\n\n```text\nUse the twingate-se agent to document my current Twingate deployment as twingate-context.md.\n```\n\nCommit the resulting file. Future sessions will pick it up automatically. Template: [`docs/twingate-context-template.md`](docs/twingate-context-template.md).\n\n### Troubleshoot\n\n```text\nUse the twingate-troubleshoot skill. My users can't reach a resource that was working yesterday.\n```\n\n### Generate IaC for a specific cloud\n\n```text\nUse the aws-deployer agent to generate Terraform for two HA connectors in us-east-1.\n```\n\n```text\nUse the azure-deployer agent to deploy connectors as Azure Container Instances with Entra ID auth.\n```\n\n---\n\n## Skills\n\nSkills load automatically when Twingate topics are detected, or you can invoke explicitly with `/skill <name>`.\n\n| Skill | What it covers |\n| --- | --- |\n| `twingate-architect` | Core ZTNA architecture, Remote Networks, Resources, design patterns |\n| `twingate-connectors` | Connector deployment, HA, upgrades, metrics, logging |\n| `twingate-terraform` | Terraform provider, resource definitions, secrets management |\n| `twingate-pulumi` | Pulumi provider — TypeScript, Python, Go, C# |\n| `twingate-kubernetes` | Helm chart, Kubernetes operator, CRDs, traffic routing |\n| `twingate-idfw` | Identity Firewall — SSH PAM, Kubernetes gateway, session recording |\n| `twingate-identity` | IdP integration, SCIM, security policies, device trust, JIT |\n| `twingate-api` | GraphQL API, CLI tools, automation scripts |\n| `twingate-dns-security` | DNS filtering, exit networks, DNS-over-HTTPS |\n| `twingate-troubleshoot` | Diagnostics — connector failures, access failures, policy issues |\n\n---\n\n## Agents\n\nAgents orchestrate multiple skills for end-to-end workflows. Invoke them by name.\n\n| Agent | When to use |\n| --- | --- |\n| `twingate-se` | Starting any Twingate deployment or major change — environment assessment, network design, end-to-end deployment |\n| `aws-deployer` | Deploying connectors on AWS (ECS, EC2, IAM, Secrets Manager) |\n| `azure-deployer` | Deploying connectors on Azure (ACI, VMs, Key Vault, Entra ID) |\n| `gcp-deployer` | Deploying connectors on GCP (Cloud Run, GCE, Secret Manager, Google Workspace) |\n| `network-designer` | Planning a new Twingate network before writing IaC — resource strategy, security tiers, output tables |\n| `idfw-deployer` | Implementing certificate-based SSH PAM or kubectl proxy access |\n\nExample invocations:\n\n```text\nUse the aws-deployer agent to help me set up HA connectors in us-west-2.\n```\n\n```text\nUse the network-designer agent to plan our resource structure for three environments.\n```\n\n---\n\n## How it stays current\n\nEach skill has a `references/` directory of summarized Twingate documentation. A weekly GitHub Action refreshes those summaries from the Twingate docs site, the Twingate help center, and the public `Twingate`, `Twingate-Solutions`, `Twingate-Labs`, and `Twingate-Community` GitHub orgs (repos and wikis), so the plugin always reflects current Twingate behavior. No action needed on your end — just re-run `/plugin install` occasionally to pull updates.\n\n---\n\n## Forking, customizing, contributing\n\nWant to fork this plugin and customize it for your own organization, run the pipeline against your own docs, or extend it for a Twingate-adjacent product? See [`docs/MAINTAINING.md`](docs/MAINTAINING.md).\n\nWant to contribute back upstream? See [`CONTRIBUTING.md`](CONTRIBUTING.md).\n\n---\n\n## License\n\nApache 2.0 — see [LICENSE](LICENSE).\n",
  "bytes": 4910,
  "sha": "eaabff82089a2fdde47dd17676a236c15e642548a5ab1c2d13fb9a6a9feff390",
  "repo_slug": "twingate-solutions/twingate-assistant",
  "fonte": "repo",
  "truncated": false,
  "api": "https://api.agentalog.com/api/listings/skl_twingate_solutions_twingate_assistant_tw_6dac9a2a/readme"
}