CtrlK
BlogDocsLog inGet started
Tessl Logo

gather-business-context

Gather business context from connected or provided sources so downstream analysis starts with the right framing. Use when an analytical question depends on missing context, such as what a metric means, what changed recently, or which sources should be checked. If the same prompt asks for diagnosis, recommendation, or a deliverable, gather context first and continue to the focused skill.

62

Quality

73%

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/data-analytics/workflows/gather-business-context/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 body is a well-structured, actionable retrieval workflow with a clear stop condition and concrete examples. Its main weakness is conciseness, where the Standards section redundantly restates workflow guidance and could be tightened.

Suggestions

Tighten or merge the Standards section with the workflow steps to remove repetition and reduce token load on the conciseness dimension.

Add a brief explicit re-anchor/retry checkpoint in Step 2 or 3 (e.g., 'if results are thin, revise anchors before concluding the source is missing') framed as a validate-then-retry loop to lift workflow clarity toward 5.

Consider splitting the per-step guidance on source attribution and conflict reconciliation into a short reference note so the main SKILL.md stays a lean overview, improving progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but the Standards section restates guidance already covered in the workflow steps and several passages could be tightened, fitting score 3 rather than 4.

3 / 5

Actionability

Concrete procedural guidance with specific examples ('a metric plus a dashboard name, a feature plus a launch window') and named source artifacts (schemas, datasets, tables, views, metrics); as an instruction-only skill the absence of code is not penalized, leaving only minor gaps versus score 5.

4 / 5

Workflow Clarity

A clear 8-step sequence with an explicit stop-condition checkpoint (Step 7) and anchor-revision guidance; this is a retrieval task rather than a destructive/batch operation so the validation cap does not apply, but no strong validate-fix-retry loop keeps it at 4 rather than 5.

4 / 5

Progressive Disclosure

Well-organized into Boundary, Workflow, and Standards sections in a self-contained file with no content that clearly belongs in separate files; at ~60 lines it exceeds the simple-skill 50-line exception and is fully inline, so 4 rather than 5.

4 / 5

Total

15

/

20

Passed

Description

78%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 clearly states what the skill does and when to use it with concrete trigger phrases and good boundary guidance against sister skills. It is slightly less comprehensive on specific actions and natural-term synonyms, capping specificity and trigger quality just below the top.

DimensionReasoningScore

Specificity

Names the domain and a couple of concrete actions ('Gather business context from connected or provided sources', 'continue to the focused skill') but does not enumerate a comprehensive set of specific actions, matching the score-3 anchor rather than 4's broader action list.

3 / 5

Completeness

Explicitly answers both what ('Gather business context... so downstream analysis starts with the right framing') and when ('Use when an analytical question depends on missing context, such as...') with concrete trigger phrases, matching the score-5 anchor.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('what a metric means', 'what changed recently', 'which sources should be checked') with good coverage, though a few common synonyms or variations are missing, fitting score 4 over 5.

4 / 5

Distinctiveness Conflict Risk

Draws a clear niche (framing context, not the deliverable) and names distinct sister skills ($metric-diagnostics, $product-business-analysis), leaving only minor overlap risk with closely related analysis skills, so 4 rather than 5.

4 / 5

Total

16

/

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.