Token导航 LogoToken导航

Agent Skill · 研究检索

strategy-document(战略文件)

strategy-document 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

strategy-document 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 12,407。

总安装 10,290周安装 442GitHub Stars 750下载 3,607核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:strategy-document(战略文件)
来源仓库:https://github.com/jezweb/claude-skills
仓库路径:skills/strategy-document
安装命令:
npx skills add https://github.com/jezweb/claude-skills --skill strategy-document
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/jezweb/claude-skills --skill strategy-document

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

strategy-document 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于基于关键词或任务场景的信息搜集与筛选需求。通过 npx skills add 命令从指定 GitHub 仓库安装并使用。

安装前需确认权限范围、维护状态及是否涉及联网或文件操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/strategy-document

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/jezweb/claude-skills --skill strategy-document;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

strategy-document 怎么安装?

在终端执行 npx skills add https://github.com/jezweb/claude-skills --skill strategy-document。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

strategy-document 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

strategy-document 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

strategy-document 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

strategy-document 用的人多吗?

公开数据是累计安装 10,290 次,近一周安装 442 次,下载 3,607 次,GitHub 750 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

strategy-document 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
strategy-document

战略文件 · 本页

10,290750需要联网未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Strategy Document Writer

Produces strategic documents that are specific enough to act on. The quality bar: every statement should be falsifiable ("We have 3 React developers with 10+ years experience" vs "We have a strong team") and every recommendation should be implementable within a defined timeframe.

Process

Step 1: Determine the mode

Ask the user which document type they need:

  1. SWOT analysis — assess current position
  2. Business plan (lean or full) — articulate the business model
  3. OKRs / Goals — set measurable objectives
  4. Competitive analysis — understand the market landscape

If the user is unsure, ask what decision they are trying to make. That usually reveals the right mode:

  • "Should we enter this market?" -> Competitive analysis + SWOT
  • "What should we focus on this quarter?" -> OKRs
  • "We need funding / a partner deck" -> Business plan
  • "Something feels off but I can't pinpoint it" -> SWOT

Step 2: Gather context

Ask for:

  • Business name, industry, size (team, revenue if comfortable sharing)
  • Current situation (what prompted this exercise?)
  • Key competitors (if known)
  • Time horizon (this quarter, this year, 3-year)
  • Audience for the document (internal team, board, investors, bank, personal clarity)

The audience determines the level of detail. A bank wants financial projections. A founder wants clarity. A team wants direction.

Step 3: Draft and validate

Write the document, then review every entry against the specificity test: could this statement apply to any business in the industry? If yes, it is too vague. Rewrite with the user's specific context.


Mode 1: SWOT Analysis

Structure

Present as a 2x2 grid with 3-5 points per quadrant. Each point is one sentence — specific and actionable.

             HELPFUL                    HARMFUL
          to achieving objectives    to achieving objectives

INTERNAL  STRENGTHS                  WEAKNESSES
(origin)  - ...                      - ...
          - ...                      - ...

EXTERNAL  OPPORTUNITIES              THREATS
(origin)  - ...                      - ...
          - ...                      - ...

Internal (Strengths, Weaknesses) = things the business controls: team skills, processes, technology, finances, culture, IP.

External (Opportunities, Threats) = things the business does not control: market trends, competitors, regulation, economic conditions, technology shifts.

Quality bar for entries

Too vagueSpecific and useful
"Strong team""3 developers with 10+ years React experience; only 1 has backend skills"
"Good reputation""4.8 Google rating from 127 reviews; 94% client retention over 3 years"
"Growing market""Australian SME SaaS market growing 12% annually (IBISWorld 2025)"
"Competition""Competitor X launched a free tier in Q4 2025, capturing 200+ of our target segment"
"Cash flow issues""Average debtor days: 58; target: 30. $120K outstanding beyond 60 days"

Every entry should pass the "so what?" test — it must be clear why this point matters for strategic decisions.

The "So What?" Section

After the grid, add a section that translates findings into actions:

Strategic implications:

  • Which strengths can be leveraged against which opportunities? (attack)
  • Which weaknesses are exposed by which threats? (defend)
  • What should the business start doing, stop doing, or change?

This is the most valuable part of a SWOT. The grid without implications is an exercise in categorisation, not strategy.

Anti-patterns

  • Listing the same point in both Strengths and Opportunities (if it is internal, it is a strength)
  • Including items the business cannot influence in Strengths/Weaknesses
  • Generic entries that apply to every business in the industry
  • No implications section — the grid alone is not actionable

Mode 2: Business Plan

Lean format (one page)

Use when the audience is the founder or a small team needing clarity. One paragraph per section, no padding.

SectionWhat to write
ProblemWhat pain exists? Who feels it? How do they cope today?
SolutionWhat does the business offer? In one sentence.
Key Metrics3-5 numbers that indicate health (MRR, churn, CAC, LTV, NPS)
Unique Value PropWhy this business over alternatives? One sentence.
ChannelsHow do customers find you? Rank by effectiveness.
Revenue StreamsHow does money come in? List each stream with approximate % of total.
Cost StructureTop 5 cost categories with approximate monthly/annual figures.
Unfair AdvantageWhat cannot be easily copied? (team expertise, proprietary data, network effects, regulatory position)

The test for each section: if you cannot say it in one paragraph, you do not understand it well enough yet. Rewrite until you can.

Full format

Adds to the lean format:

  • Executive Summary (write last — it summarises everything else)
  • Market Analysis — TAM/SAM/SOM with sources, customer segments, market trends
  • Financial Projections — 12-month P&L, cash flow forecast, break-even analysis
  • Team — key people, their relevant experience, gaps to fill
  • Milestones — what happens in the next 3, 6, and 12 months with specific deliverables

