Luopan Company Research
zhangxiaoqiang1991/luopan
罗盘的公司研究子模式。研究具体上市或非上市公司的财务增长、商业模式、 竞争生态位、治理与组织信号，并分别生成投资初筛和求职初筛。
Identify and prioritize evidence-based pain points a target company likely faces, based on growth signals, tech stack, hiring activity, and industry context.
Install Pain Identifier
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill pain-identifier -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system pain-identifier --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/lemlist/pain-identifier .claude/skills/pain-identifier && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pain-identifier" agent skill from https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/pain-identifier into .claude/skills/pain-identifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pain-identifier", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/pain-identifierType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill pain-identifier -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system pain-identifier --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/lemlist/pain-identifier .agents/skills/pain-identifier && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pain-identifier" agent skill from https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/pain-identifier into .agents/skills/pain-identifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pain-identifier", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill pain-identifier -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system pain-identifier --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/lemlist/pain-identifier .cursor/skills/pain-identifier && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pain-identifier" agent skill from https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/pain-identifier into .cursor/skills/pain-identifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pain-identifier", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git --path .claude/skills/lemlist/pain-identifier--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill pain-identifier -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system pain-identifier --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/lemlist/pain-identifier .gemini/skills/pain-identifier && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pain-identifier" agent skill from https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/pain-identifier into .gemini/skills/pain-identifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pain-identifier", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system pain-identifierInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill pain-identifier -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/lemlist/pain-identifier .github/skills/pain-identifier && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pain-identifier" agent skill from https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/pain-identifier into .github/skills/pain-identifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pain-identifier", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill pain-identifier -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Othmane-Khadri/YALC-the-GTM-operating-system pain-identifier --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/lemlist/pain-identifier .opencode/skills/pain-identifier && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pain-identifier" agent skill from https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/pain-identifier into .opencode/skills/pain-identifier/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pain-identifier", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pain-identifier- GitHub stars
- 318
- Token cost
- ~1.2k tokens
- SKILL.md length
- 573 words
- Files
- 1
- Skills in repo
- 57
- Repo updated
- First seen
- Licence
- MIT
At a glance
Identify and prioritize evidence-based pain points a target company likely faces, based on growth signals, tech stack, hiring activity, and industry context.
- Works in 5 steps: Gather inputs → Build the company profile → Detect signals → …
- Asked what are [company]s pain points
- SKILL.md covers Step 1 — Gather inputs, Step 2 — Build the company…, Step 3 — Detect signals and Step 4 — Map signals to pain…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Pain Identifier is an agent skill from Othmane-Khadri/YALC-the-GTM-operating-system. Identify and prioritize evidence-based pain points a target company likely faces, based on growth signals, tech stack, hiring activity, and industry context. Use when asked "what are [company]'s pain points", "research pain points for [company]", "why would [company] buy", "what problems does [company] face", "qualify this lead", "account research for [company]", "help me personalize outreach to [company]", or "what signals should I mention in my email to [company]".
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering Sales call preparation. The repository describes itself as: YALC 1.0, the open-source Clay alternative. MIT, CLI-first, self-hosted, runs in Claude Code. Yalc today is an intelligent orchestration layer that runs pre configured GTM agents…. The licence is MIT.
When your agent uses it
- Asked what are [company]s pain points
- Research pain points for [company]
- Why would [company] buy
- What problems does [company] face
Example prompts
- “what are [company]”
- “research pain points for [company]”
- “why would [company] buy”
- “/pain-identifier”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 5686d1f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Pain Identifier loads about 1.2k tokens when it runs. Until then it costs about 122 tokens; SKILL.md has 573 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Othmane-Khadri/YALC-the-GTM-operating-system at commit 5686d1f, republished under its MIT licence (© Othmane-Khadri). 573 words, ~1,242 tokens.
Download SKILL.mdSave it as
.claude/skills/pain-identifier/SKILL.md (or your agent's skills folder).- name
- pain-identifier
- description
- Identify and prioritize evidence-based pain points a target company likely faces, based on growth signals, tech stack, hiring activity, and industry context. Use when asked "what are [company]'s pain points", "research pain points for [company]", "why would [company] buy", "what problems does [company] face", "qualify this lead", "account research for [company]", "help me personalize outreach to [company]", or "what signals should I mention in my email to [company]".
Pain Identifier — Uncover what keeps them up at night
You are a B2B account research specialist. You analyze target companies to identify specific, likely pain points based on observable signals — so outreach is personalized and relevant, not generic.
Core principle: Pain points are predictable, not random. They follow company stage, growth signals, tech stack, industry dynamics, and trigger events.
Step 1 — Gather inputs
Ask for:
- Company name or URL (required)
- Your product/solution (so you know which pains you can solve)
- Any signals you already know (funding, hiring, recent news)
Step 2 — Build the company profile
Extract from LinkedIn, website, Crunchbase:
- Industry (specific vertical, not just "tech")
- Size (employees) and funding stage
- What they sell and who they sell to
- Recent hires, open roles, funding, news
Stage → typical pains:
| Stage | Size | Typical pains |
|---|---|---|
| Pre-Seed/Seed | 1–25 | Everything manual, wearing too many hats, no processes |
| Series A | 25–75 | Scaling GTM, first sales team, process chaos |
| Series B | 75–200 | Efficiency gaps, data silos, need better tooling/ops |
| Series C+ | 200–500 | Complex operations, security/compliance, enterprise motion |
| Mature | 500+ | Technical debt, integrations, change management |
Step 3 — Detect signals
Hiring signals (LinkedIn jobs page):
- Hiring SDRs/BDRs → building outbound, need SEP
- Hiring RevOps → sales process chaos, need systems
- Hiring Customer Success → churn risk, scaling support
- Rapid hiring (10+ open roles) → scaling pains, onboarding challenges
- New VP/C-level hire → change mandate, new tool evaluation window (first 90 days)
Funding signals:
- Just raised → pressure to scale, deploy capital fast
- 12–18 months since raise → approaching next round, needs metrics
- Series A → B transition → efficiency focus replaces growth-at-all-costs
Tech stack signals:
- Has Salesforce but no SEP → manual outreach pain
- Using HubSpot basic → outgrowing tool, needs more automation
- No data enrichment tool → manual research, time waste
- Legacy tools → integration pain, poor UX
Other signals:
- New office / geographic expansion → coordination, localization pain
- Product launch → GTM for new offering, messaging challenges
- Press coverage or milestones → fast growth, scaling pains
Step 4 — Map signals to pain points
For each identified pain, score it:
| Criterion | Weight | Score (1–5) |
|---|---|---|
| Severity (how much it hurts) | 30% | |
| Evidence strength (confidence it's real) | 25% | |
| Solution fit (how well you solve it) | 25% | |
| Urgency (need to solve it now) | 20% |
Priority score > 3.5 → lead with this pain in outreach
Show full SKILL.md (208 more words)Show less
Step 5 — Output
Pain Point Analysis: [Company Name]
Company context: [Industry | Size | Stage | What they do]
Key signals detected:
- ✅ [Signal 1] → indicates [pain inference]
- ✅ [Signal 2] → suggests [pain]
- ✅ [Signal 3] → confirms [pain]
Priority pain points
🔴 Pain #1: [Name] — Score: X/5
The pain: [Specific description in concrete terms] Evidence: [Which signal(s) indicate this] Business impact: [Cost, lost revenue, inefficiency — quantify] Personal impact (for [role]): [How this affects their job/bonus/career] Urgency: [Why they need to solve this NOW] How [your product] solves it: [Specific capability] Outreach angle: "I noticed [signal]. Most [similar companies] struggle with [pain]. We help [outcome]. Worth a chat?"
🟡 Pain #2: [Name] — Score: X/5
[Same structure, abbreviated]
🟢 Pain #3: [Name] — Score: X/5
[Same structure, abbreviated]
Recommended outreach strategy
Primary angle: [Lead with Pain #1 — opening line + value hook + proof] Discovery questions to confirm:
- "[Question to surface Pain #1]"
- "[Question to quantify impact]"
- "[Question to uncover urgency]"
Confidence assessment
- High confidence: [pains with direct evidence]
- Medium confidence: [strong inference, stage/industry pattern]
- Low confidence: [educated guess — flag as hypothesis to test in discovery]
Quality bar
- Every pain linked to a specific observable signal?
- Avoided generic pains ("need more efficiency") — used specific descriptions?
- Clear priority ranking?
- Provided outreach angles, not just analysis?
- Flagged what's certain vs. inferred?
© Othmane-Khadri, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/lemlist/pain-identifier of Othmane-Khadri/YALC-the-GTM-operating-system.
Open the folder on GitHubat commit 5686d1f
Compare with similar skills
Pain Identifier next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pain Identifier this skillOthmane-Khadri/YALC-the-GTM-operating-system | 318 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Luopan Company Researchzhangxiaoqiang1991/luopan | 389 | — | ~998 | Automated safety check: Pass | MIT | |
| Company Researchstophobia/deerflow2.0-enhanced | 822 | — | ~845 | Automated safety check: Pass | MIT | |
| Meeting Prep BriefBrianRWagner/ai-marketing-claude-code-skills | 441 | — | ~922 | Automated safety check: Pass | None | |
| SdtStopDisTrain/sdt-skills | 309 | — | ~535 | Automated safety check: Pass | MIT | |
| Account Researchextruct-ai/gtm-skills | 109 | — | ~1.6k | Automated safety check: Pass | None |
Similar skills
Company Research
stophobia/deerflow2.0-enhanced
综合企业背景调研技能，用于尽职调查、合作伙伴评估、投资分析、市场研究等场景。支持公司工商信息、财务数据、法律风险、舆情分析、竞品对比等多维度调研，自动生成Markdown和HTML格式的专业调研报告。触发条件：用户提及"企业调研"、"公司背景"、"尽职调查"、"合作伙伴评估"、"投资分析"、"市场研究"等关键词。
Meeting Prep Brief
BrianRWagner/ai-marketing-claude-code-skills
Builds a pre-meeting brief from your Obsidian vault: participant research, past notes, open commitments, a prioritized agenda and sharp questions.
Sdt
StopDisTrain/sdt-skills
SDT 内容生产工具箱的总入口：根据当前任务选择最合适的 sdt- 模块，既能完成标题、开头等单一步骤，也能组织从账号研究到发布的完整流程。用户不知道该用哪个 SDT Skill，或希望一站式完成内容生产时使用。
Account Research
extruct-ai/gtm-skills
Deep-research a single target account into a decision-ready dossier: the entity tree, the buying units and decision-makers, live signals (open/closed roles, leadership moves, news, tech stack), and…
Call Prep
breakstageaxe61/genspark-claw
Prepare an AI phone call end-to-end — research the callee, set a concrete objective and fallback, draft a natural call script with branching, and produce a post-call summary template.
More from Othmane-Khadri/YALC-the-GTM-operating-system
All 57 skills in this repoClaap Weekly Recap
Othmane-Khadri/YALC-the-GTM-operating-system
Turns a week of Claap-recorded sales calls into action items and focus blocks on a Notion Kanban, delivered with a Slack summary.
Fullenrich Plg Reverse Lookup
Othmane-Khadri/YALC-the-GTM-operating-system
A skill your agent uses when the user says "set up FullEnrich reverse lookup for trial signups", "PLG enrichment webhook", "identify free trial signups via FullEnrich", "reverse email lookup for…
Fullenrich Content Engagers
Othmane-Khadri/YALC-the-GTM-operating-system
A skill your agent uses when the user says "enrich people who engaged with this post", "qualify post engagers with FullEnrich", "scrape and enrich LinkedIn post {URL}", "engagers from this post into…
Fullenrich Event Attendees
Othmane-Khadri/YALC-the-GTM-operating-system
A skill your agent uses when the user says "enrich this LinkedIn event", "enrich attendees of this event", "enrich this attendees CSV", "scrape and enrich LinkedIn event {URL}", "FullEnrich event…
Answer Linkedin Comments
Othmane-Khadri/YALC-the-GTM-operating-system
Reply to comments on a LinkedIn post via Unipile — drafts thread-aware replies grounded in the user's voice and the conversation context, then sends on approval.
Fullenrich Network Activation
Othmane-Khadri/YALC-the-GTM-operating-system
A skill your agent uses when the user says "activate co-founder network with FullEnrich", "enrich LinkedIn connections export", "qualify my LinkedIn connections CSV", "turn Connections.csv into a…
Related
Categories
Questions about Pain Identifier
What does Pain Identifier do?
Identify and prioritize evidence-based pain points a target company likely faces, based on growth signals, tech stack, hiring activity, and industry context. Pain Identifier is an agent skill from Othmane-Khadri/YALC-the-GTM-operating-system. Identify and prioritize evidence-based pain points a target company likely faces, based on growth signals, tech stack, hiring activity, and industry context.
When should I use Pain Identifier?
Pain Identifier fits situations like: asked what are [company]s pain points; research pain points for [company]; why would [company] buy; what problems does [company] face.
How do I install Pain Identifier in Claude Code?
Run `npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill pain-identifier -a claude-code`. Or copy the skill folder (.claude/skills/lemlist/pain-identifier in Othmane-Khadri/YALC-the-GTM-operating-system) into .claude/skills/pain-identifier in your project. Claude Code loads it when a task matches its description.
How do I install Pain Identifier in Codex?
Run `npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill pain-identifier -a codex`. Or copy the skill folder (.claude/skills/lemlist/pain-identifier in Othmane-Khadri/YALC-the-GTM-operating-system) into .agents/skills/pain-identifier in your project. Codex loads it when a task matches its description.
Can I use Pain Identifier in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Othmane-Khadri/YALC-the-GTM-operating-system --skill pain-identifier -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pain-identifier, .gemini/skills/pain-identifier, .github/skills/pain-identifier and .opencode/skills/pain-identifier in your project.
What does Pain Identifier need to run?
SKILL.md names no scripts, command-line tools or credentials: Pain Identifier is instructions for the agent only.
Does Pain Identifier access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Pain Identifier safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Pain Identifier use?
Pain Identifier is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pain Identifier use?
About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Pain Identifier?
Skills that share tags, products or a category with Pain Identifier: Luopan Company Research (zhangxiaoqiang1991/luopan, 389 stars), Company Research (stophobia/deerflow2.0-enhanced, 822 stars), Meeting Prep Brief (BrianRWagner/ai-marketing-claude-code-skills, 441 stars) and Sdt (StopDisTrain/sdt-skills, 309 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pain Identifier?
Othmane-Khadri (a GitHub user) maintains it in Othmane-Khadri/YALC-the-GTM-operating-system, which has 318 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on August 20, 2026.
Source: Othmane-Khadri/YALC-the-GTM-operating-system on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.