Account Research Brief logo

Account Research Brief

Organization
swan-gtm
account-research-brief

Use this skill before a first meeting, an ABM push, or a territory review, when you need a defensible account brief instead of a copied About page. Produces firmographics, positioning pillars, an evidence-tagged SWOT, a named exec list, and live hiring signals, with every claim marked as sourced or inferred.

Overview

Publisherswan-gtm
Repositorygtm-skills
Skill nameaccount-research-brief
Stars
216
Forks
103
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by swan-gtm on GitHub. Read the source before you install it.

Installation

Install the Account Research Brief AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/swan-gtm/gtm-skills/tree/main/skills/amir-baldiga/account-research-brief
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/swan-gtm/gtm-skills.git /tmp/gtm-skills
mkdir -p .claude/skills
cp -r /tmp/gtm-skills/skills/amir-baldiga/account-research-brief .claude/skills/account-research-brief
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Account Research Brief in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Account Research Brief on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Account Research Brief is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Run this before a first meeting or an ABM push. It produces a one-page brief where every claim is tagged as evidence-backed or inference, so the AE knows what they can say out loud.

The play

  1. Resolve the company to a stable identifier first. Match on the company's own URL slug rather than its display name. Name search returns near-matches and you will research the wrong entity, which is worse than researching nothing.

  2. Pull firmographics. Size, industry, headquarters, founding year, description, specialities. This is the skeleton the rest hangs on.

  3. Read composition, not just headcount. How the employee base splits by function and seniority says more than a total. A company that is 60% engineering sells differently than one that is 60% sales.

  4. Extract positioning pillars. Cluster the company's own description, tagline, and specialities into three to six themes: product areas, target buyer, stated differentiators. Name each pillar and cite the exact source phrase. These are the words the buyer already uses about themselves.

  5. Build a SWOT where every line is tagged. Mark each point evidence (traceable to something retrieved) or inference (your read). An untagged SWOT is opinion wearing a suit, and an AE who repeats an inference as fact in a meeting loses the room.

  6. Ask before you spend on people. Confirm two things with the requester: which titles matter, and how many employee records to pull. Skipping this is how a routine brief turns into a surprise bill.

  7. Read hiring as a live signal. Recent joiners, by function, are the most current evidence you have of where budget is moving. A team that added four engineers and no marketers last quarter is telling you something.

  8. Deliver both shapes. Structured data for the next automation step, and a short human brief for the AE. They have different readers and different lifespans.

What good looks like

  • The best briefs quote the company's own language back. Buyers relax when you describe them the way they describe themselves.
  • The mediocre version is a reformatted About page: no composition, no signal, no tagging, and nothing an AE could not have read themselves in two minutes.
  • Absence is a finding. "No leadership changes in twelve months" is real intelligence. Say it rather than padding the section.
  • You know it is good when the AE walks in able to say which claims are sourced and which are your read, and never has to guess.

Rules

  • MUST tag every SWOT point as evidence or inference.
  • MUST confirm target titles and record counts before pulling people data.
  • MUST state plainly when a data source returned nothing, in the brief itself.
  • NEVER invent a headcount growth trend, an exec, or a job opening to fill a section.
  • NEVER research a company you matched by display name alone without confirming the identifier.

Frequently asked questions

What does the Account Research Brief AI skill do?

Use this skill before a first meeting, an ABM push, or a territory review, when you need a defensible account brief instead of a copied About page. Produces firmographics, positioning pillars, an evidence-tagged SWOT, a named exec list, and live hiring signals, with every claim marked as sourced or inferred.

Why use Account Research Brief on TypingMind?

Because you install it once and use it with any model. Account Research Brief is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Account Research Brief in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/swan-gtm/gtm-skills/tree/main/skills/amir-baldiga/account-research-brief. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Account Research Brief?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Account Research Brief?

As many as you like. As long as a model supports skills, you can use Account Research Brief with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Account Research Brief AI skill free?

Yes. It is published on GitHub by swan-gtm under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