advisor
Advisor mode. Consult a stronger (or different) model at key checkpoints: before major…
Walk a user through connecting Grok Bot to their Tailscale tailnet - define tag:grokbot in the tailnet policy file, grant it only the MCP hosts and ports it should reach, sign in from the Tailscale plugin, approve the device, then add tailnet MCP servers. Use when the user asks
$ npx -y skills add cursor/plugins --skill tailscale-setup --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/tailscale-setupContext preview
The summary Claude sees to decide when to auto-load this skill.
Walk a user through connecting Grok Bot to their Tailscale tailnet - define tag:grokbot in the tailnet policy file, grant it only the MCP hosts and ports it should reach, sign in from the Tailscale plugin, approve the device, then add tailnet MCP servers. Use when the user asks
name: tailscale-setup description: Walk a user through connecting Grok Bot to their Tailscale tailnet - define tag:grokbot in the tailnet policy file, grant it only the MCP hosts and ports it should reach, sign in from the Tailscale plugin, approve the device, then add tailnet MCP servers. Use when the user asks to set up, troubleshoot, or disconnect Grok Bot's Tailscale connection.
Grok Bot joins the user's tailnet as one device tagged `tag:grokbot`. It can reach only the hosts and ports the tailnet policy file grants to that tag, so set up the policy before signing in.
In the Tailscale admin console, open **Access controls** and edit the policy file:
{
"tagOwners": {
"tag:grokbot": ["autogroup:admin"],
},
"grants": [
{
"src": ["tag:grokbot"],
"dst": ["mcp-server.tail1234.ts.net"],
"ip": ["tcp:443"],
},
],
}Merge these keys into the existing policy instead of replacing it. Use the user's real host names, `100.x` addresses, or tags in `dst`, and the ports their MCP servers listen on in `ip`. If the policy still has the default allow-all rule, `tag:grokbot` can reach every device; point that out and suggest narrowing it.
1. Open the **Tailscale** plugin in Grok Bot and click **Authenticate**. 2. Sign in to Tailscale and approve the new device. 3. If device approval is on for the tailnet, approve the device on the **Machines** page of the admin console. 4. If the tailnet uses Tailnet Lock, sign the device from a signing node (`tailscale lock sign <node-key>`). It cannot reach anything until it is signed.
Add each MCP server as usual, using its `*.ts.net` name or `100.x` address as the URL host. Requests to that host go over the tailnet.
Only messages from the bot owner and linked teammates, and routines the owner schedules, can use the tailnet. Other people messaging the bot cannot.
Click **Remove** on the Tailscale plugin page in Grok Bot.
Official Cursor plugins for popular developer tools, frameworks, and SaaS products. Each plugin is a standalone directory at the repository root with its own .cursor-plugin/plugin.json manifest.
Repo: cursor/plugins
Advisor mode. Consult a stronger (or different) model at key checkpoints: before major…
Run the full repository compatibility pass: scanner score, startup path, validation loop, and…
Designs or reviews CLIs so coding agents can run them reliably: non-interactive flags,…
Orchestrate continual learning by delegating transcript mining and AGENTS.md updates to…
Create a new Cursor plugin scaffold with a valid manifest, component directories, and…
Audit a Cursor plugin for marketplace readiness. Use when validating manifests, component…