---
name: find-skill
description: >-
  Meta-skill and entry point for the tidb-gtm-skills pack. Describe what you
  are trying to accomplish in plain language — a content goal, a role, or a
  situation — and get back the right skill(s) to use, in order, with the brain
  files to load. Use this when you are new to the system or unsure where to
  start.
---

# find-skill — your entry point into the TiDB GTM skills pack

**Role:** Navigator. You take the user's goal or situation, match it to the right skill(s) in the pack, and hand them a ready-to-run starting point — skill file path, brain files to load, and a one-sentence reason for the recommendation.

This skill does not produce GTM content. It tells you exactly which skill does.

---

## How to use this skill

Describe your situation in plain language. Any of these forms work:

- **By output:** "I need to write a technical blog post about TiDB's HTAP capabilities."
- **By role:** "I'm a PMM starting a new messaging cycle — where do I begin?"
- **By situation:** "I'm preparing for KubeCon and need event materials."
- **By problem:** "My team keeps saying 'TiDB Serverless' and I need to fix our naming."
- **By question:** "How do I compare TiDB against Aurora for a prospect?"

Then follow the recommended path below.

---

## Before you write: two editorial filters

If your goal is to create blog or article content, run it through two quick tests before picking a content skill. They catch posts that shouldn't exist before any effort goes in.

- **The topic test.** Would this piece still be valuable to the reader if TiDB didn't exist? If yes, it's not for our blog (it belongs in generic content marketing). If no — the reader needs it *because* of a TiDB-relevant problem — it probably belongs here.
- **The reader contract.** Finish this sentence in one line: *"After reading this, the reader can ______."* A specific answer ("decide whether to migrate from Aurora to TiDB," "build a RAG pipeline on TiDB," "explain how HTAP works to their team") means the piece has earned the reader's time. A vague answer ("learn about TiDB") means it hasn't — sharpen the angle before you start.

---

## Quick match: describe your goal

### "I need to create content right now"

| What you need to create | Skill to use | Brain files to load |
|------------------------|-------------|-------------------|
| Technical blog, migration story, AI tutorial | `tidb-tech-story` | `knowledge/product.md`, `playbooks/messaging.md` |
| Customer case study, customer win, proof point story | `tidb-case-study` | `knowledge/product.md`, `playbooks/messaging.md`, `playbooks/benchmark-standards.md` |
| LinkedIn, Twitter/X, WeChat, 知乎, newsletter post | `tidb-channel-copy` → `tidb-content-review` | `playbooks/messaging.md` |
| GitHub README narrative, HN Show HN, community announcement | `tidb-developer-story` → `tidb-content-review` | `knowledge/product.md` |
| Strategic essay, exec column, keynote narrative | `tidb-thought-leadership` | `playbooks/messaging.md`, `knowledge/product.md` |
| Event or field campaign brief | `tidb-field-brief` → `tidb-channel-copy` → `tidb-content-review` | `knowledge/icp.md`, `playbooks/messaging.md` |
| Benchmark or performance claim content | `tidb-benchmark-narrative` → `tidb-messaging-review` | `playbooks/benchmark-standards.md`, `knowledge/product.md` |

### "I need to check or review something"

| What you need to check | Skill to use | Brain files to load |
|----------------------|-------------|-------------------|
| Is this content ready to publish? | `tidb-content-review` | `playbooks/messaging.md`, `knowledge/product.md` |
| Is our messaging platform accurate and evidence-backed? | `tidb-messaging-review` | `playbooks/messaging.md`, `knowledge/product.md` |
| Is our GTM brief grounded in real signals? | `tidb-strategy-review` | *(no brain file required)* |
| Is our brand naming and voice correct? | `tidb-brand-voice` | `knowledge/product.md` |
| Does this deliverable follow TiDB visual standards? | `tidb-brand-visual` | `knowledge/brand.md` |
| How does our GTM content compare to industry leaders? | `tidb-gtm-benchmark` | `knowledge/competitors.md` |

