Terminal
Terminal/Skill
Builds a sourced brief on one company from its domain, covering what it does, who it sells to, size, funding and recent news.
By Clay
Works with
npx skills add clay-run/clay-skill-creator --skill company-research-briefThe insight: most wrong briefs are right briefs about the wrong entity — or yesterday's entity. Company names collide (holdings, franchises, regional clones, rebrands), and a model's memory of a company drifts stale the day it's written. So this skill anchors on the DOMAIN — visit it first, always, before any name-keyed lookup — disambiguates the entity before spending on enrichment, and builds the brief from what sources actually say today, each claim carrying its source. A field nothing supports stays empty — never "N/A", never filler, never the model's recollection dressed as research.
Nothing here ships with a value. Each one is the installer's, not the author's: ask for it, never substitute a plausible default, and where an answer does not exist say which step becomes unavailable rather than guessing. Where a default IS defensible it is named below, and using it means saying so in the output.
| Input | What the installer supplies | If it is missing |
|---|---|---|
| The anchor | the company's domain, ideally | given only a name, resolve the domain first and confirm it if several candidates exist. A wrong domain poisons the whole brief |
| The angle | selling in, partnering, or competitive | seller's brief is the defensible default and must be stated — it decides which sections go deep |
| Budget | credits | the standard brief is a handful of credits; state the number before running, not after |
If an answer sheet is present beside this skill, load it and ask only for what it does not cover. A partial sheet is normal; a value it is missing gets asked for on its own rather than restarting the interview. Say which values came from the sheet before using them — a sheet applied silently is a wrong field nobody catches. If there is no sheet, say nothing about sheets — the check is a file lookup, not a question, so run the interview as though the feature did not exist rather than reporting an absence. At delivery, offer to save the answers back (identifiers only — never a token or a password), private and never published — and phrase the offer so it explains itself: "want me to save your answers to a file, so the next person on your team doesn't have to answer these again?"
Run clay whoami; echo "exit_code=$?". If it fails or Clay tools are missing, run
the Clay plugin's setup skill, restart if it says to, and re-run this skill. Tell
the user which workspace you're in. Confirm the managed Enrich Company function
and the news catalog action exist and read their declared costs (they drift; see
references/research-recipe.md).
The two commands that resolve them, and the one that carries the price:
clay routines list --limit 100 # the managed enrichment; the list call omits costs
clay routines get <routineId> # the declared cost
clay workflows actions list # the news arm lives in the action catalogue
Identify a catalogue action by the pair of packageId and actionKey; keys collide across
packages at different prices.
Pre-gate an unknown domain for FREE first — a DNS resolution or status probe; a dead domain hangs the scraper for a minute-plus while the free check answers in a second (mechanics in the reference). Then fetch the company's own site — homepage, then /about or /product if present (via this agent's web access or the scrape action). From the company's OWN words: what they do, who they serve, products, positioning. Two disciplines:
references/research-recipe.md §Entity edge cases). Ambiguity goes
back to the user BEFORE spend, with the candidates named.With the entity anchored: run managed Enrich Company on the domain for
firmographics — industry, headcount (arrives as a BAND STRING — report the band,
never a fake number), HQ, founding year, type. Cross-check the payload's identity
fields against the anchor (the payload's own domain field can echo a marketing/
shortener domain — match on website, and a mismatch is a flag, not a silent pick).
Pull recent developments with the news arm, date-windowed (default: last 90 days),
classified per the signal menu; each with date + source link. Funding facts come
from the enrichment or dated news — never from memory.
Sections (schema in references/research-recipe.md): identity (cleaned name, domain,
entity type) · what they do (description, products, value prop — from THEIR site) ·
who they sell to (ICP, target personas/industries — inferred from evidence, marked as
inference) · firmographics (from the enrichment payload, quoted) · recent
developments (dated, linked) · open questions (what could NOT be established).
Ask: "Prep me a brief on brightloop.example before my call tomorrow." Anchor: homepage + /product fetched — B2B workflow-automation SaaS for logistics teams, self-described; entity matches (no collisions found). Enrich Company → industry "Software Development", size "201-500 employees" (band), HQ Rotterdam, founded 2018. News, 90-day window → one dated event: a Series B announcement with source link → recent developments. ICP section: "mid-market logistics operators" — labeled inference from their case-study page. Open questions: revenue (no source), US presence (site silent). Brief delivered with per-claim sources; 3 credits, stated up front. Counter-example: "brief on Meridian" — three plausible Meridians (a fintech, a consultancy, a medical group) → candidates presented, user picks the domain, THEN the pipeline runs. No spend before the entity is pinned.