Brief
alirezarezvani/claude-skills
/cs:brief <topic — Generate a one-page strategy brief from an office-hours intake.
Prepare for an industry analyst briefing (Gartner, Forrester, IDC and similar).
MITAuto-check passed
Install Analyst Relations Brief
$ npx skills add mohitagw15856/pm-claude-skills --skill analyst-relations-brief -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills analyst-relations-brief --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/analyst-relations-brief .claude/skills/analyst-relations-brief && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "analyst-relations-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/analyst-relations-brief into .claude/skills/analyst-relations-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyst-relations-brief", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/analyst-relations-briefType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill analyst-relations-brief -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills analyst-relations-brief --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/analyst-relations-brief .agents/skills/analyst-relations-brief && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "analyst-relations-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/analyst-relations-brief into .agents/skills/analyst-relations-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyst-relations-brief", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill analyst-relations-brief -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills analyst-relations-brief --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/analyst-relations-brief .cursor/skills/analyst-relations-brief && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "analyst-relations-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/analyst-relations-brief into .cursor/skills/analyst-relations-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyst-relations-brief", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/analyst-relations-brief--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill analyst-relations-brief -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills analyst-relations-brief --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/analyst-relations-brief .gemini/skills/analyst-relations-brief && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "analyst-relations-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/analyst-relations-brief into .gemini/skills/analyst-relations-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyst-relations-brief", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills analyst-relations-briefInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill analyst-relations-brief -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/analyst-relations-brief .github/skills/analyst-relations-brief && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "analyst-relations-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/analyst-relations-brief into .github/skills/analyst-relations-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyst-relations-brief", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill analyst-relations-brief -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills analyst-relations-brief --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/analyst-relations-brief .opencode/skills/analyst-relations-brief && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "analyst-relations-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/analyst-relations-brief into .opencode/skills/analyst-relations-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyst-relations-brief", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
analyst-relations-brief- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 507 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Prepare for an industry analyst briefing (Gartner, Forrester, IDC and similar).
- Works in 7 steps: Set the objective — what a good outcome… → Frame the market — the category, the… → Tell the narrative — problem, approach,… → …
- Asked to prep an analyst briefing
- SKILL.md covers What This Skill Produces, Required Inputs, Process and Output Format, plus 11 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Analyst Relations Brief is an agent skill from mohitagw15856/pm-claude-skills. Prepare for an industry analyst briefing (Gartner, Forrester, IDC and similar). Use when asked to prep an analyst briefing, write an AR briefing document, build talking points for an analyst call, or prepare a Magic Quadrant / Wave submission narrative. Produces a briefing kit — objective, company/product narrative, differentiation, proof points, the demo storyline, anticipated questions, and follow-up commitments.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to prep an analyst briefing
- Write an AR briefing document
- Build talking points for an analyst call
- Prepare a Magic Quadrant / Wave submission narrative
Example prompts
- “/analyst-relations-brief”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Set the objective — what a good outcome looks like and the single message to land.
- Frame the market — the category, the shift, and where you play; align to the analyst's taxonomy.
- Tell the narrative — problem, approach, why now, why you.
- Prove it — evidence that survives scrutiny; concede limits honestly.
- Map the demo to the analyst's criteria — show, don't tell.
- Pre-empt hard questions — pricing, scale, competition, gaps; prepare honest answers.
- Plan follow-up — what you'll send, by when, and how you'll track the relationship.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Analyst Relations Brief loads about 1.1k tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 507 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 507 words, ~1,070 tokens.
Download SKILL.mdSave it as
.claude/skills/analyst-relations-brief/SKILL.md (or your agent's skills folder).- name
- analyst-relations-brief
- description
- Prepare for an industry analyst briefing (Gartner, Forrester, IDC and similar). Use when asked to prep an analyst briefing, write an AR briefing document, build talking points for an analyst call, or prepare a Magic Quadrant / Wave submission narrative. Produces a briefing kit — objective, company/product narrative, differentiation, proof points, the demo storyline, anticipated questions, and follow-up commitments.
Analyst Relations Brief Skill
Prepare a crisp, credible analyst briefing that lands the company's narrative and positions it well for evaluations. Analysts reward clear differentiation backed by evidence — not marketing gloss.
What This Skill Produces
- A briefing objective and the one message to land
- A tight company + product narrative and market framing
- Differentiation and proof points an analyst can verify
- A demo storyline mapped to the analyst's evaluation criteria
- Anticipated tough questions with honest answers, plus follow-ups
Required Inputs
Ask for these if not provided:
- The analyst / firm and their coverage area, plus any evaluation (Magic Quadrant, Wave, MarketScape) in play
- Objective — inclusion in an evaluation, repositioning, launch awareness, feedback
- Company & product basics — what it does, who it's for, traction
- Differentiation and the proof (customers, metrics, architecture)
- Roadmap themes you can share (and what's confidential)
- Known analyst views or prior feedback, if any
Never fabricate metrics, customers, or roadmap dates — mark [to confirm] and flag anything under NDA.
Process
- Set the objective — what a good outcome looks like and the single message to land.
- Frame the market — the category, the shift, and where you play; align to the analyst's taxonomy.
- Tell the narrative — problem, approach, why now, why you.
- Prove it — evidence that survives scrutiny; concede limits honestly.
- Map the demo to the analyst's criteria — show, don't tell.
- Pre-empt hard questions — pricing, scale, competition, gaps; prepare honest answers.
- Plan follow-up — what you'll send, by when, and how you'll track the relationship.
Output Format
Analyst Briefing Kit — [Firm / Analyst]
Date: [date] · Objective: [outcome] · Evaluation in play: [MQ / Wave / none]
The One Message
[The single thing the analyst should remember.]
Market Framing
[The category shift and where you fit, in the analyst's language.]
Company & Product Narrative
- What we do: [one line] · For: [ICP]
- Why now: [market shift] · Traction: [customers / growth — or
[to confirm]]
Show full SKILL.md (199 more words)Show less
Differentiation & Proof
| Differentiator | Why it matters | Proof (verifiable) |
|---|---|---|
| [Point] | [analyst-relevant value] | [customer / metric / architecture] |
Demo Storyline (mapped to evaluation criteria)
- [Criterion] → [what we show]
- [Criterion] → [what we show]
Anticipated Questions
| Likely question | Honest answer | Where we're weak (and the plan) |
|---|---|---|
| [Question] | [answer] | [gap + roadmap theme] |
Roadmap Themes to Share
- [Theme] — [shareable direction] · [confidential: yes/no]
Follow-Ups
- [Deliverable] — [owner] — [by when]
Quality Checks
- The one message is explicit and repeated in the narrative
- Differentiators map to the analyst's evaluation criteria
- Every proof point is verifiable, or marked
[to confirm] - Weak spots are acknowledged with a credible plan, not hidden
- Confidential/NDA items are clearly flagged
- Follow-ups have owners and dates
Anti-Patterns
- Do not use marketing superlatives an analyst will discount
- Do not dodge gaps — analysts probe them; own them with a plan
- Do not invent metrics, logos, or roadmap dates
- Do not ignore the analyst's taxonomy and force your own category
- Do not overload the demo; map it to what's being evaluated
Example Trigger Phrases
- "Prep me for a Gartner briefing next week"
- "Write an analyst briefing document for our platform"
- "Build talking points and anticipated questions for a Forrester Wave call"
- "Prepare our narrative for a Magic Quadrant submission"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/analyst-relations-brief of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Analyst Relations Brief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Analyst Relations Brief this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Briefalirezarezvani/claude-skills | 28k | — | ~967 | Automated safety check: Pass | MIT | |
| Industry Chain Analystdigoal/blog | 8.6k | — | ~1.9k | Automated safety check: Pass | GPL-2.0 | |
| Briefdavepoon/buildwithclaude | 3.6k | — | ~1.3k | Automated safety check: Notes | MIT | |
| Harness Similarityruvnet/ruflo | 74k | — | ~866 | Automated safety check: Notes | MIT | |
| Public Relationscoreyhaines31/marketingskills | 54k | — | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
Industry Chain Analyst
digoal/blog
以资深投行分析师的视角，输入一个行业或产业名称，系统梳理该行业产业链各节点，列出各节点代表性上市公司，深度分析商业模式、上下游关系、核心竞争力、护城河、风险揭露、竞争格局等，用通俗易懂的语言面向普通投资人输出图文并茂的Markdown报告，保存到当前项目 markdown/…
Brief
davepoon/buildwithclaude
Session-start briefing from Origin. An agent skill from davepoon/buildwithclaude.
Harness Similarity
ruvnet/ruflo
ADR-152 — weighted similarity between two harness fingerprints (genome + score JSON).
Public Relations
coreyhaines31/marketingskills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests).
Public Relations
sickn33/agentic-awesome-skills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests).
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Questions about Analyst Relations Brief
What does Analyst Relations Brief do?
Prepare for an industry analyst briefing (Gartner, Forrester, IDC and similar). Analyst Relations Brief is an agent skill from mohitagw15856/pm-claude-skills. Prepare for an industry analyst briefing (Gartner, Forrester, IDC and similar).
When should I use Analyst Relations Brief?
Analyst Relations Brief fits situations like: asked to prep an analyst briefing; write an AR briefing document; build talking points for an analyst call; prepare a Magic Quadrant / Wave submission narrative.
How do I install Analyst Relations Brief in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill analyst-relations-brief -a claude-code`. Or copy the skill folder (skills/analyst-relations-brief in mohitagw15856/pm-claude-skills) into .claude/skills/analyst-relations-brief in your project. Claude Code loads it when a task matches its description.
How do I install Analyst Relations Brief in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill analyst-relations-brief -a codex`. Or copy the skill folder (skills/analyst-relations-brief in mohitagw15856/pm-claude-skills) into .agents/skills/analyst-relations-brief in your project. Codex loads it when a task matches its description.
Can I use Analyst Relations Brief in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill analyst-relations-brief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyst-relations-brief, .gemini/skills/analyst-relations-brief, .github/skills/analyst-relations-brief and .opencode/skills/analyst-relations-brief in your project.
What does Analyst Relations Brief need to run?
SKILL.md names no scripts, command-line tools or credentials: Analyst Relations Brief is instructions for the agent only.
Does Analyst Relations Brief access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Analyst Relations Brief safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Analyst Relations Brief use?
Analyst Relations Brief is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Analyst Relations Brief use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Analyst Relations Brief?
Skills that share tags, products or a category with Analyst Relations Brief: Brief (alirezarezvani/claude-skills, 28k stars), Industry Chain Analyst (digoal/blog, 8.6k stars), Brief (davepoon/buildwithclaude, 3.6k stars) and Harness Similarity (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Analyst Relations Brief?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.