Competitive Executive Market Brief logo

Competitive Executive Market Brief

Organization
LMTYdotcom
competitive-executive-market-brief

Prepare a concise, decision-oriented market and competitive brief for executives, leadership reviews, QBRs, board preparation, strategy discussions, or major planning moments. Use when leadership needs the few market changes, competitor moves, risks, opportunities, and decision questions that matter, with evidence and explicit uncertainty rather than a long CI report.

Overview

PublisherLMTYdotcom
Repositoryskills
Skill namecompetitive-executive-market-brief
Stars
83
Forks
2
Bundled files
8
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.

  • 8 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by LMTYdotcom on GitHub. Read the source before you install it.

Installation

Install the Competitive Executive Market 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/LMTYdotcom/skills/tree/main/skills/competitive-executive-market-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/LMTYdotcom/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/competitive-executive-market-brief .claude/skills/competitive-executive-market-brief
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Competitive Executive Market 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 Competitive Executive Market 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 Competitive Executive Market 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.

Competitive Executive Market Brief

Mission

Turn market context into an executive decision surface.

The brief should tell leadership what changed, why it matters to the company's current priorities, what is uncertain, and which decisions or questions deserve attention.

It should not be a compressed competitor newsletter.

Use this skill when

  • preparing for a board or leadership meeting
  • creating a QBR competitive section
  • briefing a CEO, CMO, CPO, CRO, or product leader
  • a strategic planning cycle needs market context
  • leadership asks "what changed and what should I care about?"
  • a PMM wants to prevent being blindsided in an executive conversation
  • a launch, pricing decision, or strategic shift needs executive market context

Do not use this skill when

  • the audience primarily wants operational weekly updates. Use competitive-market-briefing.
  • the user needs a full competitor teardown. Use competitive-deep-dive.
  • the user needs a detailed position, pricing, or launch work product. Use the corresponding skill, then summarize here.

Required outcome

Produce a brief that answers:

  1. What materially changed in the relevant period?
  2. Which changes matter to current company priorities?
  3. What market pattern or strategic implication is worth leadership attention?
  4. What is likely noise or not yet decision-relevant?
  5. What risks could surprise the company?
  6. What opportunities or openings may exist?
  7. Which assumptions are weak?
  8. What decisions, research, or monitoring should leadership authorize or discuss?

Context acquisition

Read references/CONTEXT.md. If call, CRM, win/loss or company-knowledge sources are connected, read references/INTERNAL.md before using them.

Minimum useful context:

  • company/product
  • meeting or audience
  • relevant time period if different from a sensible default

Strongly preferred:

  • company priorities, goals, or strategic motion
  • LMTY briefing and significant changes
  • current market report
  • product roadmap or launch context
  • revenue/deal/customer signals
  • prior leadership decisions when available

If current company priorities cannot be retrieved, ask only if the answer would materially alter the brief. Otherwise create a market-grounded brief and label the missing internal lens.

Source priority for this job

  1. current company priorities and decision context
  2. LMTY significant changes and briefing
  3. internal customer, deal, product, and revenue signals
  4. current report and competitor evidence
  5. external corroboration for material claims

Workflow

Step 1 - Identify the executive decision context

Determine:

  • audience
  • meeting type
  • current strategic priorities
  • decisions likely to be made
  • time horizon

A board brief and a product leadership QBR should select different market facts.

Step 2 - Gather significant market movement

Use LMTY briefing and change filters when available.

Prioritize:

  • pricing/packaging moves affecting economics or buyer expectations
  • product launches affecting differentiation or roadmap assumptions
  • positioning shifts affecting category narrative
  • target-customer movement
  • new entrants with actual evidence of relevance
  • market patterns supported by multiple signals

Step 3 - Link market movement to internal reality

When internal sources exist, ask:

  • Are these changes appearing in deals?
  • Are customers asking for them?
  • Do they affect current launches or roadmap?
  • Do they affect strategic assumptions?
  • Do they alter the company's position or pricing narrative?

This step is what separates an executive brief from a news summary.

Step 4 - Prioritize by decision consequence

Rank items using:

  • potential business impact
  • relevance to current priority
  • evidence strength
  • time sensitivity
  • reversibility of a wrong decision

Do not rank by headline size or competitor fame.

Step 5 - Separate signal from noise

Include a short "not yet worth reacting to" section when the market is noisy.

