by affaan-m·ecc
>- 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.
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.
Before scoring, establish the client's positioning brief. It supplies:
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.
Weights guide synthesis emphasis, not a single blended score (avoid a false composite — see Bias controls). Sum = 100%.
Anchor every score to observable evidence. Generic descriptors below; adapt the specifics per dimension but keep the level meaning constant.
Read the axis labels and their 1/3/5 anchors from the client's positioning brief. Example anchors for a memorability × credibility tension:
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.
For each competitor, work the dimensions in this order (cheapest signal first):
What to record per dimension: the score, one-line justification, and the source link/screenshot that earned it. No score without evidence.
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.
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.包含 15 个子 Skill 的测试用例生成流水线,从产品说明书读取、需求分析、测试策略、正负向用例编写、质量审查到 Excel 输出。
通用 Simulink HIL 建模、重构、迁移、评审和发布规范。用于设计 Plant/Control/IO/Bus/Fault/Monitor 架构,定义 Subsystem、Bus、ValueType、MonBus 和 Variant 接口,治理数据字典、参数、采样时间、多核任务、引用组件和初始化流程,检查 .slx/.mdl/.sldd/MATLAB Project,或为实时 HIL 模型生成合规报告、迁移方案、测试计划与发布证据。
航空电子系统 ICD 接口控制文件(AVIAGE SYSTEMS 格式)转标准 Template 格式转换专家,适用于 ICD 转换、接口控制文件格式统一和帧结构解析。
面向航空电子 ICD Excel 文件的标准 Template 格式转换 Skill,支持协议帧分析、颜色编码识别、字段元数据索引、帧长度校验和 Excel 输出。
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.
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.