PolarHub
  • Agents
  • MCP Servers
  • Skills
  • PolarBear
PolarHub © 2026
技能市场测试开发benchmark-methodology
返回「测试开发」

benchmark-methodology

by affaan-m·ecc

0下载测试开发

简介

>- Use after competitive-platform-analysis has produced a tiered competitor set. Scores each competitor across nine weighted dimensions (positioning, voice, visual craft, offer packaging, evidence, enterprise-readiness, thought leadership, pricing, client's strategic tension) with explicit 1–5 rubrics and a tension-plot. Precedes competitive-report-structure.

SKILL.md 详细内容

来自 ECC · 10KB

Benchmark Methodology

Use this skill to turn a scoped competitor set into comparable, defensible scores. Each competitor is assessed on the same nine dimensions, with explicit 1–5 rubrics, then captured in a uniform profile card. Consistency is the point: scores are only useful if the same evidence would earn the same number for any competitor.

When to Activate

  • A scoped, tiered competitor set from competitive-platform-analysis is ready to score.
  • Need comparable, evidence-anchored scores across competitors — not gut-feel rankings.
  • Client's strategic tension (the paired axes defining their target white-space) has been established.
  • Preparing to produce profile cards for assembly in competitive-report-structure.

Client positioning brief (establish first)

Before scoring, establish the client's positioning brief. It supplies:

  • Strategic tension — the two axes (e.g., memorability × hireability) whose intersection marks the client's target white-space. Dimension 9 is always the client's named tension; report both poles separately, never averaged.
  • Differentiator — what makes the client's moat. This informs which dimensions matter most for the client's positioning argument.
  • Brand balance — the intended mix of distinct strategic emphases. Strategic recommendations must not break this balance without flagging it.

Why these dimensions

The client competes on a specific tension held across two poles, not on service breadth. The dimensions are weighted to reflect that moat. Two dimensions — the tension poles — are scored separately and never averaged together, because the client's strategic question is precisely whether a rival achieves both simultaneously.

The nine dimensions (with weights)

Weights guide synthesis emphasis, not a single blended score (avoid a false composite — see Bias controls). Sum = 100%.

  1. Positioning clarity & distinctiveness (18%) — Is the studio's position sharp, ownable, and instantly legible? Or generic?
  2. Brand voice / verbal distinctiveness (15%) — Does the copy have an ownable register, or is it interchangeable agency-speak?
  3. Visual identity & site craft (15%) — Quality and ownership of the visual system; site as proof-of-craft.
  4. Service offer & packaging (12%) — Productized and legible (named sprints/audits) vs vague. Packaging maturity.
  5. Evidence & credibility (12%) — Named clients, quantified outcomes, case-study depth. Proof beyond assertion.
  6. Enterprise-readiness / commercial maturity (10%) — Signals they can land and hold SaaS/fintech/B2B/enterprise work (process, logos, scale, contracts).
  7. Thought leadership / content presence (8%) — Owned POV: writing, talks, newsletters, frameworks. Depth over volume.
  8. Pricing transparency & engagement model (5%) — Is pricing/engagement legible? Productized vs bespoke vs opaque.
  9. [Client's strategic tension] (5% as a flag; score BOTH poles, report separately) — Read the tension name and axis descriptions from the client's positioning brief. Plot both; the gap is the insight. The client's target quadrant is the single most important finding: who else is already there?

Scoring rubric (1–5, applies to dimensions 1–8)

Anchor every score to observable evidence. Generic descriptors below; adapt the specifics per dimension but keep the level meaning constant.

  • 1 — Absent / generic. No discernible position or craft; indistinguishable from a template. Active liability.
  • 2 — Below par. Some intent but inconsistent, derivative, or unconvincing. Wouldn't survive a side-by-side.
  • 3 — Competent / table-stakes. Solid, professional, unremarkable. Meets expectation, ownable by nobody.
  • 4 — Strong / distinctive. Clearly above peers; a real strength a buyer would notice and cite.
  • 5 — Category-defining. Best-in-class, ownable, hard to imitate. Sets the bar others react to.

Tension axes (dimension 9) — score each 1–5

Read the axis labels and their 1/3/5 anchors from the client's positioning brief. Example anchors for a memorability × credibility tension:

  • Memorability — 1: forgotten instantly · 3: recognizable in context · 5: unforgettable, talked-about, distinctively owned.
  • Credibility — 1: feels risky/amateur · 3: safe, competent, unexciting · 5: enterprise-trusted, obvious safe choice.

Plot competitors on the tension 2×2. The client's target quadrant is named in the positioning brief. Who else occupies that quadrant is the single most important finding of the benchmark.

How to collect the data

For each competitor, work the dimensions in this order (cheapest signal first):

  1. Competitor's own site — positioning, voice, offer packaging, pricing posture, named clients, manifesto/POV. Screenshot the homepage + one case study.
  2. Case studies / work — evidence depth, quantified outcomes, client names. Distinguish asserted ("we delivered X") from proven (metrics, named, verifiable).
  3. Review directories — corroborate clients, project size, engagement model → credibility & enterprise-readiness (e.g. Clutch.co or the niche equivalent).
  4. LinkedIn — team size/model, founder narrative, content cadence → thought leadership, model.
  5. Portfolio / craft platforms — craft register (use the showcase native to the niche: design boards, showreels, published samples, etc.).
  6. Content channels — newsletter/talks/writing → thought-leadership depth.

What to record per dimension: the score, one-line justification, and the source link/screenshot that earned it. No score without evidence.

Bias controls

  • No single composite score. Report dimension scores and the tension plot separately. A weighted average hides the asymmetry that matters.
  • Asserted vs proven. Downgrade credibility/evidence scores for self-reported claims with no corroboration. Site copy is marketing, not fact.
  • Aesthetic affinity bias. Reviewers may over-score studios whose aesthetic they share and under-score rivals' commercial strength. Score craft and credibility independently; a "boring" site may be winning bigger clients.
  • Recency / flashiness bias. Award-winning, showpiece work dazzles but may lack commercial depth — verify with directories/clients before scoring credibility.
  • Survivorship. The visible, well-marketed studios aren't the whole market; note strong-but-quiet operators found via directories/reviews.
  • Calibrate across the set, not in isolation. Before finalizing, re-read scores side-by-side — a "4" must mean the same thing for every competitor. Adjust outliers.

Competitor profile card (output format)

Produce one card per profiled competitor — the atomic unit the report assembles from:

## <Competitor name>
- **Profile / Tier:** <positioning stance · specialization · size band> / <Direct | Adjacent | Aspirational>
- **One-liner:** <how they position themselves, in their words>
- **Model / size / geography:** <solo|micro|boutique> · <region> · <pricing/engagement model>
- **Notable clients / evidence:** <named, with proven/asserted tag>

### Dimension scores
| Dimension | Score (1–5) | Justification (1 line) | Source |
|---|---|---|---|
| Positioning clarity & distinctiveness | | | |
| Brand voice / verbal distinctiveness | | | |
| Visual identity & site craft | | | |
| Service offer & packaging | | | |
| Evidence & credibility | | | |
| Enterprise-readiness / commercial maturity | | | |
| Thought leadership / content presence | | | |
| Pricing transparency & engagement model | | | |

### Tension plot
- **[Axis 1 from positioning brief]:** <1–5> — <why>
- **[Axis 2 from positioning brief]:** <1–5> — <why>
- **Quadrant:** <high/high | high-1/low-2 | low-1/high-2 | low/low>

### Read for [client]
- **Strength to learn from:** <…>
- **Weakness to exploit / white-space it exposes:** <…>
- **Threat to [client]:** <…>

Hand the completed cards plus the tension plot to competitive-report-structure.

Anti-Patterns

  • Averaging the tension axes. The two poles of the client's strategic tension must be scored and reported separately. Averaging destroys the insight — the gap between poles is the finding.
  • Scoring without evidence. Every score requires a one-line justification and a source link. A score without evidence is an opinion, not a benchmark.
  • Creating a single composite score. Report dimension scores individually. A weighted average hides the asymmetric strengths that matter for positioning.
  • Applying generic rubric anchors without adapting. The 1–5 anchors must be calibrated to the specific dimension and competitor set. The generic descriptions are a starting point, not a fixed standard.
  • Running before the competitor set is scoped. Use competitive-platform-analysis first to produce a tiered, pruned set. Scoring an unscoped list wastes effort on irrelevant competitors.

Related Skills

  • competitive-platform-analysis — the prerequisite; produces the tiered competitor set this skill scores.
  • competitive-report-structure — the next step; assembles the scored profile cards into a client-deliverable report.

相关 Skills(来自「测试开发」)

测试用例生成 Skills v2.0

包含 15 个子 Skill 的测试用例生成流水线,从产品说明书读取、需求分析、测试策略、正负向用例编写、质量审查到 Excel 输出。

50

Simulink HIL Modeling Standard

通用 Simulink HIL 建模、重构、迁移、评审和发布规范。用于设计 Plant/Control/IO/Bus/Fault/Monitor 架构,定义 Subsystem、Bus、ValueType、MonBus 和 Variant 接口,治理数据字典、参数、采样时间、多核任务、引用组件和初始化流程,检查 .slx/.mdl/.sldd/MATLAB Project,或为实时 HIL 模型生成合规报告、迁移方案、测试计划与发布证据。

47

ICDConverter AVIAGE Template

航空电子系统 ICD 接口控制文件(AVIAGE SYSTEMS 格式)转标准 Template 格式转换专家,适用于 ICD 转换、接口控制文件格式统一和帧结构解析。

2

ICDConverter TIU

面向航空电子 ICD Excel 文件的标准 Template 格式转换 Skill,支持协议帧分析、颜色编码识别、字段元数据索引、帧长度校验和 Excel 输出。

2

ai-regression-testing

Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code.

0

angular-developer

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.

0

给 Agent 的安装提示词

复制下方脚本发给 AI,Agent 会自动完成下载和解压

Download and install a skill. Follow these steps EXACTLY. If any step fails, STOP and report the error.

SKILL_NAME="benchmark-methodology"
DOWNLOAD_URL="/downloads/ecc-skills/benchmark-methodology.zip"
INSTALL_CMD="Download benchmark-methodology.zip and extract it into your Agent skills directory."

STEP 1 - FIND SKILL DIRECTORY
[ -d "$HOME/.agents/skills" ] && echo "USER: $HOME/.agents/skills"
[ -d "$PWD/.agents/skills" ] && echo "PROJECT: $PWD/.agents/skills"
for d in "$HOME"/.*/skills; do [ -d "$d" ] && echo "USER: $d"; done
for d in "$PWD"/.*/skills; do [ -d "$d" ] && echo "PROJECT: $d"; done

Decide based on output (deduplicate lines first):
a) Only USER lines -> INSTALL_DIR="<that dir>/$SKILL_NAME"
b) Only PROJECT lines -> INSTALL_DIR="<that dir>/$SKILL_NAME"
c) Both USER and PROJECT -> ask the user to pick global install or project install.
d) Nothing found -> mkdir -p "$HOME/.agents/skills"; INSTALL_DIR="$HOME/.agents/skills/$SKILL_NAME"

