client-research

client-research is a skill for Claude Code, Codex from Ken-Technology/cold-email-skills. It costs 99 tokens per session (1,338 once invoked), scanned A, original, MIT.

A guide for combining meeting recordings, website information, documents, and other client material into a Markdown research document. The document supports sales planning, target-list building, and email work.

In plain words
What is it for?
It helps collect and organize company details, customer research, competitors, testimonials, sales materials, and past campaign notes into reusable client context.
Why use it?
It keeps important client information in one structured place instead of making later campaign work depend on scattered source files.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: model in frontmatter.

Good fit It helps collect and organize company details, customer research, competitors, testimonials, sales materials, and past campaign notes into reusable client context.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ken-technology/cold-email-skills/client-research
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 Ken-Technology/cold-email-skills --skill client-research
Clone the repo
git clone --depth 1 https://github.com/Ken-Technology/cold-email-skills

Made for: Claude Code, Codex.

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 client-research

README.md
[![agentmods](https://agentmods.dev/badge/skills/ken-technology/cold-email-skills/client-research/github.svg)](https://agentmods.dev/skills/ken-technology/cold-email-skills/client-research)
Your own site
<a href="https://agentmods.dev/skills/ken-technology/cold-email-skills/client-research"><img src="https://agentmods.dev/badge/skills/ken-technology/cold-email-skills/client-research/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 client-research

Your own site · 80×15
<a href="https://agentmods.dev/skills/ken-technology/cold-email-skills/client-research"><img src="https://agentmods.dev/badge/skills/ken-technology/cold-email-skills/client-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 99 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,338 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00099 $0.01338
Opus 5 $0.00049 $0.00669
Sonnet 5 $0.00020 $0.00268
Haiku 4.5 $0.00010 $0.00134

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

Security

Grade A, and why

client-research scanned grade A with 0 findings 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 9d 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

client-research/SKILL.md · 145 lines

How it starts

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

Client Research Skill

Synthesize multiple research sources into a comprehensive client strategy document optimized for both human review and downstream AI agents (GTM strategy, list building, email copywriting).

Required Context

Before generating the research document, load all available client sources. {workspace} = the client campaign workspace (default ./cold-email/{slug}/ under the current directory):

Directory Structure Reference:

{workspace}/
├── research.md       # Existing research (preserve metadata if updating) - THIS skill's output
├── notes.md          # Optional client preferences
├── research/         # Source material: scraped website content,
│   └── website/      # transcripts, documents the user dropped in
└── {plan folders}/   # Past campaign plans (note what worked)

Sources may also arrive as user uploads or paths given in the conversation - use whatever is provided.

Inputs

Expect one or more of these source types:

  • Meeting recordings/transcripts (Fireflies, Otter, Gong, etc.)
  • Scraped website content
  • Product documentation
  • Competitor analysis
  • Customer testimonials or case studies
  • Sales materials

Output Format

Generate ONE document, {workspace}/research.md, with a quick-reference summary on top followed by the comprehensive research. This single file is what every downstream campaign skill reads.

Part 1: Summary (top of research.md)

Quick-reference section for daily use. See references/context-template.md for the exact structure. Key sections:

  • Header metadata (client slug, created date, owner)
  • Elevator Pitch - Short hook answering: "If I met {ICP} in an elevator with {Company}, what should I say in a couple seconds to make them really hooked?"
  • About the Company - 3-paragraph executive summary
  • Target Audience - Condensed ICP (1-2 paragraphs)
  • Core Problems Solved - Bulleted list (3-5 items)
  • Key Assets - Top 3 lead magnets (table format)
  • Case Studies - Top 3 results (table format)
  • Quick Links - Website, other client links

Read the full file on GitHub · 145 lines

Files

What ships with it

2 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. 9d ago First seen · 145 lines · 99 tokens per session scan A bcf8c9d21e13

Subscribe to this mod's changes

client-research is a skill published in the GitHub repository Ken-Technology/cold-email-skills (3 stars, last pushed 12d ago), licensed MIT. It adds 99 tokens to every session and 1,338 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

outbound-strategy

Build your own in-house cold email / outbound infrastructure instead of renting Smartlead, Instantly or Lemlist. Use when someone wants to set up self-hosted cold outreach: connecting their own SMTP/IMAP inboxes, sourcing and segmenting B2B leads, writing multi-step sequences, sending at scale with deliverability-safe…

gquthier/autonomous-cold-email · 144 tokens

cold-email-onboarding

First-run interactive setup for the cold-email skill pack. Walks the operator through brand-config.json (ICP, PSP, EVP, tone, infrastructure) and SOUL.md (voice fingerprints, banned phrases, stories you lean on) in 10 minutes. Refuses to let the operator skip — generic output is worse than no output. Loaded…

cmj-hub/claude-cold-email · 91 tokens

cold-email-kickoff

Adaptive router for the cold-email skill pack. Detects the operator's current state (brand-config present? SOUL.md present? infrastructure ready? PSP defined? EVP locked? first campaign run?) and picks the next-best step. Loaded by the main cold-email skill on bare invocation ("/cold-email") or when the operator asks…

cmj-hub/claude-cold-email · 99 tokens

cold-email-list-quality

Score a cold-email prospect list 0-100 across dedup, role-fit (vs brand-config.icp), signal freshness, email-validity heuristics, exclusion-criteria match, and company-stage match. Returns the score, list of rows to remove, and a fix recommendation. Loaded by cold-email-weekly-rhythm on Monday's list refresh. Operates…

cmj-hub/claude-cold-email · 88 tokens

cold-email-reply-scoring

Classify replies to cold email into 4 categories — buy-signal, positive, neutral, not-interested — using deterministic features (intent keywords, time-to-reply, length, question count, calendar/asset asks). Routes each reply per brand-config.operations.replyrouting. Backed by a Python script that uses regex + features…

cmj-hub/claude-cold-email · 94 tokens

cold-email-weekly-rhythm

Operational cadence playbook for the cold-email program. Defines what happens on Monday (PSP signals + list refresh), Wednesday (sequence ship + reply triage), Friday (reply scoring + adjust). Surfaces this week's queue, drift signals, and the metric review against last week. Inspired by coldoutboundskills'…

cmj-hub/claude-cold-email · 92 tokens