CtrlK
BlogDocsLog inGet started
Tessl Logo

index

Use this Sales index first for explicit Sales mentions and clear seller workflows: prospecting, lead qualification, account research, monitoring or prioritization, meeting prep, call follow-up, outreach research, deal strategy, pipeline or forecast review, CRM-backed context or data enrichment, internal source finding or sales support, customer quotes or evidence, business cases, competitive briefs, rep coaching, sales company research, and company or contact enrichment. For implicit use require clear seller, prospect, account, opportunity, pipeline, forecast, CRM, or customer-facing sales intent.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/opencode/src/skill/builtin/.bundle/sales/workflows/index/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%Weight 40%Scale 1-5

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

The content is a well-structured router/index with actionable tooling guidance and a clean reference split, but it is notably verbose with redundant connector-resolution prose that inflates the token budget. Tightening the overlapping policy sections would materially improve conciseness without losing clarity.

Suggestions

Consolidate the overlapping Category Resolution, Missing Source Resolution, and Source authority sections into a single concise rule block to remove redundant connector-availability guidance.

Trim padded prose such as the long negative-availability-claim paragraph and the audience-collaborator sentences down to their operative rules.

Move the large Cross-Skill Best Practices policy block into its own reference file, leaving the index as a lean overview that routes to focused skills and the orientation reference.

DimensionReasoningScore

Conciseness

The body is noticeably verbose, with overlapping sections (Category Resolution, Missing Source Resolution, Source authority) restating connector-availability guidance and padded prose such as the ~120-word negative-availability-claim paragraph and the audience-collaborator sentences.

2 / 5

Actionability

Provides concrete instruction-only guidance via named tools (ask_user_input, request_plugin_install), a specific reference file to load, and output-format templates, though some rules remain high-level and the templates are placeholder-laden.

4 / 5

Workflow Clarity

Sequences a clear Resolve→Gather→First Output→Next Steps flow with explicit checkpoints (20s context pass, blocking-vs-non-blocking timing, pause-until-source), but some checkpoints are prose rather than tight validate→fix→retry loops.

4 / 5

Progressive Disclosure

Clearly signals a one-level-deep reference (references/orientation-response.md, verified present) and appropriately splits the orientation response out, though the index inlines substantial cross-skill policy that could itself be a separate reference.

4 / 5

Total

14

/

20

Passed

Description

100%Weight 40%Scale 1-5

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

The description is strong: it comprehensively lists concrete sales actions, uses natural trigger terms, and explicitly covers both what the skill does and when to use it with clear distinctiveness. It is somewhat long but each enumerated term earns its place.

DimensionReasoningScore

Specificity

Enumerates many concrete seller actions (prospecting, lead qualification, account research, meeting prep, call follow-up, deal strategy, pipeline/forecast review, business cases, rep coaching, company/contact enrichment) with comprehensive coverage across the sales domain.

5 / 5

Completeness

Explicitly states both the 'what' (the enumerated seller workflows) and the 'when' via an explicit 'Use this Sales index first for explicit Sales mentions and clear seller workflows' trigger plus an implicit-use guard.

5 / 5

Trigger Term Quality

Packs in natural sales vocabulary sellers actually use (lead qualification, meeting prep, call follow-up, deal strategy, pipeline review, CRM-backed context) plus synonyms (company or contact enrichment), leaving few common phrases missing.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear sales niche with distinct triggers and an implicit-use guard requiring seller/prospect/account/opportunity/pipeline/forecast/CRM intent, minimizing the chance of triggering for unrelated skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.