Localized reading guide
account-researchPurpose, usage and source
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
partner-built/common-room/skills/account-research/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- research
- Last collected
License: License file needs review
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
How the upstream workflow works
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.
Upstream passage · L18 ↗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.
Upstream passage · L33 ↗## [Company Name] — Account Overview (Limited Data)
**Data available:** [List exactly what Common Room returned]
[Present only the returned fields]
**Web Search**
[Findings from web search — or "No significant recent news found"]
**Note:** Common Room has limited data on this account. The account may need enrichment in Common Room.Requirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
Quality Standards
Scores must always be raw values or percentiles — never categorical labels For targeted questions, answer precisely and don't over-deliver
Upstream passage · L129 ↗Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
66288f1275c427efeea6de62ca0679874195e1c01d2ff5c3b32269f53614571a