### "I need to build strategy or positioning"

| What you need to build | Skill to use | Brain files to load |
|----------------------|-------------|-------------------|
| Full messaging platform (positioning, value props, taglines) | `tidb-messaging-platform` | `knowledge/product.md`, `knowledge/icp.md`, `knowledge/competitors.md`, `playbooks/messaging.md` |
| GTM brief (motion, ICP priority, channels, metrics) | `tidb-gtm-brief` → `tidb-strategy-review` | `knowledge/icp.md`, `knowledge/competitors.md` |
| ICP segment analysis | `tidb-icp-synthesis` | `knowledge/icp.md` |
| Competitive positioning map | `tidb-competitive-map` | `knowledge/competitors.md` |
| Product narrative brief (PM → PMM handoff) | `tidb-product-narrative` | `knowledge/product.md` |
| Launch plan (timeline, channels, assets, metrics) | `tidb-launch-brief` | `playbooks/messaging.md` |
| Multi-market launch coordination (e.g., CN + global) | `tidb-gtm-brief` → `tidb-strategy-review` → `tidb-field-brief` | `knowledge/icp.md`, `knowledge/competitors.md`, `playbooks/messaging.md` |

---

## Quick start by role

**GTM Strategy** — start at Stage 0, work upstream to downstream:
1. `tidb-icp-synthesis` → `tidb-competitive-map` → `tidb-gtm-brief` → `tidb-strategy-review` → `tidb-launch-brief`

**PMM** — own messaging and content quality:
1. `tidb-competitive-map` → `tidb-messaging-platform` → `tidb-messaging-review` → `tidb-content-review`
2. For performance content: add `tidb-benchmark-narrative` before `tidb-messaging-review`
3. For executive content: `tidb-thought-leadership`
4. For quarterly content quality audit: `tidb-gtm-benchmark` (competitor PMM analysis + TiDB gap review)

**Product Manager** — provide the facts layer before the messaging cycle:
1. `tidb-product-narrative` → sign off on `tidb-strategy-review` + `tidb-messaging-review`

**Growth** — distribution and channel:
1. `tidb-channel-copy` → `tidb-content-review`
2. For campaigns: `tidb-launch-brief` → `tidb-field-brief` → `tidb-channel-copy`

**Field Marketing** — events and regional:
1. `tidb-field-brief` → `tidb-channel-copy` → `tidb-content-review`

**Field Sales / Account Management** — deal-cycle external communication:
1. Competitive or objection handling narrative: `tidb-competitive-map` → `tidb-channel-copy`
2. Benchmark or performance proof asks: `tidb-benchmark-narrative` → `tidb-messaging-review`
3. Customer expansion / renewal campaign messaging: `tidb-gtm-brief` → `tidb-channel-copy` → `tidb-content-review`

**Solutions Engineer** — technical workshop and POC communication:
1. Event/workshop briefing: `tidb-field-brief` → `tidb-tech-story` → `tidb-content-review`
2. Competitive technical comparisons: `tidb-competitive-map` → `tidb-content-review`

**DevRel / Technical Writer** — technical credibility content:
1. `tidb-tech-story` or `tidb-developer-story` → `tidb-content-review`
2. For performance content: `tidb-benchmark-narrative` first
3. Always load `tidb-brand-voice` — naming accuracy matters

---

## Decision tree for common situations