This is useful executive value, especially when a Slack channel or news cycle is creating anxiety.

Step 6 - Surface risks and openings

Risks should be specific and evidence-linked.

Openings should be framed as hypotheses or questions unless customer/company evidence makes them stronger.

Step 7 - Create decision questions

A strong executive brief ends with a small number of questions such as:

  • Does this change an assumption behind our current pricing plan?
  • Do we need customer research before committing roadmap capacity?
  • Should we change launch language because our claimed difference is now parity?
  • Is this entrant appearing in enough deals to warrant active tracking?

Avoid generic "keep monitoring" as the only action.

Step 8 - Hand off what you do not own

Requests routinely arrive as two questions joined by "and". Answer the one this skill owns, in full. For the rest, name the skill that owns it and stop there.

This is not a refusal and it is not a disclaimer at the bottom. Write it as a line the reader can act on:

Pricing - the board question is really whether to change our pricing. That is a separate decision: run competitive-pricing-packaging-review with this analysis as input.

One line per area the work touched, named explicitly:

The request also wantsSay to run
field talk tracks, objection handling, or a rep-facing cardcompetitive-battlecard
a market position, messaging, or differentiationcompetitive-positioning
a full profile of one competitorcompetitive-deep-dive
launch framing, claims, or enablement for a releasecompetitive-launch-readiness
a recurring digest of what changedcompetitive-market-briefing
whether a pattern is a real shift or noisecompetitive-market-shift-analysis
a pricing or packaging decisioncompetitive-pricing-packaging-review

The failure this prevents is quietly answering the other half yourself. It looks helpful, and it produces a recommendation built on this skill's evidence alone, without the context the other decision actually needs.

Step 9 - Produce the artifact

Use assets/executive-brief-template.md.

Default length:

  • one page for leadership/QBR
  • up to two pages for board or strategy prep

Put source detail in an appendix.

Evidence and reasoning rules

Read references/TRUST.md.

Especially for executive briefs:

  • increase burden of proof as the decision consequence rises
  • do not hide contradictions
  • label speculative scenarios
  • distinguish "competitor moved" from "we need to respond"
  • preserve dates and freshness for material claims

Graceful fallback

Read references/DEGRADATION.md. For what LMTY can and cannot do, read references/LMTY.md.

Without company priorities:

  • produce a market-grounded brief
  • replace strong recommendations with decision questions

Without LMTY:

  • research a current snapshot and cite collection dates
  • avoid implying comprehensive monitored coverage

Composition

Each companion below owns a decision this skill should not make on its own evidence. The hand-off step is where the request's own follow-on question gets named.

Common inputs from:

  • competitive-market-briefing
  • competitive-market-shift-analysis
  • competitive-positioning
  • competitive-pricing-packaging-review
  • competitive-launch-readiness
  • competitive-deep-dive

Quality bar

Read references/QUALITY.md.

An executive should understand the decision landscape in under five minutes.

Every included item should answer "why is this in front of me?"

Examples of activating requests

  • "Prepare the competitive section for our QBR."
  • "I have a board meeting Friday. What market changes could blindside me?"
  • "Brief the CPO on what changed this quarter and the roadmap questions it raises."
  • "Turn this month's LMTY activity into a CEO-ready one-pager."
  • "What should leadership discuss based on the last 90 days of competitor movement?"

References

  • references/METHODOLOGY.md
  • references/LMTY.md
  • references/TRUST.md
  • references/CONTEXT.md
  • references/DEGRADATION.md
  • references/INTERNAL.md
  • references/QUALITY.md

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Competitive Executive Market Brief AI skill do?

Prepare a concise, decision-oriented market and competitive brief for executives, leadership reviews, QBRs, board preparation, strategy discussions, or major planning moments. Use when leadership needs the few market changes, competitor moves, risks, opportunities, and decision questions that matter, with evidence and explicit uncertainty rather than a long CI report.

Why use Competitive Executive Market Brief on TypingMind?

Because you install it once and use it with any model. Competitive Executive Market 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 Competitive Executive Market Brief in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/LMTYdotcom/skills/tree/main/skills/competitive-executive-market-brief. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Competitive Executive Market 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 Competitive Executive Market Brief?

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

Is the Competitive Executive Market Brief AI skill free?

Yes. It is published on GitHub by LMTYdotcom 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 👇