CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

85%

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

The canonical home for this skill is calculator-design in rampstackco/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A well-structured, opinionated instructional skill with strong progressive disclosure (real one-level-deep references for every topic), concrete frameworks, and a worked example. Its main weakness is token efficiency: the core three-pattern framing and the reference listings are repeated across multiple sections, so roughly a third of the body could be cut without losing guidance.

Suggestions

State the vanity-calculator/lead-trap/transparent-decision-tool triad once (the keystone framing section) and reference it from the intro, anti-patterns, email-capture, and closing sections instead of restating it in full each time.

Drop either the per-section "Detail in [references/...]" links or the closing "Reference files" section — both enumerate the same nine files; keeping one (the closing list with descriptions) is sufficient.

Compress the closing section ("calculators earn the email when they would have been worth paying for"), which restates the framing, the tier/email/result/update disciplines, and the litmus test already covered in the body.

DimensionReasoningScore

Conciseness

The body is mostly non-obvious, domain-specific guidance (not concepts Claude already knows), but it is noticeably repetitious: the vanity-calculator/lead-trap/transparent-decision-tool triad is fully restated in the intro, the keystone framing section, the anti-patterns section, the email-capture section, and the closing; the reference files are listed twice (inline "Detail in" links plus the closing "Reference files" section); and the "What this skill covers" section repeats the description. This fits the 3 anchor (mostly efficient but could be tightened) better than 2, since the padding is self-repetition rather than explanation of known concepts.

3 / 5

Actionability

For an instruction-only skill the guidance is concrete: a 12-consideration design/audit framework, a worked B2B SaaS tiered-value example with per-tier contents, enumerated input types with when-to-use guidance, a specific example formula ("Your savings = (current cost x 12) - (our cost x 12) + implementation savings of $X"), and failure symptoms mapped to cures. It stops short of the 5 anchor's copy-paste-ready depth (e.g., no sample methodology-page copy or assumption-list templates inline — those are deferred to references), matching the 4 anchor: mostly concrete guidance with minor gaps.

4 / 5

Workflow Clarity

The content proceeds in a coherent order (invest-or-not decision → keystone framing → input design → transparency → result presentation → email capture → tiers → anti-patterns → failures → 12-point framework), and the litmus test ("can a stranger in the target audience defend the result to a stakeholder?") plus the lead-quality measurement consideration act as validation checkpoints. It fits the 4 anchor (clear sequence, most checkpoints present, minor gaps) rather than 5, since the 12 considerations are a checklist rather than an explicitly sequenced workflow with error-recovery feedback loops. No destructive/batch operations, so the workflow-clarity cap does not apply.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview: each topic section states its principles concisely and defers detail via "Detail in [references/X.md]" links, all nine referenced files exist in the bundle (verified against the references/ listing), and references are one level deep. The closing "Reference files" section with one-line descriptions aids discovery. This matches the 5 anchor: clear overview with well-signaled one-level-deep references and appropriately split content.

5 / 5

Total

16

/

20

Passed

Description

91%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.

A strong description that explicitly answers what the skill does and when to use it, with comprehensive natural trigger terms and named diagnostic patterns. The only weakness is that a few broad trigger terms ("interactive tool", "decision tool") create minor overlap risk with adjacent interactive-tool skills.

DimensionReasoningScore

Specificity

The description names the domain and enumerates concrete calculator types ("ROI calculators, pricing estimators, savings projections, mortgage calculators, custom assessments") plus three named diagnostic patterns (vanity-calculator, lead-trap, transparent-decision-tool). It falls just short of the 5 anchor, which expects multiple distinct concrete actions rather than one design action applied across enumerated artifact types.

4 / 5

Completeness

Both questions are answered explicitly and concretely: what ("Designing interactive calculators... that deliver real decision-support value while serving as lead magnets and qualified-traffic generators") and when ("Triggers on calculator, ROI calculator... Also triggers when an audience needs a calculation-driven lead magnet..."). This mirrors the 5 anchor's structure of a clear what followed by explicit trigger phrases; the 'Triggers on...' clause is equivalent explicit trigger guidance, so the 3-cap for missing trigger guidance does not apply.

5 / 5

Trigger Term Quality

"Triggers on calculator, ROI calculator, pricing estimator, savings calculator, custom calculator, interactive tool, decision tool, financial calculator" is a comprehensive list of natural user terms with synonyms, augmented by situational triggers ("when a vanity calculator is producing leads but no qualified ones, or when a calculator is being scoped for the first time"). Matches the 5 anchor's comprehensive natural-term coverage; no common variation is obviously missing.

5 / 5

Distinctiveness Conflict Risk

The calculator-design niche is clear and mostly distinct, but the generic trigger terms "interactive tool" and "decision tool" invite minor overlap with closely related skills (e.g., a quiz-and-assessment-design sister skill covering interactive/decision tools). This fits the 4 anchor (mostly distinct, minor overlap risk with closely related skills) better than the 5 anchor's minimal-conflict bar.

4 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rampstackco/claude-skills

Path

dist/codex/.agents/skills/calculator-design/SKILL.md

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.