linkedin-job-post-to-buyer-pain-map

linkedin-job-post-to-buyer-pain-map is a skill for Claude Code from Varnan-Tech/opendirectory. It costs 134 tokens per session (3,335 once invoked), scanned A, original, MIT.

A buyer-pain analysis made from pasted LinkedIn job posts, which are public descriptions of roles companies are hiring for. It connects wording in those posts to company-level operational needs and buying signals.

In plain words
What is it for?
Use it to analyze hiring posts, prioritize accounts, and suggest outreach angles for a product. It does not infer personal or protected characteristics about candidates.
Why use it?
It turns hiring language into evidence about capability gaps and possible buy-versus-build choices. Each inferred pain must be supported by text from the job post.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the opendirectory plugin — 58 skills shipped together

Good fit Use it to analyze hiring posts, prioritize accounts, and suggest outreach angles for a product. It does not infer personal or protected characteristics about candidates.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/varnan-tech/opendirectory/linkedin-job-post-to-buyer-pain-map
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Varnan-Tech/opendirectory --skill linkedin-job-post-to-buyer-pain-map
Clone the repo
git clone --depth 1 https://github.com/Varnan-Tech/opendirectory

Made for: Claude Code.

Or install opendirectory, the plugin that ships this one along with the rest of its 58 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for linkedin-job-post-to-buyer-pain-map

README.md
[![agentmods](https://agentmods.dev/badge/skills/varnan-tech/opendirectory/linkedin-job-post-to-buyer-pain-map/github.svg)](https://agentmods.dev/skills/varnan-tech/opendirectory/linkedin-job-post-to-buyer-pain-map)
Your own site
<a href="https://agentmods.dev/skills/varnan-tech/opendirectory/linkedin-job-post-to-buyer-pain-map"><img src="https://agentmods.dev/badge/skills/varnan-tech/opendirectory/linkedin-job-post-to-buyer-pain-map/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for linkedin-job-post-to-buyer-pain-map

Your own site · 80×15
<a href="https://agentmods.dev/skills/varnan-tech/opendirectory/linkedin-job-post-to-buyer-pain-map"><img src="https://agentmods.dev/badge/skills/varnan-tech/opendirectory/linkedin-job-post-to-buyer-pain-map.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 134 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,335 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 5 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Privilege Escalation · line 29
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
  • high Supply Chain · line 113
    Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.
    Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
  • high Supply Chain · line 151
    Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.
    Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
  • medium Data Exfiltration · line 113
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 151
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00134 $0.03335
Opus 5 $0.00067 $0.01667
Sonnet 5 $0.00027 $0.00667
Haiku 4.5 $0.00013 $0.00333

Measured 13d ago against content hash e6310d0cf72c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

linkedin-job-post-to-buyer-pain-map scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s -X POST \
skills/linkedin-job-post-to-buyer-pain-map/SKILL.md · 302 lines

How it starts

The opening of the file, as written. The whole thing — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.

LinkedIn Job Post to Buyer Pain Map

Take LinkedIn job posts. Decode them into a structured buyer pain map with scores, pains, and outreach angles.


Critical rule: Every inferred pain must cite specific language from the job description that supports it. Never hallucinate pains that are not grounded in the text. If a post is too generic to infer pain, say so explicitly and assign a low signal strength score.

Ethical rule: Do not infer personal attributes or protected characteristics about candidates. Focus strictly on company-level operational pain and organizational needs.


Step 1: Setup Check

Confirm required env vars:

echo "GEMINI_API_KEY: ${GEMINI_API_KEY:+set}"

If GEMINI_API_KEY is missing: Stop. Tell the user: "GEMINI_API_KEY is required. Get it at aistudio.google.com. Add it to your .env file."


Step 2: Collect Inputs

The skill needs 3 required inputs. Collect them before proceeding.

2a: Product Brief

Ask: "Describe your product in 2-5 sentences. What do you do, what is your core value prop, and who do you target?"

If the user already included this in their prompt: Extract it. Confirm: "Product brief captured: [summary]."

2b: ICP Description

Ask: "Describe your ideal customer profile in 2-6 bullets: industries, company sizes, roles you sell to, tech stack hints."

If the user already included this in their prompt: Extract it. Confirm: "ICP captured: [summary]."

2c: Hiring Posts

Ask: "Paste the job descriptions you want analyzed. For each post, include the company name, job title, and the full description text. You can paste 1-15 posts."

Accepted formats:

  • Raw pasted text with company name and job title clearly labeled
  • Structured JSON objects with fields: company_name, job_title, location (optional), seniority (optional), team_or_function (optional), job_description_text, job_url (optional)
  • Multiple posts separated by clear delimiters (--- or numbered)

If any field is missing: Infer what you can from the description text. If company_name or job_description_text is missing, ask for it before proceeding.

Read the full file on GitHub · 302 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 13d ago First seen · 302 lines · 134 tokens per session scan A e6310d0cf72c

Subscribe to this mod's changes

linkedin-job-post-to-buyer-pain-map is a skill published in the GitHub repository Varnan-Tech/opendirectory (640 stars, last pushed 27d ago), licensed MIT. It adds 134 tokens to every session and 3,335 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

content-style

Writing Reddit-native content that sounds human, avoids AI tells, and delivers value through structure and specificity. Applies to workshop posts, definitive model guides, research megathreads, and community FYI/update posts.

AtlasOmnia/donna-starter · 37 tokens

coding-worktree-recovery

Use this skill when coding-agent work is interrupted, an agent exits without a clean commit, multiple controllers target the same checkout, or the checkout produces inconsistent file/Git behavior.

AtlasOmnia/donna-starter · 56 tokens

macos-storage-management

Safely reclaim local Mac storage without mistaking cloud placeholders for resident data, losing File Provider content, or flattening metadata onto an incompatible external filesystem.

AtlasOmnia/donna-starter · 22 tokens

hermes-mnemosyne

Mnemosyne is Hermes' primary local-first memory engine — SQLite with vector + FTS5 hybrid search, 19+ tools, auto-consolidation, and a standalone CLI. It's a pip-installed plugin (not a built-in toolset) discovered via $HERMESHOME/plugins/mnemosyne/.

AtlasOmnia/donna-starter · 30 tokens

skill-auditor

Audit any Hermes skill file and assign a quality grade based on clarity, completeness, tool guidance, and shareability. Returns specific fix suggestions ranked by impact.

AtlasOmnia/donna-starter · 64 tokens

marketplace-purchase-vetting

Use this when the user asks whether a local listing is a scam, "too good to be true," worth looking at, or a good deal. Also use this when he asks you to find options — search/discover candidates, then vet the best ones. The goal is not a generic buying guide; it is a practical risk read with clear next steps.

AtlasOmnia/donna-starter · 72 tokens