SKILLEMALL.ai
GitHub ↗ RU Sign in

BC metrics-dashboard

Pick the 5 metrics that matter at a startup's current stage, with definitions, targets, actions when below target, a minimal tracking setup, and a weekly review template. Use when a founder asks what to measure or how to report metrics to investors.

emotixco/claude-skills-founder Claude Code author: emotixco 1 file body ≈ 743 tokens Open the sourcegithub.com↗ analyzed 10 h ago

Pick the 5 metrics that matter at a startup's current stage, with definitions, targets, actions when below target, a minimal tracking setup, and a weekly…

As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

ProcedureData and analyticstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
84
Run on models
none yet
Process rating
C
58/100
Has gaps
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: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 58/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
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 1 mutating operations with no state check
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 20 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 743 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
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 249: enough signal without eating the budget
    • +4Structure: 9 headings
    • +3Step-by-step instructions: 20 items
    • +4Has examples (1 code blocks)

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