STEP 2 - PREPARE
[ -f "$INSTALL_DIR/SKILL.md" ] && echo "EXISTS" || echo "NEW"
# If EXISTS, ask user whether to overwrite. If no, STOP.
mkdir -p "$INSTALL_DIR"

STEP 3 - DOWNLOAD
TMPDIR=$(mktemp -d)
curl -fSL -o "$TMPDIR/skill.zip" "$DOWNLOAD_URL" 2>/dev/null || wget -q -O "$TMPDIR/skill.zip" "$DOWNLOAD_URL"
# If both fail, try INSTALL_CMD as fallback: $INSTALL_CMD
# If still fail, STOP.

STEP 4 - EXTRACT & INSTALL
unzip -o "$TMPDIR/skill.zip" -d "$TMPDIR/ext" 2>/dev/null || python3 -m zipfile -e "$TMPDIR/skill.zip" "$TMPDIR/ext"
# If both fail, this is not a valid ZIP. STOP.

SKILL_PATH=$(find "$TMPDIR/ext" -maxdepth 2 -name "SKILL.md" -print | head -1)
if [ -n "$SKILL_PATH" ]; then
  cp -R "$(dirname "$SKILL_PATH")"/. "$INSTALL_DIR"/
else
  echo "FATAL: SKILL.md not found"; find "$TMPDIR/ext" -type f
fi

STEP 5 - VERIFY
head -5 "$INSTALL_DIR/SKILL.md"

DONE
Read "$INSTALL_DIR/SKILL.md" and follow its instructions to finish the user's task.
粘贴到 Claude / Cursor / Codex 等 Agent 后,会按步骤自动安装到 ~/.agents/skills/

自动安装

通过 PolarBear 协议从 ZIP 地址导入 Skill

Skill 压缩包地址
/downloads/ecc-skills/benchmark-methodology.zip

polarbear://skills/download?name=benchmark-methodology&url=%2Fdownloads%2Fecc-skills%2Fbenchmark-methodology.zip

手动安装

3 步完成

  1. 1

    下载 Skill 压缩包

    下载 ZIP
  2. 2

    将其解压到 Agent 的 Skills 目录

    ~/.agents/skills/benchmark-methodology/
  3. 3

    重启或重新加载 Agent,让 Skill 可用

    重启 Agent 客户端,或刷新会话后即可调用此 Skill。

来源

平台
ecc
作者
affaan-m
Slug
benchmark-methodology
在源站查看