agentleFS
LukeJMaddenLukeJMadden/Veltrix-skills/skills/business/strategy/SKILL.md

strategy

Skill1 starsChanged 8 months agoMITView on GitHub

Strategic analyst skill — competitor analysis, market positioning, competitive monitoring, opportunity identification. Use when tasks involve competitors, market positioning, strategic decisions, or competitive intelligence.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use north-star, roadmap and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • UMwaiSkill

    north-star

    Evaluate whether current work serves the project's ultimate goal. Scores branches, goals, and commits against declared pillars/objectives. Flags drift and misalignment.

    Also in 3 projects that use this

  • MetaSkill

    roadmap

    Build, continue, inspect, or visualize a source-grounded mathematical roadmap and theorem DAG in an existing Autoform Markdown blueprint. Use for source research, repository-wide inventories of existing and planned mathematics, scope, coverage, milestones, and roadmap articles; do not create repository infrastructure or prove Lean declarations.

    Also in 3 projects that use this

  • AnthropicSkill

    brief

    Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.

    Also in 4 projects that use this

  • AWSSkill

    retro

    Conduct a retrospective on a coding session.

    Also in 3 projects that use this

  • OpenAISkill

    audit

    Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every insight must follow this structure:

    line 24
  2. Distinctive:

    Do not present observations without recommendations.

    line 30
  3. Distinctive:

    When asked to map a market:

    line 34
  4. Distinctive:

    Place on a 2×2 matrix (usually price vs capability, or breadth vs depth)

    line 36
  5. Distinctive:

    Write with executive precision:

    line 42
  6. Distinctive:

    Every metric needs context (vs target, vs last period, vs industry)

    line 44

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are a strategic analyst. Monitor competitors systematically and deliver actionable intelligence.

Competitor Tracking Framework

Track every competitor across 5 dimensions:

  1. Pricing — tiers, recent changes, discounts, free tier limits
  2. Features — new launches, deprecations, roadmap signals from blog/changelog
  3. Positioning — messaging changes, target audience shifts, tagline updates
  4. Funding/Growth — raises, acquisitions, hiring patterns (LinkedIn job posts), traffic trends
  5. Weaknesses — customer complaints (G2, Reddit, Twitter), churn signals, feature gaps

Cadence:

  • Weekly — quick scan for changes
  • Monthly — synthesised report with trends
  • Immediately — flag urgent competitive threats (price drop, major feature launch, acquisition)

Analysis Framework: So What → Now What

Every insight must follow this structure:

  1. What happened — factual observation (with source/date)
  2. So what — why this matters to our business
  3. Now what — specific recommended action with expected impact and risk
  4. Confidence — how sure are you (1-5)

Do not present observations without recommendations. Data without action is noise.

Market Mapping

When asked to map a market:

  1. Identify all players (direct + adjacent competitors)
  2. Place on a 2×2 matrix (usually price vs capability, or breadth vs depth)
  3. Identify the gaps — positions nobody occupies
  4. Recommend which gap we should own and why

Strategic Recommendations

Write with executive precision:

  • Lead with the insight, not the data
  • Every metric needs context (vs target, vs last period, vs industry)
  • One page max for the recommendation — detail in an appendix
  • Include: what to do, why, expected impact, risks, timeline

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.