codingthefuturewithai/teamcraft-glgd:teamcraft-setup

Goal

Get Teamcraft GLGD fully operational. That means two MCP servers working — GitLab and Google Drive — and the right companion plugins installed. This skill verifies each connection, guides through setup if anything is missing, and leaves the user ready to run any other Teamcraft skill.

Run this once when first installing the plugin. Re-run it anytime a connection stops working.

Step 1: Understand the User's Context

Before verifying any connections, understand who is setting up and what they need. Ask:

"Before we start, a couple of quick questions so I can tailor the setup:

1. What kind of work will you be doing with Teamcraft? (e.g., writing code, planning projects, managing requirements, a mix of everything)
2. Are you running this in Claude Code or Claude Cowork?"

What this tells you:

• What they do determines which tools matter. If they write and ship code, they'll need the full build loop and LSP plugins. If they focus on planning, requirements, or documentation, they only need GitLab MCP and Google Drive MCP — upstream skills don't require build loop tools.
• Environment determines how to guide MCP setup if something is missing. In Claude Code, the claude mcp add CLI works. In Claude Cowork, MCP servers must be configured in Claude Desktop's config file — follow references/cowork-mcp-setup.md.

Store what you learn for the rest of the setup flow. If the user's answers make it obvious (e.g., "I'm planning sprints in Cowork"), don't ask redundant follow-ups.

Step 2: Verify GitLab MCP

First confirm basic connectivity by calling mcp__gitlab__list_projects. If that fails, go straight to references/gitlab-mcp-setup.md.

If connectivity succeeds, the server is running but may be missing required tool subsets. Teamcraft depends on specific env vars that are not set by default. Spot-check each subset by attempting a lightweight call:

| Tool to call | Required env var | What Teamcraft uses it for | |---|---|---| | mcp__gitlab__list_milestones (any project ID) | USE_MILESTONE=true | Sprint containers — every sprint planning session | | mcp__gitlab__list_pipelines (any project ID) | USE_PIPELINE=true | CI/CD health monitoring | | mcp__gitlab__execute_graphql (minimal query) | GITLAB_TOOLS=execute_graphql | Advanced project queries | | mcp__gitlab__list_wiki_pages (any project ID) | USE_GITLAB_WIKI=true | Project orientation in onboard |

For each call: if the tool responds (even with an empty list or API error), that subset is exposed and the env var is set. If the call fails with a "tool not found" or "unknown tool" error, that env var is missing.

Report which subsets passed and which failed. For any failure, follow references/gitlab-mcp-setup.md — the reconfiguration section shows the exact fix.

Step 3: Verify Google Drive MCP

Call mcp__google-drive__list_accounts. Any response means the server is reachable.

• No accounts returned — Drive MCP is reachable but no Google account is authenticated. Follow references/google-drive-mcp-setup.md.
• One account — confirm it to the user and move on.
• Multiple accounts — present them and ask which one they primarily use for project work.
• Call fails entirely — follow references/google-drive-mcp-setup.md.

Step 4: Check Companion Plugins

Based on the environment from Step 1:

Claude Code

Run claude plugin list and check for the following. If missing, tell the user what's needed and why. Do not assume specific install commands are correct — plugin registries and install mechanisms evolve. Name the plugin and let Claude Code guide the installation.

frontend-design — discover-problem uses it for client-facing HTML mockups. Without it the session still works but visuals look generic.

context7 — plan-and-implement-issue uses it for real-time library documentation during technical research. Without it, tech research falls back to training data. Note: context7 may be available as a plugin or as an MCP server — check both if one doesn't work.

LSP plugins — Only if the user writes code. Follow references/lsp-plugins.md.

Cowork

Tell the user which plugins are needed and why. Help them figure out how to install plugins in their Cowork environment.

Step 5: Done

Summarize what's working and what (if anything) was skipped or still needs attention. Then let the user know setup is complete and Teamcraft is ready to use.

If the user asks what to do next, point them to teamcraft-glgd:learn-teamcraft for a walkthrough of available skills. Don't steer them toward a specific activity — that's their call.