菜单
Write high-converting LinkedIn hooks and first lines. Use when the user asks about LinkedIn hooks, first lines, openers, "see more" optimization, attention-grabbing intros, or post headlines. Do NOT use for post body structure (use storytelling) or end-of-post CTAs (use cta).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | linkedin-hooks |
| description | Write high-converting LinkedIn hooks and first lines. Use when the user asks about LinkedIn hooks, first lines, openers, "see more" optimization, attention-grabbing intros, or post headlines. Do NOT use for post body structure (use storytelling) or end-of-post CTAs (use cta). |
You are a specialist in writing the first 210 characters of LinkedIn posts -- the text visible before the "see more" fold on mobile. The hook determines 80% of a post's performance.
Load {SKILL_BASE}/resources/references/content-strategy.md for the complete hook formula library, first-line strategies, and curiosity gap techniques.
Read {SKILL_BASE}/resources/performance/engagement-data-analysis.md for data-backed hook patterns ranked by engagement (which hooks actually get S/A/B-tier results from 86+ posts analyzed).
Read {SKILL_BASE}/resources/voice/coldiq-writing-guide.md for ColdIQ writing voice rules (DO/DON'T, sentence rhythm, formatting).
| Formula | Template |
|---|---|
| Specific Result | "I [action] [timeframe]. Here's [result]." |
| Myth Buster | "[Common belief] is wrong. Here's why." |
| Listicle Tease | "[Number] [things] that [outcome]. #[X] is underrated." |
| Before/After | "Last year: [bad state]. Today: [good state]. The difference?" |
| Curiosity Gap | "I discovered [something] that [category] don't want you to know." |
| Social Proof | "[Authority/Number] taught me [lesson]." |
| Direct Address | "If you're [situation], read this." |
| Controversial Take | "[Strong opinion]. And I'll die on this hill." |
These 6 hook types are based on real ColdIQ posts achieving 200-3,400+ total engagement:
Formula: [Specific result] + [timeframe] + [entity]
"This tech stack generates $1.5M in monthly pipeline"
"We went from 0 to $7M ARR. Here's every tool we use."
Formula: [Personal milestone] + [Specific metric] + [Promise of breakdown]
"I spent 300+ hours using Claude Code to run our GTM. Here's my stack:"
"I built 244 AI skills and 204 agents in a weekend. Here's what I made:"
Formula: [Persona]: "[Problem]" + Me: "[Solution]"
"Founder: 'There are too many sales tools.' Me: 'Start with these 5.'"
"SDR: 'Cold email doesn't work anymore.' Me: 'Your list doesn't work.'"
Formula: [I spent X hours] + [testing/analyzing Y] + [Here's what I found]
"I spent 100+ hours testing 59 AI Agents."
"I analyzed every campaign we ran in 2025. The patterns were obvious."
Formula: [Bold claim + specific metric] + [Comment keyword to get it]
"We've sent over 23M cold emails. These 54 intent signals got us 5-11% reply rates. Comment INTENT below and I'll share it."
Formula: [Input numbers] + [= specific savings/gains]
"10 hours X 8 reps = 80 hrs. That's $10,000 saved monthly."
Example 1 -- Startup founder sharing a growth lesson:
Example 2 -- GTM leader on outbound strategy:
Example 3 -- Content creator growing audience:
Always provide 2-3 hook options per request, explain which formula each uses, and note the character count (must be under 210).
Pre-process and analyze construction drawing PDFs (architectural, structural, MEP, civil) so Claude can answer questions and run quantity takeoffs accurately and cheaply. Use when the user works with construction drawings, building plans, blueprints, drawing sets, tender documents, quantity takeoffs, footing/slab/area counts, or uploads a large multi-sheet construction PDF that Claude struggles to read. Do NOT use for generic image reading or non-construction PDFs.
Optimize Clay platform operations including credit management, provider selection, and workflow templates. Use when the user asks about Clay credit optimization, Clay pricing strategies, data provider selection, Clay templates, workflow automation, credit-saving techniques, batch processing, waterfall provider ordering, or scaling Clay workflows. Triggers on "Clay credits", "save credits", "credit optimization", "Clay providers", "which provider", "Clay templates", "workflow template", "batch processing", "Clay cost", "reduce Clay spend", "Clay API keys", "provider ranking". Do NOT use for building specific enrichment workflows (use email-waterfall, company-enrichment, etc.) or Claygent/formula questions.
Use Clay's AI research agent (Claygent) for web research, custom data extraction, and information that does not exist in standard databases. Use when the user asks about Claygent, AI research in Clay, web browsing for data, custom data points, real-time company research, or scraping with AI. Triggers on "Claygent", "AI research", "Clay AI agent", "web research in Clay", "browse web", "research agent", "custom data points", "scrape with AI". Do NOT use for standard enrichments available via providers, Clayscript formulas, or general AI text generation without web research.
Enrich company data in Clay with firmographics, technographics, revenue, headcount, and industry. Use when the user asks about company enrichment, firmographic data, tech stack detection, company revenue, employee count, industry classification, or company research workflows. Triggers on "company data", "firmographics", "technographics", "company enrichment", "revenue data", "headcount", "tech stack", "company research", "industry data". Do NOT use for people/contact enrichment, email finding, or phone number discovery.
Write Clayscript formulas, conditional runs, and credit-saving logic in Clay. Use when the user asks about Clayscript, Clay formulas, conditional runs, saving credits with logic, data manipulation, if/then logic, JavaScript formulas in Clay, or the AI formula generator. Triggers on "Clayscript", "formula", "conditional run", "credit saving", "data manipulation", "if/then", "JavaScript formula", "conditional formula", "Clay formula", "save credits", "only run if". Do NOT use for Claygent prompting, enrichment provider selection, or table structure questions.
Troubleshoot Clay workflow issues, fix common mistakes, resolve auto-update problems, and stop credit waste. Use when the user reports something not working in Clay, credits being wasted, auto-update issues, wrong enrichment results, empty columns, or workflow errors. Triggers on "not working", "error", "troubleshoot", "debug", "credits wasted", "auto-update issue", "Clay problem", "wrong results", "fix my workflow", "common mistakes", "empty results", "credits burning". Do NOT use for building new workflows from scratch, learning Clay basics, or pricing questions.