Token导航 LogoToken导航

Agent Skill · 待分类

biz-pestel(商业佩斯特尔)

biz-pestel 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

biz-pestel 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 7,288。

总安装 374周安装 15GitHub Stars 125下载 121核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/asgard-ai-platform/skills --skill biz-pestel

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

biz-pestel 扫描宏观环境六大维度,识别影响行业的外部趋势与风险。适用于新市场进入、政策合规评估或战略规划前期扫描的场景。使用时输入目标国家/行业,工具按政治、经济、社会、技术、环境、法律分类输出因素。安装需通过 npx 添加 GitHub 仓库,建议确认是否更新最新法规与事件数据库。

注意:分类为待分类,结果为可能性列表,需结合本地知识过滤无关项。

来源仓库内路径:skills/biz-pestel

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

biz-pestel 怎么安装?

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

biz-pestel 支持哪些 AI 工具?

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

biz-pestel 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

biz-pestel 是免费的吗?

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

biz-pestel 用的人多吗?

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

biz-pestel 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

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

待分类类 Skill 对比

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

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
biz-pestel

商业佩斯特尔 · 本页

374125只读未明确通过

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

SKILL.md 原文

PESTEL Analysis

Overview

PESTEL scans the macro-environment across six dimensions to identify external forces that could impact a business or industry. It operates at the macro level — broader than industry (Porter's Five Forces) or company (SWOT). Use it to surface trends and risks the organization cannot control but must respond to.

When to Use

Trigger conditions:

  • User evaluating a new market or country for expansion
  • User needs to understand regulatory, economic, or social trends
  • User wants to identify macro risks before strategic planning
  • User asks "what external factors should we consider?"

When NOT to use:

  • For company-specific assessment → use SWOT
  • For industry competitive dynamics → use Porter's Five Forces
  • For product portfolio decisions → use BCG Matrix

Framework

IRON LAW: Macro-Level Only

PESTEL factors are MACRO-ENVIRONMENT forces — they affect all players in
a market, not just one company. "Our costs are rising" is not a PESTEL factor.
"Inflation is driving up input costs across the industry" is.

Test: "Does this factor affect ALL companies in this market?"
  YES → Valid PESTEL factor
  NO  → It belongs in SWOT or Five Forces, not PESTEL
IRON LAW: Evidence-Based, Not Speculative

Every PESTEL factor must be grounded in observable data, trends, or events.
"Technology might change" is not a factor. "5G rollout reaching 70% coverage
by 2026 (GSMA data)" is a factor.

Step 1: Define the Scope

  • What entity? Country, region, or market being analyzed
  • For whom? Which business or industry perspective
  • Time horizon: near-term (1-2 years) or medium-term (3-5 years)

Step 2: Scan Each Dimension

For each of the six dimensions, identify 2-4 key factors with evidence:

P — Political: Government stability, trade policy, taxation policy, political risk, corruption, foreign investment rules

E — Economic: GDP growth, inflation, interest rates, exchange rates, unemployment, consumer spending power, commodity prices

S — Social: Demographics, cultural trends, consumer attitudes, lifestyle changes, education levels, urbanization, health consciousness

T — Technological: R&D activity, automation, digital infrastructure, emerging technologies, innovation rate, tech transfer

E — Environmental: Climate change, sustainability regulations, resource scarcity, carbon emissions rules, environmental awareness, natural disaster risk

L — Legal: Employment law, consumer protection, data privacy (GDPR, PDPA), industry-specific regulation, IP protection, antitrust

Step 3: Assess Impact and Likelihood

For each factor:

  • Impact on the business: High / Medium / Low
  • Likelihood of change: High / Medium / Low
  • Direction: Favorable (+) or Unfavorable (−)

Step 4: Prioritize and Connect

  1. Rank factors by impact × likelihood
  2. Identify cross-dimensional connections (e.g., political instability → economic uncertainty → social unrest)
  3. Highlight the top 3-5 factors that require strategic response

Output Format

# PESTEL Analysis: {Market/Country} for {Business Context}

## Scope
- Market: ...
- Perspective: ...
- Time horizon: ...

## PESTEL Factors

| Dimension | Factor | Evidence | Impact | Direction |
|-----------|--------|----------|--------|-----------|
| Political | ... | ... | H/M/L | +/− |
| Economic | ... | ... | H/M/L | +/− |
| Social | ... | ... | H/M/L | +/− |
| Technological | ... | ... | H/M/L | +/− |
| Environmental | ... | ... | H/M/L | +/− |
| Legal | ... | ... | H/M/L | +/− |

### Political
{Detailed analysis}

### Economic
{Detailed analysis}

### Social
{Detailed analysis}

### Technological
{Detailed analysis}

### Environmental
{Detailed analysis}

### Legal
{Detailed analysis}

## Priority Factors
1. {Highest impact factor} — {required response}
2. ...
3. ...

## Cross-Dimensional Connections
- {Factor A} → {Factor B} → {combined implication}

Examples

Correct Application

Scenario: PESTEL for Vietnam market, perspective of a Taiwanese food manufacturer (2025-2028)

DimensionFactorEvidenceImpactDirection
PoliticalVietnam-Taiwan informal trade relations stable; no diplomatic frictionBilateral trade volume growing YoYMed+
EconomicVietnam GDP growth 6.5% (2024), rising middle classWorld Bank data, urban consumer spending up 12%High+
SocialYoung population (median age 31), increasing demand for packaged foodUN demographic data, urbanization rate 39% → projected 45% by 2030High+
TechnologicalCold chain logistics still underdeveloped outside Ho Chi Minh and HanoiOnly 30% of food supply chain has cold storage (VCCI report)High−
EnvironmentalGovernment tightening plastic packaging regulationsDecree on solid waste management (2024) requiring recyclable packagingMed−
LegalFood safety registration (Decree 15/2018) requires 6-month approval cycleForeign food products need Certificate of Free Sale + lab testing in-countryHigh−

Incorrect Application

Scenario: Same Vietnam market analysis

What went wrong:

  • "Our factory is running at 80% capacity" → Company-level fact, not macro factor. Violates Iron Law: PESTEL is macro-level only.
  • "Technology is changing fast" → No evidence, no specificity. Violates Iron Law: evidence-based, not speculative. What technology? What change? What data?

Gotchas

  • Overlap between dimensions: A factor can span multiple dimensions (e.g., "data privacy law" is both Legal and Technological). Place it where the primary impact lies, and note the connection.
  • Country-level, not city-level: PESTEL typically analyzes national macro factors. If sub-national differences matter (e.g., China's tier-1 vs tier-3 cities), note them as variations within the dimension.
  • Snapshot vs trend: A PESTEL factor should capture the direction of change, not just current state. "GDP is $X" is a fact; "GDP growing at 6.5% with acceleration trend" is a useful factor.
  • Too many factors: Listing 10+ factors per dimension creates noise. Keep to 2-4 per dimension, prioritized by impact.
  • Missing the "So what?": Each factor needs an implication for the business. "Population is aging" without "→ shifting demand toward health products" is incomplete.

References

  • For comparison with other strategy frameworks, see references/framework-comparison.md
  • For country-specific PESTEL data sources, see references/data-sources.md

平台分布

Codex

35%
按下载量换算42

Claude

31.35%
按下载量换算38

Cursor

17.67%
按下载量换算21

Gemini CLI

10.14%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills