account-research

account-research is a skill for Claude Code from sun2443/designer-skills. It costs 50 tokens per session (1,338 once invoked), scanned A, a copy of account-research, Apache-2.0.

A company-research workflow that gathers and combines account information from Common Room, a customer-data and engagement platform. It can answer either a broad question about a company or a focused question about one detail.

In plain words
What is it for?
Use it to prepare an account overview, check company details, find buying signals, identify account owners, or answer targeted questions about a customer.
Why use it?
Customer information is often spread across many signals and may be incomplete. This workflow focuses the lookup and explains when the available data is sparse.

Skill for Claude Code

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

Part of the common-room plugin — 5 skills, 2 commands shipped together

Good fit Use it to prepare an account overview, check company details, find buying signals, identify account owners, or answer targeted questions about a customer.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sun2443/designer-skills/account-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 sun2443/designer-skills --skill account-research
Clone the repo
git clone --depth 1 https://github.com/sun2443/designer-skills

Made for: Claude Code.

Or install common-room, the plugin that ships this one along with the rest of its 5 skills, 2 commands.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/sun2443/designer-skills/account-research"><img src="https://agentmods.dev/badge/skills/sun2443/designer-skills/account-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 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 100% copy Near-identical to another mod 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.00050 $0.01338
Opus 5.5 $0.00020 $0.00535
Sonnet 5.5 $0.00010 $0.00268
Haiku 4.5 $0.00005 $0.00134

Measured 13d ago against content hash 66288f1275c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

account-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 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.

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.

Origin

This is a copy

100% identical to account-research — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

partner-built/common-room/skills/account-research/SKILL.md · 141 lines

How it starts

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

Account Research

Retrieve and synthesize account information from Common Room. Handles four interaction patterns: full overviews, targeted field questions, sparse data situations, and combined MCP data + LLM reasoning.

Step 0: Load User Context (Me)

Before researching any account, fetch the Me object from Common Room. This provides:

  • The user's profile, title, role, and Persona in CR
  • The user's segments ("My Segments")

Default all queries to the user's own segments unless the user explicitly asks for a broader view. This keeps results scoped to their territory.

Step 1: Identify the Interaction Pattern

Determine what the user actually needs before deciding how much data to fetch:

Pattern 1 — Full Overview: "Tell me about Datadog" / "Summarize cloudflare.com" → Fetch the full field set and produce a structured briefing.

Pattern 2 — Targeted Question: "Who owns the Snowflake account?" / "Is acme.io showing buying signals?" / "What's the employee count for notion.so?" → Fetch only the relevant field(s). Return a direct, concise answer — do not produce a full brief for a simple question.

Pattern 3 — Sparse Data: "Tell me about tiny-startup.io" → If Common Room has limited data for an account, say so honestly: "There is limited information available for this account." Never speculate or fill gaps with generic statements.

Pattern 4 — Combined Reasoning: Fetch structured MCP data, then layer in LLM analysis — e.g., "Stripe has 8,000 employees and is hiring heavily for AI roles. Based on your ICP of 1k–10k fintech companies, this is a strong fit."

Step 2: Look Up the Account

Search Common Room for the account by domain or company name. Exact match first; if no result, try partial match and confirm with the user before proceeding.

Step 3: Fetch the Right Fields

Use the Common Room object catalog to see available field groups and their contents. For full overviews, request all field groups. For targeted questions, request only what's relevant.

Read the full file on GitHub · 141 lines

Files

What ships with it

1 file 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 · 141 lines · 50 tokens per session scan A 66288f1275c4

Subscribe to this mod's changes

account-research is a skill published in the GitHub repository sun2443/designer-skills (0 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,338 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to account-research, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens