菜单
Creates or updates a competitor battlecard. Use when the user needs positioning, strengths, weaknesses, objections, win conditions, and practical talk tracks saved into competitive knowledge.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill when the user wants to submit, contribute, or publish a GTM skill to the GTM Skills library (github.com/swan-gtm/gtm-skills, gtmskills.com), or update one of their existing skills or their creator profile there.
Use this skill when [the concrete trigger — a signal fires, a moment in the deal, a recurring cadence]. Produces [the concrete output]. [One or two more sentences dense with the phrases someone would actually say when they need this.]
Use this skill when a deal closes won and you want to turn the win into pipeline immediately. It extracts the win profile, finds lookalike companies not yet in your CRM, researches the right persona contact at each, drafts outreach from the deal owner using an anonymized win reference, and queues a single batch review task — nothing sends without human approval.
Use this skill when scoring a paying customer (closed-won account) for expansion. It evaluates product usage depth, persona quality, and expansion headroom to produce an expansion tier with short actionable reasoning. Designed as a sub-skill of your lead-scoring methodology — the parent runs the ACV assessment first and this returns a tier to it.
Use this skill when a profile-view webhook (e.g. LeadShark) fires for a new view on a team member's LinkedIn profile. It resolves the viewer's identity and company, applies dedup, internal, relationship, and ICP gates, and routes qualified viewers into the MQL pipeline — treating a profile view exactly like a website visit. The CRM is never polluted: only fully resolved, ICP-matched viewers reach a CRM write.
Use this skill when a tracked influencer publishes a LinkedIn post focused on your product (sponsored, review, or organic mention) and you want to capture the engagers as leads. It verifies the post is genuinely about you, scrapes the full engager list, filters to ICP-fit companies and buyer personas, runs lead scoring, and posts per-lead alerts plus a reconciled digest. Detection and scoring only — no outreach.
| name | battlecard |
| title | Battlecard |
| description | Creates or updates a competitor battlecard. Use when the user needs positioning, strengths, weaknesses, objections, win conditions, and practical talk tracks saved into competitive knowledge. |
| category | Research |
State check. This skill assumes the org has at least basic positioning established — a value prop and competition notes saved to org knowledge. Load org competition knowledge via swan-get-memory. If there's no competition slot at all and no value prop on file, the battlecard will end up generic — build out positioning first (the positioning capability has its own setup flow) before generating a battlecard. If competition notes exist for some competitors but not this one, that's fine: this run becomes the create-from-scratch path.
A six-section battlecard in canonical format, saved to org knowledge via swan-update-knowledge-competition and returned to the user.
Get the competitor name and primary URL from the user. Confirm the spelling. If the user has prior notes, load them first via swan-update-knowledge-competition (the read path is via swan-get-memory on the competition slot).
swan-get-memory for org competition knowledge. If there's already a section on this competitor, treat the task as update, not create from scratch. Preserve what's true; only revise what's stale.
Make a small number of cheap queries. Do not dump everything; pick the highest-signal sources first.
swan-fetch-scraped-url on the competitor's homepage and pricing page. Capture: the headline value prop, the primary CTA, the named target customer/segment.swan-fetch-scraped-url on their /customers or case-study page if linked. Capture 3-5 named customers and any pattern.swan-linkedin-social-media-presence on the competitor's company LinkedIn. Capture: posting cadence, hiring areas (titles in recent posts), leadership announcements.swan-website-traffic on the competitor's domain. Capture: traffic order of magnitude (10k, 100k, 1M monthly) and trend direction.swan-fetch-business-events for funding/leadership/partnership events.If the user already has fresh intelligence, skip the corresponding fetch. Don't burn credits re-pulling.
Write the battlecard in this exact structure:
## Battlecard — <Competitor>
*Last updated: <today's date>*
### 1. One-line description
<What they sell, who they sell to, in one sentence.>
### 2. Where they win
<Bullet list — 3-5 items. The genuine strengths. Don't strawman.>
### 3. Where they lose
<Bullet list — 3-5 items. Real weaknesses, ideally evidenced from public reviews, missing features, or known customer complaints.>
### 4. Common objections we hear
<Format: "Objection → our response." 3-6 entries. Keep each response < 30 words.>
### 5. Win conditions
<Bullet list — when we beat them. Specific buyer profiles, deal sizes, technical requirements, regional factors.>
### 6. Where to push in a deal
<Bullet list — concrete tactical moves. Demo emphasis, pricing posture, proof points to bring up.>
Be honest about strengths. A battlecard that pretends the competitor has no advantages doesn't get used.
swan-update-knowledge-competition with the new battlecard content. Use append or find-and-replace depending on whether this is a new competitor or an update.
Return the full battlecard in the response. The user typically wants to read it once and share it.
swan-update-knowledge-competition. A battlecard that lives only in chat history is wasted.