```
What's your situation?
│
├── "I need to write something for external publishing"
│   ├── Technical / engineering audience → tidb-tech-story → tidb-content-review
│   ├── Customer story / proof point / case study → tidb-case-study → tidb-content-review
│   ├── Business / executive audience → tidb-thought-leadership → tidb-content-review
│   ├── Developer community (GitHub, HN, Discord) → tidb-developer-story → tidb-content-review
│   └── Social / newsletter / short-form → tidb-channel-copy → tidb-content-review
│
├── "I'm preparing for an event or campaign"
│   ├── Event brief / field campaign → tidb-field-brief → tidb-channel-copy → tidb-content-review
│   ├── Campaign strategy still unclear → tidb-gtm-brief → tidb-strategy-review
│   └── Social copy for the event → tidb-channel-copy → tidb-content-review
│
├── "I need to understand our positioning or ICP"
│   ├── Who is our target customer? → tidb-icp-synthesis → tidb-gtm-brief → tidb-strategy-review
│   ├── How do we compare to competitors? → tidb-competitive-map
│   └── What is our full messaging platform? → tidb-messaging-platform
│
├── "I'm starting a new launch or campaign cycle"
│   ├── Strategy not yet clear → tidb-gtm-brief → tidb-strategy-review → tidb-launch-brief
│   └── Multi-region launch coordination needed → tidb-gtm-brief → tidb-strategy-review → tidb-field-brief
│
├── "I need to review or approve something"
│   ├── Content ready to publish? → tidb-content-review
│   ├── Messaging platform accurate? → tidb-messaging-review
│   └── GTM brief grounded? → tidb-strategy-review
│
├── "I just need to check naming / voice"
│   └── tidb-brand-voice (load knowledge/product.md alongside)
│
└── "I need to apply visual brand to a deliverable (slides, social, ads, docs)"
    └── tidb-brand-visual (load knowledge/brand.md)
```

---

## Full skill inventory (reference)

| Skill | Stage | When to use |
|-------|-------|------------|
| `find-skill` | Foundation | You are here — use this to navigate |
| `tidb-brand-voice` | Foundation | Naming accuracy, voice standards, banned phrases |
| `tidb-brand-visual` | Foundation | Visual identity: colors, typography, logo, Cornerstone, layouts, 74-asset library |
| `tidb-icp-synthesis` | 0 — Intelligence | Synthesize customer signals into ICP cards |
| `tidb-competitive-map` | 0 — Intelligence | Map TiDB position vs Aurora, CockroachDB, Neon, etc. |
| `tidb-gtm-brief` | 1 — Strategy | Motion selection, ICP priority, channel mix, metrics |
| `tidb-strategy-review` | 1 — Gate | Verify GTM brief before execution |
| `tidb-product-narrative` | 2 — Positioning | PM → PMM product context handoff |
| `tidb-messaging-platform` | 2 — Positioning | Full messaging: positioning, value props, taglines |
| `tidb-benchmark-narrative` | 2 — Positioning | Performance claims and benchmark content |
| `tidb-messaging-review` | 2 — Gate | Verify all claims before content creation begins |
| `tidb-launch-brief` | 3 — Launch | Launch timeline, assets, channels, success metrics |
| `tidb-field-brief` | 3 — Launch | Event / regional / partner campaign brief |
| `tidb-tech-story` | 4 — Content | Technical blog, migration story, tutorial |
| `tidb-case-study` | 4 — Content | Customer case study: intake, structure, SEO/GEO optimization, publish |
| `tidb-thought-leadership` | 4 — Content | Strategic essay, exec column, keynote narrative |
| `tidb-channel-copy` | 4 — Distribution | Platform-adapted copy for every channel |
| `tidb-developer-story` | 4 — Distribution | GitHub, HN, community forum, Discord announcement |
| `tidb-content-review` | 4 — Gate | Final check before any external content publishes |
| `tidb-gtm-benchmark` | 0 — Intelligence | Competitor GTM content analysis; gap analysis vs tidb-gtm-skills |

---

## How to load a skill

**Claude Code:**
```
@tidb-gtm-skills/tidb-tech-story/SKILL.md
@tidb-gtm-brain/knowledge/product.md
```

**Cursor / Windsurf / Trae:** use `@file:` workspace reference or open the SKILL.md directly.

**Any AI assistant (ChatGPT, Claude.ai, etc.):** open the SKILL.md file, copy the full content, paste at the start of your conversation.

---

## Pairs with

- All 17 skills in the pack — this skill routes you to them
- `tidb-brand-voice` — always load this or `knowledge/product.md` alongside any content skill