CtrlK
BlogDocsLog inGet started
Tessl Logo

db-conventions

Data-layer invariants for the collector — SQLite patterns, transactions, time keys, backendId isolation, ClickHouse read/write topology. Use when writing queries, touching repositories, or debugging data drift.

68

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 tightly written, highly actionable conventions skill with excellent token efficiency and clean organization. The one gap is workflow clarity: for batch/transactional and range-query operations it lists what to do but lacks explicit validation/retry checkpoints the rubric expects for destructive/batch work.

Suggestions

Add an explicit validation checkpoint for flush/range-query changes (e.g. verify per-group outcome before clearing the realtime store, or assert SQLite and ClickHouse query results match after implementing a *WithRouting method).

For range-query additions, spell out a short fix-and-retry loop: implement both counterparts, run a parity check, and only merge when semantics match.

State the verification step for backend deletion explicitly (confirm all tables in deleteBackendData were cleared) to close the destructive-operation feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: dense invariants, named file paths, and SQL fragments with no padding or explanations of concepts Claude already knows; every line carries a concrete constraint.

3 / 3

Actionability

Concrete, executable guidance throughout — exact SQL expressions (the INSTR delimiter-aware dedup pattern), specific method/file paths (batchUpdateTrafficStats, toMinuteKey), named env flags, and a table of flag meanings; no pseudocode.

3 / 3

Workflow Clarity

Multi-step constraints are stated (route via *WithRouting, implement BOTH repository and clickhouse.reader.ts counterparts) and a partial-failure contract is named, but there are no explicit validation checkpoints or fix-and-retry feedback loops for the batch/transactional operations the guidelines themselves flag as fragile.

2 / 3

Progressive Disclosure

Well-organized single-file skill under 50 lines with clear sections (Invariants, SQLite usage, ClickHouse topology, Partial-failure contract); no bundle files exist, so the sectioned structure fully satisfies the simple-skill allowance.

3 / 3

Total

11

/

12

Passed

Description

77%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 strong, specific description with an explicit 'Use when' clause and a clear collector-scoped niche. Its only weakness is trigger-term naturalness: it relies on internal jargon more than the phrases a user would naturally say.

Suggestions

Add more user-natural trigger phrasings (e.g. 'stats queries', 'data drift', 'ClickHouse reads') alongside the internal terms so it matches how users actually phrase requests.

Consider mirroring common variations of the trigger terms (e.g. 'SQL queries', 'repository changes') to broaden natural-keyword coverage.

DimensionReasoningScore

Specificity

Lists several concrete capability areas — 'SQLite patterns, transactions, time keys, backendId isolation, ClickHouse read/write topology' — each a distinct, named action rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Data-layer invariants ... SQLite patterns, transactions ...') and when ('Use when writing queries, touching repositories, or debugging data drift'), satisfying the 'Use when...' clause requirement.

3 / 3

Trigger Term Quality

'writing queries, touching repositories, debugging data drift' are reasonable user-facing triggers, but the term set leans on internal jargon (backendId, ClickHouse topology) and omits common natural phrasings a user would say, so it stops short of full coverage.

2 / 3

Distinctiveness Conflict Risk

Scoped to a single app's data layer (apps/collector) with collector-specific terms (backendId, traffic stats, ClickHouse routing), giving it a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
foru17/neko-master
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.