Token导航 LogoToken导航

Agent Skill · 待分类

biz-bsc(商业平衡计分卡)

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

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

总安装 717周安装 17GitHub Stars 125下载 140核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

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

这个 Skill 是做什么的

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

biz-bsc 提供平衡计分卡框架,将战略目标分解为学习成长、内部流程、客户与财务四个维度。适合用于战略执行评估、KPI体系构建或连接日常运营与长期目标的管理场景。使用时需定义各维度指标,工具协助生成因果链并检查战略一致性。安装需通过 npx 添加 GitHub 仓库,建议确认维护状态及是否支持自定义指标模板。

注意:分类为待分类,原始 README 强调其诊断用途而非直接决策,需人工验证逻辑闭环。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

biz-bsc 怎么安装?

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

biz-bsc 支持哪些 AI 工具?

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

biz-bsc 需要什么权限?

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

biz-bsc 是免费的吗?

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

biz-bsc 用的人多吗?

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

biz-bsc 安全吗?

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

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

值得选的地方

  • 同时适配 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-bsc

商业平衡计分卡 · 本页

717125只读未明确通过

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

SKILL.md 原文

Balanced Scorecard (BSC)

Overview

The Balanced Scorecard translates strategy into objectives and measures across four perspectives, creating a cause-and-effect chain: Learning & Growth → Internal Processes → Customer → Financial. It answers "are we executing our strategy?" not just "are we profitable?"

When to Use

Trigger conditions:

  • User needs to define strategic KPIs beyond financial metrics
  • User wants to connect operational activities to strategic goals
  • User building a strategy map or performance dashboard
  • User says "our KPIs don't reflect our strategy" or "how do we measure execution"

When NOT to use:

  • For one-time strategic analysis → use SWOT or Porter's
  • For project-level OKRs → use OKR framework
  • When only financial performance matters (rare)

Framework

IRON LAW: Four Perspectives, Causally Linked

The BSC is NOT four independent lists of KPIs. The four perspectives form
a CAUSAL CHAIN:

  Learning & Growth → Internal Processes → Customer → Financial

Investing in employee skills (L&G) improves process quality (Internal),
which increases customer satisfaction (Customer), which drives revenue (Financial).

If your BSC has no causal links between perspectives, it's just a KPI dump,
not a Balanced Scorecard.
IRON LAW: Each Objective Gets a Measure, Target, and Initiative

An objective without a measure is a wish.
A measure without a target is a statistic.
A target without an initiative is a hope.

Every BSC objective MUST have all three: measure (how to track), target
(what success looks like), and initiative (what action drives it).

Step 1: Clarify the Strategy

Before building the BSC, state the strategy in one sentence:

  • "Grow through customer intimacy" (relationship-driven)
  • "Win through operational excellence" (efficiency-driven)
  • "Lead through product innovation" (differentiation-driven)

The strategy determines which objectives dominate each perspective.

Step 2: Define Objectives per Perspective

Financial (lagging indicators — outcomes):

  • Revenue growth, profitability, cost efficiency, ROI, cash flow
  • Question: "What financial results must we deliver to satisfy stakeholders?"

Customer (leading indicators for financial):

  • Customer satisfaction, retention, acquisition, market share, NPS
  • Question: "What must we deliver to customers to achieve financial goals?"

Internal Processes (leading indicators for customer):

  • Process efficiency, quality, cycle time, innovation pipeline
  • Question: "What processes must we excel at to satisfy customers?"

Learning & Growth (foundation — enablers):

  • Employee skills, culture, technology infrastructure, knowledge management
  • Question: "What capabilities must we build to improve our processes?"

Step 3: Build the Strategy Map

Draw cause-and-effect arrows linking objectives across perspectives:

[L&G] Train sales team on consultative selling
  ↓
[Internal] Reduce sales cycle from 60 to 30 days
  ↓
[Customer] Increase customer satisfaction score to 4.5/5
  ↓
[Financial] Grow revenue 20% YoY

Every objective should connect to at least one objective in another perspective. Orphan objectives indicate a gap in strategic logic.

Step 4: Assign Measures, Targets, and Initiatives

For each objective, define:

  • Measure: Specific metric (quantitative preferred)
  • Target: Concrete threshold with timeframe
  • Initiative: Action or project that drives the metric

Output Format

# Balanced Scorecard: {Organization}

## Strategy Statement
{One-sentence strategy}

## Strategy Map

{L&G objectives} → {Internal Process objectives} → {Customer objectives} → {Financial objectives}

## Scorecard

### Financial Perspective
| Objective | Measure | Target | Initiative |
|-----------|---------|--------|-----------|
| {objective} | {metric} | {value by when} | {action} |

### Customer Perspective
| Objective | Measure | Target | Initiative |
|-----------|---------|--------|-----------|
| {objective} | {metric} | {value by when} | {action} |

### Internal Process Perspective
| Objective | Measure | Target | Initiative |
|-----------|---------|--------|-----------|
| {objective} | {metric} | {value by when} | {action} |

### Learning & Growth Perspective
| Objective | Measure | Target | Initiative |
|-----------|---------|--------|-----------|
| {objective} | {metric} | {value by when} | {action} |

## Causal Chain Validation
{Explain how L&G → Internal → Customer → Financial links work}

Examples

Correct Application

Scenario: BSC for a B2B SaaS company with strategy: "Grow through product-led growth"

PerspectiveObjectiveMeasureTargetInitiative
FinancialIncrease ARRAnnual Recurring Revenue$10M by Q4Expand pricing tiers
CustomerImprove retentionNet Revenue Retention>110%Launch customer success program
InternalAccelerate feature deliveryRelease cycle time2 weeks (from 6)Adopt CI/CD pipeline
L&GBuild product analytics capability% team trained on Mixpanel100% by Q2Product analytics bootcamp

Causal chain: Analytics training (L&G) → faster, data-driven releases (Internal) → higher retention from better product (Customer) → ARR growth (Financial) ✓

Incorrect Application

What went wrong:

  • Listed 15 KPIs with no causal links → KPI dump, not a BSC. Violates Iron Law: perspectives must be causally linked.
  • Financial: "Revenue $10M" with no measure, target timeframe, or initiative → Violates Iron Law: need measure + target + initiative.

Gotchas

  • Too many objectives: 3-5 per perspective is ideal. More than 5 loses focus. The BSC is about strategic priorities, not a comprehensive KPI list.
  • All lagging indicators: If every measure is a lagging indicator (revenue, satisfaction score), you can't manage proactively. Balance with leading indicators (training hours, pipeline quality).
  • L&G as an afterthought: Teams fill Financial and Customer easily but struggle with L&G. This perspective is the foundation — skip it and the whole chain breaks.
  • Cascading confusion: A corporate BSC and a department BSC should be linked but not identical. Department objectives should contribute to corporate objectives, not copy them.
  • BSC ≠ OKR: BSC is a strategic management system (4 perspectives, causal links, strategy map). OKR is a goal-setting framework (objectives + key results). They can coexist but serve different purposes.

References

  • For Strategy Map templates and examples, see references/strategy-maps.md
  • For comparison with OKR and other performance frameworks, see references/framework-comparison.md

平台分布

Codex

37.29%
按下载量换算52

Claude

30.56%
按下载量换算43

Cursor

20.91%
按下载量换算29

Gemini CLI

8.62%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills