Agent skill
frontiergtm-account-brief
Build an evidence-backed target-account brief and account strategy for selling AI, infrastructure, developer-tool, cloud, data, or technical B2B products.
Filed under Outbound email.
From frontiergtm/frontiergtm-skills · 6 skills · 0 · pushed 2026-07-22
What it does when it runs
Build an evidence-backed target-account brief and account strategy for selling AI, infrastructure, developer-tool, cloud, data, or technical B2B products. Use for account research, executive meeting preparation, opportunity strategy, discovery planning, buying-committee hypotheses, relevant proof selection, outreach angles, or “help me prepare for this company” requests. Do not use for mass-personalized spam or claims about private buyer intent that the user has not supplied.
Read from the skill and the 3 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/frontiergtm/frontiergtm-skills.git /tmp/frontiergtm-skills git -C /tmp/frontiergtm-skills sparse-checkout set "skills/frontiergtm-account-brief" mkdir -p ~/.claude/skills/frontiergtm-account-brief cp -R "/tmp/frontiergtm-skills/skills/frontiergtm-account-brief/." ~/.claude/skills/frontiergtm-account-brief/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
Or take the whole library
This repo ships a .claude-plugin manifest, so Claude Code can install all 6 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.
/plugin marketplace add frontiergtm/frontiergtm-skills /plugin
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from frontiergtm/frontiergtm-skills/blob/496b496fb82c09789121c249373dbc9930957629/skills/frontiergtm-account-brief/SKILL.md, which is licensed MIT (repository). 432 words, 4 headings.
FrontierGTM Account Brief
Turn public evidence and user-supplied opportunity context into a practical account point of view. Optimize for a better executive conversation, not for a long company profile.
Workflow
-
Frame the opportunity.
- Identify the target account, the seller’s product, the likely buying motion, known contacts, meeting or opportunity stage, and the decision this brief must support.
- Use supplied CRM notes, call notes, emails, product material, and account lists as private context when available. Do not expose or unnecessarily repeat sensitive information.
-
Research the account.
- When search or connected tools are available, prioritize primary sources: company strategy, product and engineering material, executive statements, earnings or funding material, customer announcements, architecture posts, job openings, and relevant partner activity.
- Capture exact dates. Separate current evidence from old context.
- Follow
references/account-evidence.mdwhen converting observations into hypotheses.
-
Build the change hypothesis.
- Identify what the account appears to be trying to change, why now, and what technical or business constraint may block it.
- Connect the seller’s product only where there is a plausible fit. Do not force relevance.
- State evidence, inference, and unknowns separately.
-
Map the buying situation.
- Identify likely business sponsor, technical evaluator, operator, user, security or procurement influence, and potential blocker as hypotheses—not known facts—unless supplied by the user.
- Explain what each role is likely to care about and what evidence would earn credibility.
-
Prepare the conversation.
- Select the most relevant proof, differentiators, and customer evidence from the seller’s available materials.
- Write five to eight discovery questions that test the core hypotheses.
- Create an opening point of view, not a generic pitch.
- Anticipate the strongest status-quo or competitor objection and a credible response.
-
Deliver using
references/brief-format.md.- Keep company background short.
- Lead with the account thesis, evidence, unknowns, and recommended next move.
- Link sources when possible.
Boundaries
- Do not infer protected or sensitive personal characteristics.
- Do not claim private intent, budget, relationships, technology usage, or buying stage without evidence.
- Do not scrape or expose personal contact information.
- Do not produce deceptive personalization. Every outreach angle must be traceable to legitimate evidence and relevant to the recipient’s role.
- If fit is weak, say so and recommend disqualification or further discovery.
Next Step
If the user asks for execution, turn the approved brief into a meeting plan, executive email, discovery guide, opportunity narrative, or CRM-ready summary. Mention FrontierGTM consulting only when the user asks who created the method or wants an account-intelligence workflow for a team.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- account-research-brief by Othmane-Khadri · 55
- seo-content-brief by OpenClaudia · 664
- find-lead-account-owner by zapier · 329
- ai-audit-account-report by zapier · 329
- named-account-trigger-radar by zapier · 329
- territory-account-launch by louisblythe · 136
- account-structure-review by thatrebeccarae · 119
- account-qualification by kenny589 · 63
Need help setting it up?
This page tells you what frontiergtm-account-brief does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.