Writing principles for plans

  • Present tense for current state, future tense for plans. Never past tense for the core model.
  • Financial projections must state assumptions explicitly. "$50K MRR by month 12" needs "assuming 15% monthly growth from current $12K base and 5% churn."
  • Acknowledge risks. Investors and lenders trust founders who see the dangers, not those who pretend they do not exist.
  • No aspirational filler. "We aim to be the leading provider" is not a plan. "We will acquire 200 paying customers in 12 months through Google Ads ($5K/month budget, target $25 CAC)" is a plan.

Mode 3: OKRs and Goals

Structure

OBJECTIVE: [Qualitative, inspiring, time-bound]

  KR1: [Quantitative, measurable, has a number]
  KR2: [Quantitative, measurable, has a number]
  KR3: [Quantitative, measurable, has a number]

Typically 3-5 Objectives per quarter, each with 3-5 Key Results.

Objectives

  • Qualitative and inspiring — describes the desired future state
  • Time-bound (usually one quarter)
  • Ambitious but achievable with stretch effort (70% completion = healthy)
Too vagueSpecific
"Improve our marketing""Establish a predictable inbound lead pipeline by end of Q2"
"Grow the business""Expand into the Brisbane market with a repeatable sales process by Q3"
"Be more efficient""Eliminate manual reporting bottlenecks across all client accounts by Q2"

Key Results

  • Quantitative with a specific target number
  • Measurable — you can check at quarter end whether it was achieved
  • Outcomes, not tasks
Task (wrong)Outcome (right)
"Launch the new website""Achieve 1,000 monthly organic visitors to the new site"
"Hire 2 developers""Reduce average feature delivery time from 3 weeks to 1 week"
"Run Google Ads campaign""Generate 50 qualified leads at under $30 CAC"
"Write 12 blog posts""Grow organic traffic 40% (800 to 1,120 monthly sessions)"

Tasks are the activities you do to achieve Key Results. They belong on a project plan, not in OKRs.

Scoring

At quarter end, score each KR from 0.0 to 1.0:

  • 0.0-0.3: Failed to make meaningful progress
  • 0.4-0.6: Made progress but fell short
  • 0.7-0.9: Delivered strong results (this is the target zone)
  • 1.0: Hit the target exactly (may indicate the target was too easy)

If every OKR scores 1.0, the goals were not ambitious enough. If every OKR scores below 0.3, they were unrealistic or the wrong priorities.


Mode 4: Competitive Analysis

Structure

Start with a comparison matrix, then interpret it.

Comparison matrix:

FactorYour BusinessCompetitor ACompetitor BCompetitor C
Price point$X/mo$Y/mo$Z/moFree tier + $W/mo
Key feature 1YesYesNoPartial
Key feature 2NoYesYesYes
Target marketAU SMEsEnterpriseStartupsAll segments
StrengthPersonal serviceScalePriceBrand recognition
WeaknessSmall teamImpersonalLimited featuresSlow support

Interpretation sections

Where you win: Specific advantages with evidence. "Faster onboarding (3 days vs industry average of 2 weeks)" not "better service".

Where you lose: Honest assessment. "Competitor A has 10x our development team; we cannot match their feature velocity" is more useful than pretending the gap does not exist.

Where you differentiate: What you do that others structurally cannot or choose not to. This is the strategic gold — it informs positioning, messaging, and product decisions.

Recommended actions: Based on the analysis, what should change? New features to build, segments to target or avoid, pricing adjustments, partnership opportunities.

Research sources

  • Competitor websites (pricing pages, feature lists, case studies)
  • Review sites (G2, Capterra, Google Reviews, ProductHunt)
  • Job listings (reveal their priorities and gaps)
  • Social media and content (positioning, audience, tone)
  • Industry reports (market size, growth rates, trends)

If the user has access to competitors' actual customers (through industry networks, forums, social media), first-hand feedback is more valuable than any published report.


Writing Principles (All Modes)

Specific over vague. Every claim needs a number, a name, or a concrete example. "Strong growth" is not strategy — "40% revenue increase from $850K to $1.19M" is strategy.

Evidence over opinion. "We believe the market is growing" vs "The AU SaaS market grew 12% in 2025 (source)." If you cannot find evidence, say so — an honest gap is better than a fabricated claim.

Actionable over aspirational. Every section should answer "what do we do with this information?" If a SWOT entry or competitive insight does not lead to a decision or action, it is not worth including.

Honest about weaknesses. Strategy documents that only list strengths are useless. The value is in seeing the full picture — including the uncomfortable parts. Investors, partners, and teams all trust honesty more than polish.

Appropriate length. A lean business plan is one page. A SWOT is one page plus implications. OKRs are a few pages at most. Competitive analysis scales with the number of competitors. Do not pad for length — every sentence must earn its place.

Example: SWOT Strength Entry

Too vague:

Strong digital presence and good online reputation.

Right approach:

4.8 average Google rating from 127 reviews (highest among Newcastle web agencies). Website generates 35 qualified leads per month organically, with a 12% conversion rate to paying clients. Social media following of 2,400 across LinkedIn and Instagram, with 6.2% average engagement rate on case study posts.

The second version gives the reader three data points they can compare against competitors, benchmark against industry averages, and track over time.

平台分布

Codex

36.07%
按下载量换算1,301

Claude

28.07%
按下载量换算1,012

Cursor

16.61%
按下载量换算599

Gemini CLI

9.29%
按下载量换算335

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills