CtrlK
BlogDocsLog inGet started
Tessl Logo

build-competitive-brief

Use when the user wants a competitor or vendor comparison, market-landscape analysis, battlecard, objection package, positioning brief, or account-specific competitive view. Produce an evidence-backed comparison, guidance, and brief, using supplied materials, connected research, and public evidence when appropriate.

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable instruction-only skill with a clear sequenced workflow, copy-paste output templates, and correctly progressive references to real bundle files. The main weakness is verbosity in the automation-guard and repeated guardrail sections rather than any gap in guidance.

Suggestions

Tighten the 'Automation Offer Guard' section and consolidate the repeated 'do not post, send, share, or turn unsupported claims into customer-facing assertions' wording into a single canonical rule to reduce token cost.

Consider moving the lengthy automation-prompt template into references/ and linking to it, keeping SKILL.md focused on the core research-and-brief workflow.

Trim overlapping guidance between 'Next Step Options', 'Next steps to avoid', and 'Rules' where the same constraints are restated.

DimensionReasoningScore

Conciseness

The body is dense and largely operational rather than padded with concepts Claude already knows, but the lengthy 'Automation Offer Guard' and repeated 'do not post/send/share' guardrails across multiple sections could be tightened; it sits at the score-2 anchor of mostly efficient with some removable text.

2 / 3

Actionability

Provides concrete, copy-paste-ready guidance: an exact output-contract template, 1-v-1 and 1-v-many matrix formats with example rows, file-naming rules, and a fill-in automation prompt block, satisfying the instruction-only equivalent of fully executable guidance.

3 / 3

Workflow Clarity

Six numbered phases are clearly sequenced and include an explicit validation checkpoint ('Read the generated file back and verify… render it once and fix blank pages, broken layout…'), giving the feedback loop the score-3 anchor requires.

3 / 3

Progressive Disclosure

SKILL.md is a self-contained overview that signals three real one-level-deep references (request-schema.yaml, source-priority.md, output-contract.md — all present on disk) with clear 'Use [reference] when…' load triggers, matching the well-signaled one-level-deep anchor.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, trigger-rich description that concisely states both what the skill produces and when to use it, with natural competitive-sales vocabulary and a distinct niche. No material weakness; the 'Use when…' construction mirrors the rubric's good examples rather than a penalized second-person phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and outputs ('competitor or vendor comparison, market-landscape analysis, battlecard, objection package, positioning brief, or account-specific competitive view' and 'Produce an evidence-backed comparison, guidance, and brief'), matching the score-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

Clearly answers both what ('Produce an evidence-backed comparison, guidance, and brief') and when (explicit 'Use when the user wants…' clause), matching the score-3 anchor with an explicit trigger.

3 / 3

Trigger Term Quality

Uses natural seller-facing keywords a user would actually say ('battlecard', 'vendor comparison', 'market-landscape analysis', 'objection package', 'positioning brief'), giving good coverage rather than technical jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear competitive-brief/battlecard niche with distinct triggers, making it unlikely to fire for an unrelated skill; not below because the scope is sharply delineated.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository
XiaomiMiMo/MiMo-Code
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.