SKILLEMALL.ai

BB finance-metrics-quickref

Look up SaaS finance metrics, formulas, and benchmarks fast. Use when you need a quick metric definition, formula, or benchmark during analysis.

deanpeters/Product-Manager-Skills Claude Code author: deanpeters NOASSERTION 2 files body ≈ 3 844 tokens Open the sourcegithub.com↗ analyzed 4 d ago

Look up SaaS finance metrics, formulas, and benchmarks fast.

As a process B 68/100 · Nearly there — weak spots: result and completion, failures and branches, running it twice

AnalyzerData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
85
Run on models
none yet
Process rating
B
68/100
Nearly there
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "intent"
    • note frontmatter-key unknown frontmatter key "type"
    • note frontmatter-key unknown frontmatter key "best_for"
    • note frontmatter-key unknown frontmatter key "scenarios"
    • note frontmatter-key unknown frontmatter key "theme"
    • note frontmatter-key unknown frontmatter key "estimated_time"

    Process rating: all ten parameters 68/100

    • 0Result and completion. Does not say what the result is
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 7 mutating operations with no state check
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 100 steps
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3844 tokens

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 144: enough signal without eating the budget
    • +4Structure: 25 headings
    • +3Step-by-step instructions: 100 items
    • +4Has examples (0 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.