CtrlK
BlogDocsLog inGet started
Tessl Logo

calculator-design

Designing interactive calculators (ROI calculators, pricing estimators, savings projections, mortgage calculators, custom assessments) that deliver real decision-support value while serving as lead magnets and qualified-traffic generators. Honest about vanity-calculator (no real value), lead-trap (hides the answer behind email), and transparent-decision-tool (gives the result and earns the email through tiered value) patterns. Triggers on calculator, ROI calculator, pricing estimator, savings calculator, custom calculator, interactive tool, decision tool, financial calculator. Also triggers when an audience needs a calculation-driven lead magnet, when a vanity calculator is producing leads but no qualified ones, or when a calculator is being scoped for the first time.

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

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 playbook with excellent progressive disclosure into verified reference files and a clear sequenced framework. Its main weakness is conciseness: the core framing is restated across several sections and the closing largely recapitulates earlier points.

Suggestions

Consolidate the vanity-calculator/lead-trap/transparent-decision-tool framing so it is defined once and only referenced elsewhere; remove the recapitulation in the closing section.

Cut repeated methodology-disclosure and tiered-value restatements (e.g. in the 12-considerations list and closing) since each already has a dedicated section pointing to a reference file.

Tighten the prose in 'Calculation logic transparency' and 'Result presentation' to directive bullets, since the surrounding paragraphs re-explain why trust matters.

DimensionReasoningScore

Conciseness

The ~287-line body reiterates the vanity-calculator/lead-trap/transparent-decision-tool framing in the intro, a dedicated section, anti-patterns, common failures, and the closing, and restates methodology/tiered-value points multiple times; it is mostly efficient domain guidance but could be tightened well below the lean score-3 bar. It is not score 1 because the padding is repeated domain methodology rather than basic concepts Claude already knows.

2 / 3

Actionability

For an instruction-only skill it gives concrete, copy-ready directives: named input types with when-to-use, four methodology-disclosure options with examples, named result-presentation patterns, a worked 3-tier B2B SaaS example, and a 12-point framework — going beyond the score-2 'some concrete guidance but incomplete'.

3 / 3

Workflow Clarity

The '12 considerations for calculator design' is an explicit ordered checklist from the calculator decision through lead-quality measurement, with earn/don't-invest decision criteria and a closing litmus test; this is a design/audit skill (not a destructive or batch operation), so the score-2 validation cap does not apply and the sequence-with-checklist matches the score-3 anchor.

3 / 3

Progressive Disclosure

The body is an overview that consistently pushes detail to one-level-deep reference files via 'Detail in references/...md' links plus a consolidated reference list, and all nine referenced files exist on disk; this matches the score-3 'clear overview with well-signaled one-level-deep references' rather than the score-2 inline-wall case.

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.

The description is specific, trigger-rich, and complete, answering both what the skill does and when to use it with natural user-facing keywords and a clearly distinct niche. Voice is third-person throughout, so no specificity penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete calculator types ('ROI calculators, pricing estimators, savings projections, mortgage calculators, custom assessments') and specific framing actions, matching the 'lists multiple specific concrete actions' anchor rather than the score-2 'domain and some actions'.

3 / 3

Completeness

Explicitly states what ('Designing interactive calculators...that deliver real decision-support value') and when ('Triggers on...' plus 'Also triggers when an audience needs a calculation-driven lead magnet, when a vanity calculator is producing leads but no qualified ones, or when a calculator is being scoped for the first time'), with explicit trigger guidance keeping it above the score-2 cap.

3 / 3

Trigger Term Quality

'Triggers on calculator, ROI calculator, pricing estimator, savings calculator, custom calculator, interactive tool, decision tool, financial calculator' gives broad coverage of natural terms a user would say, exceeding the score-2 'some relevant keywords but missing common variations'.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche (calculator design as a specific lead-magnet type) with distinctive framing vocabulary (vanity-calculator / lead-trap / transparent-decision-tool) and specific triggers, making overlap with sibling skills unlikely; above the score-2 'could still overlap' anchor.

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
rampstackco/claude-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.