CtrlK
BlogDocsLog inGet started
Tessl Logo

math-model-selector

Routes problems to appropriate mathematical frameworks using expert heuristics

54

Quality

60%

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 ./bundled/skills/math-model-selector/SKILL.md
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.

The body is a well-structured, actionable routing skill: a concrete decision tree, output template, and worked example give clear executable guidance with a clean sequenced workflow. The main weakness is mild token redundancy from the duplicated "Key Questions to Ask" list and the overlapping example/Co-activates sections, which keeps conciseness from the top score.

DimensionReasoningScore

Conciseness

The body is largely lean decision-tree bullets with minimal concept explanation, but the "Key Questions to Ask" section duplicates the Process steps and the worked example plus "Co-activates" restate earlier material, tipping it from the lean-and-efficient anchor at 3 to the mostly-efficient-but-could-be-tightened anchor at 2.

2 / 3

Actionability

It gives a concrete 5-step decision tree with explicit "Ask" prompts, a copy-ready output format template, and a fully worked example mapping to a specific ODE and equation; the guidance is specific and actionable even though no executable code is included (an instruction/routing skill, which the rubric does not penalize for lacking code).

3 / 3

Workflow Clarity

The Process is a clearly numbered 5-step sequence each led by an explicit question, with the example tracing the same Q1–Q5 flow to a recommendation; this is a non-destructive routing skill so the destructive-ops validation cap does not apply, matching the clear-sequence anchor.

3 / 3

Progressive Disclosure

This is a simple single-file skill with no external bundle files, and the content is organized into clearly labeled sections (When to Use, Process, Output Format, Example, Co-activates), which per the rubric's simple-skills note lets progressive disclosure score 3 without external references.

3 / 3

Total

11

/

12

Passed

Description

35%

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 states a clear purpose but is too abstract: it names a single routing action, relies on jargon ("expert heuristics"), and omits any explicit "Use when..." trigger guidance. It is distinguishable as a math-routing skill but risks overlap with broader math skills. Adding concrete actions and natural trigger phrasing would raise it across all dimensions.

Suggestions

Add a "Use when..." clause with natural user phrasings such as "Use when the user has a problem but isn't sure which mathematical framework (ODEs, optimization, probability, PDEs) applies".

Replace the abstract "routes problems" with concrete actions, e.g. "Identifies the right mathematical framework (differential equations, optimization, probability, combinatorics) by walking through change, uncertainty, and optimization questions".

Drop the jargon "expert heuristics" in favor of plain terms users would actually say (model, framework, equation, formalize).

DimensionReasoningScore

Specificity

"Routes problems to appropriate mathematical frameworks using expert heuristics" names a domain and a single routing action but does not list multiple concrete capabilities, matching the anchor for names-domain-and-some-actions rather than the multiple-concrete-actions anchor at 3.

2 / 3

Completeness

It states what the skill does (routes problems to frameworks) but has no "Use when..." clause or equivalent trigger, which per the judging guidelines caps completeness at 2; not 1 because the what is clearly stated.

2 / 3

Trigger Term Quality

The description contains no natural keywords a user would say (no "math", "model", "equation"); "expert heuristics" is technical jargon, matching the no-natural-keywords anchor rather than the some-relevant-keywords anchor at 2.

1 / 3

Distinctiveness Conflict Risk

"Mathematical frameworks" signals a niche, but the description is generic enough that it could overlap with general math/modeling skills and lacks distinct triggers, matching the somewhat-specific-but-could-overlap anchor.

2 / 3

Total

7

/

12

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
foryourhealth111-pixel/Vibe-Skills
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.