Setup

Setup — Plugin Onboarding

Walk the user through first-time configuration of the marketing skills plugin. Check what's already working, fix what isn't, and finish by recommending skills based on their role.

Be patient and encouraging — many users are marketers, not engineers. Explain what each tool is and why it matters before asking them to configure it. Claude Code users are typically more technical, so adjust your tone accordingly — still helpful, but less hand-holding.

Step 1: Detect runtime and OS

Determine whether you're running in Cowork or Claude Code:

• If the google_drive_search tool is available → Cowork
• Otherwise → Claude Code

Detect the host OS:

echo $CLAUDE_CODE_HOST_PLATFORM

• darwin → macOS
• win32 → Windows
• linux → Linux

Store both for later — they affect install commands and config paths. Almost everyone will be on macOS.

Step 2: Set up Tiger Den (required)

Tiger Den is the content library that all skills depend on for reference docs (brand voice guide, product marketing context, content rubrics, etc.). It's also used for content search and voice profiles.

Try a Tiger Den-specific tool (same in both runtimes):

list_voice_profiles()

Why `list_voice_profiles` and not `search_content`? Other connectors (like Tiger Docs) also expose a search_content tool. list_voice_profiles is unique to Tiger Den, so it won't produce false positives.

If it works: Tell the user Tiger Den is connected and move on to Step 3.

If it fails: Walk them through setting it up using the instructions for their runtime below.

"Tiger Den is our content library — skills use it to find reference docs (like our brand voice guide), search existing content, and write in team members' voices. Let's connect it."

Tiger Den setup in Cowork

Tiger Den is available as a built-in connector in our Claude team environment. No terminal commands, no API keys, no Node.js required.

"Connecting Tiger Den is quick — it's a one-click connector in Claude Desktop:"

>

1. Click the gear icon (⚙️) in the top-right corner of Cowork to open Settings

2. Go to Connectors

3. Find Den.tigerdata.com in the list and click Connect

4. Follow the sign-in prompts to authenticate with your Tiger Data account

>

"Once it's connected, start a new Cowork session (the connector won't be available in this current session). In the new session, type /doctor to verify everything's working."

If the user can't find Den.tigerdata.com in the Connectors list, suggest they check with their team admin — the connector needs to be enabled for the organization.

Tiger Den setup in Claude Code

Tell the user to run this in a separate terminal (not inside Claude Code):

claude mcp add -s user --transport http tiger_den https://den.tigerdata.com/api/mcp/mcp

"Then restart Claude Code — the Tiger Den tools will appear as tiger_den MCP tools."

If it still doesn't work after restart, suggest they check ~/.claude.json and verify the tiger_den entry is present and the URL is correct.

Step 3: Check Google Drive (Cowork only, optional)

Google Drive is no longer required for reference docs (Tiger Den handles that), but some skills like case-study-prep use google_drive_fetch to read user-provided Google Docs. This step is optional.

In Claude Code, skip this step entirely.

In Cowork, try:

google_drive_search(api_query: "'1DUPUkDyG8bkQgoWWI4kvoLTyMk_sT1n2' in parents", page_size: 1)

If it works: Tell the user Google Drive is connected and move on.

If it fails: Let them know it's optional:

"Google Drive is optional — it's only needed if you use skills that read Google Docs (like case-study-prep). If you want to connect it now:"

>

1. Click the gear icon in the top-right corner of Cowork to open Settings

2. Go to Connectors

3. Find Google Drive and click Connect

4. Sign in with your Tiger Data Google account (your @tigerdata.com email)

>

"Or you can skip this and set it up later if you need it."

Step 3.5: Contributor intent (light touch)

Before moving to skill recommendations, ask a quick, low-pressure question to see whether the user plans to contribute changes to the plugin itself. Most first-time users have no context for this, so the phrasing must make "no" or "not sure" feel like the default answer.

Don't try to get them fully set up to contribute inside this step — contributing involves cloning the repo and a few other pieces, and CONTRIBUTING.md is the canonical walkthrough. Your job here is just a signpost, not an onboarding flow.

Ask in plain text (not AskUserQuestion):

"One more quick thing before I point you at skills — do you plan to contribute to skills yourself (editing existing ones or adding new ones)? If you're not sure, say no — you can always come back to this later."

Handle the response:

• No or unsure: Acknowledge briefly ("Cool — skipping that for now.") and move straight to Step 4. Do not bring it up again.
• Yes AND Claude Code: Point them at CONTRIBUTING.md and mention /contributor-setup as one of the pieces it covers. Don't offer to run it here — they may not even have the repo cloned yet:

"Nice. Contributing has a few pieces — installing tools, cloning the repo, then submitting a PR. CONTRIBUTING.md has the full walkthrough. Once you've cloned the repo, you can run /contributor-setup inside that session to handle the gh CLI and git config in one shot. And when you're ready to submit changes, just tell Claude you're done — /skill-contributor will take it from there."

Continue to Step 4.

• Yes AND Cowork: Same redirect to CONTRIBUTING.md; /skill-contributor handles submission in Cowork:

"Nice. Contributing has a few pieces (installing tools, cloning the repo, submitting a PR). CONTRIBUTING.md has the full walkthrough. When you're ready to submit changes, run /skill-contributor in a Cowork session with the repo folder selected, and it'll walk you through everything."

Continue to Step 4.

Step 4: Skill recommendations

Once Tiger Den is connected (the only required check), ask the user to describe what they do. Don't use AskUserQuestion — just ask in plain text so they can answer naturally:

"Everything's set up! One last thing — tell me a bit about what you do. What kind of work do you spend most of your time on? That'll help me point you to the most useful skills in this plugin."

Let them answer however they want — job title, a description of their day-to-day, specific tasks they're hoping to speed up, whatever. Then recommend skills based on what they said.

How to pick recommendations

Look at the available skills from the tigerdata-marketing-skills plugin (not skills from other plugins). For each skill, read its name and description. Pick the 3-5 skills that are the best match for what the user described.

Skip these utility skills — they're useful but not worth recommending during onboarding. The user will discover them when they need them:

• setup (they're already running it)
• doctor (mentioned at the end)
• skill-contributor (only relevant when submitting changes to the repo)
• de-slop (niche editing tool, not a starting point)

Platform filtering: If the user is on Cowork, only recommend skills whose platforms list includes cowork. Same for Claude Code. (You detected the platform in Step 1.)

How to present recommendations

Present them conversationally, not as a wall of text. For each skill, give one sentence on what it does and a quick example of when they'd reach for it. Tailor the examples to what the user told you about their work — if they said they write blog posts, the example for content-reviewer should mention blog posts, not white papers.

End with:

"You can use any of these by just describing what you need — or if you want to run a specific skill, type /skillname (like /content-reviewer or /brand-voice-writer). And if you ever want to check that everything's still connected, just type /doctor."

Tone

Warm, patient, non-technical for Cowork users. These are marketers setting up developer tools. Celebrate each step. Never assume they know what a terminal is — explain it the first time you mention it.

For Claude Code users, be more concise and direct — they're comfortable with the terminal.