Name: startup-metrics-framework
Rating: 48.8 (1 reviews)
Author: administrakt0r

startup-metrics-framework

Comprehensive guide to tracking, calculating, and optimizing key performance metrics for different startup business models from seed through Series A.

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/startup-metrics-framework/SKILL.md

The canonical home for this skill is startup-metrics-framework in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

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

The body is lean in length but content-poor: generic boilerplate instructions with no executable guidance and a reference to a file that is absent from the bundle. It reads as an untemplated placeholder rather than a working skill.

Suggestions

Replace the generic instruction bullets with metric-specific, actionable guidance — e.g., formulas for CAC, LTV, burn rate, and runway, with worked examples.

Either create `resources/implementation-playbook.md` with the detailed patterns and examples, or remove the broken reference.

Add concrete validation checkpoints (e.g., sanity-checking metric ratios against benchmarks) instead of the abstract "validate outcomes" step.

Dimension	Reasoning	Score
Conciseness	The body is short and mostly lean, with only minor waste such as the verbatim duplicate of the frontmatter description. Not a 5 because that duplicate line and the generic placeholder bullets ("Clarify goals, constraints, and required inputs") do not fully earn their tokens.	4 / 5
Actionability	Instructions are high-level hints ("Apply relevant best practices and validate outcomes") with no concrete formulas, code, or commands tied to startup metrics. Not a 1 because it gestures at steps; not a 3 because nothing is executable.	2 / 5
Workflow Clarity	A rough abstract sequence (clarify → apply → validate → provide steps) is present, but steps are poorly defined and validation is a generic mention with no checkpoint. Not a 3 because no concrete validation or feedback loop is specified.	2 / 5
Progressive Disclosure	Sections are present and a reference is signaled one level deep, but it points to `resources/implementation-playbook.md`, which does not exist in the bundle. A broken reference defeats navigation. Not a 3 because the referenced detail file is missing rather than merely loosely signaled.	2 / 5
	Total	10 / 20 Passed

Description

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

The description conveys a clear purpose and a reasonably specific niche, but omits any explicit trigger guidance, which caps its completeness. It is solid but not exemplary.

Suggestions

Add a "Use when..." clause naming concrete triggers, e.g., "Use when the user asks about startup KPIs, unit economics, or metrics for seed/Series A fundraising."

Replace generic verbs with metric-specific actions (e.g., "calculating CAC, LTV, burn rate, and runway") to lift specificity and trigger-term coverage.

Drop the "Comprehensive guide to" framing to reduce over-claim padding.

Dimension	Reasoning	Score
Specificity	"tracking, calculating, and optimizing key performance metrics" names several concrete actions within the startup-metrics domain, though "Comprehensive guide" is mild over-claim padding. Not a 5 because the actions are generic verbs without metric-specific coverage (e.g., CAC, LTV, burn).	4 / 5
Completeness	It clearly states what the skill does but has no "Use when..." trigger clause, which caps completeness at 3 per the judging guidelines. Not a 4 because the "when" is entirely absent rather than weakly implied.	3 / 5
Trigger Term Quality	"key performance metrics", "startup business models", and "seed through Series A" are natural phrases users would say. Not a 5 because common synonyms (KPIs, unit economics, burn rate, runway) and stage variations are missing.	4 / 5
Distinctiveness Conflict Risk	"startup business models from seed through Series A" carves a specific niche with minor overlap risk against generic analytics skills. Not a 5 because "metrics framework" is broad enough to brush against general analytics or business-planning skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/startup-metrics-framework/SKILL.md
Commit: 57c135b

Reviewed: 16 hours ago

Table of Contents

Discovery Implementation Validation

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.