add-stats-dimension

Checklist for adding or changing a statistics table/dimension in the collector. Use whenever touching SQLite schema, traffic write paths, retention, ClickHouse parity, or stats query APIs — several places must change together or data silently drifts.

Quality

100%

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

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, highly actionable checklist with a clear ordered workflow, explicit verification, and clean section organization tailored to a coupled codebase. It is a strong instruction-only skill with no meaningful structural weaknesses.

Dimension	Reasoning	Score
Conciseness	The body is dense and high-signal, assumes Claude's competence (no explanations of what SQLite/ClickHouse/Vitest are), and every bullet earns its place by pairing a concrete file/function with a bug-preventing rationale; the lone v1.3.9/dated-doc reference is provenance for a standing rule, not rotting temporal instruction.	3 / 3
Actionability	Concrete file paths, named functions (batchUpdateTrafficStats, buildRuleName, deleteBackendData), config keys (connectionLogsDays, hourlyStatsDays), and one executable SQL snippet give exact, actionable guidance despite being instruction-only.	3 / 3
Workflow Clarity	Eight ordered steps worked "in order" with an explicit validation checkpoint (step 8: add a Vitest case then run the verify-changes skill), so the destructive/batch database operations are not left without verification.	3 / 3
Progressive Disclosure	Around 50 lines, single-purpose, no bundle files, and organized into eight clearly labeled sections, which the rubric's simple-skills note says is sufficient for a top score.	3 / 3
	Total	12 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 specific, well-triggered description that clearly states both what the skill does and when to use it, with concrete domain terms unlikely to collide with other skills. The only minor nit is the inline version/date citation, but it does not undermine the description's strength.

Dimension	Reasoning	Score
Specificity	Names concrete actions ("adding or changing a statistics table/dimension") plus multiple specific areas (SQLite schema, traffic write paths, retention, ClickHouse parity, stats query APIs), matching the multiple-specific-actions anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Explicitly answers both what ("Checklist for adding or changing a statistics table/dimension in the collector") and when ("Use whenever touching SQLite schema, traffic write paths, retention, ClickHouse parity, or stats query APIs") with an explicit Use-when trigger.	3 / 3
Trigger Term Quality	Natural terms the target developer would actually say ("statistics table/dimension", "SQLite schema", "retention", "ClickHouse parity", "stats query APIs") give good coverage rather than opaque jargon.	3 / 3
Distinctiveness Conflict Risk	A clearly scoped niche (stats dimensions in a specific collector tied to SQLite/ClickHouse/traffic write paths) makes it unlikely to trigger for unrelated skills, satisfying the distinct-triggers anchor.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: foru17/neko-master
Path: .claude/skills/add-stats-dimension/SKILL.md
Commit: 6f72cfd

Reviewed: 23 days 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.