iptvnator-sqlite-db-worker

Use when changing Electron SQLite IPC, database-worker operations, request-scoped progress or cancellation, worker packaging, or runtime verification of non-EPG database work.

Quality

68%

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 ./.codex/skills/iptvnator-sqlite-db-worker/SKILL.md

Quality

Content

75%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 a lean, well-structured single-file skill that assumes Claude's competence and supplies concrete commands, file paths, and behavioral rules with a verification-backed rebuild workflow.

Dimension	Reasoning	Score
Conciseness	The body is dense and codebase-specific (file paths, the request chain, identity semantics, env vars) with no padding about concepts Claude already knows, matching 'efficient; minor instances of over-explanation'; not a 5 because the 13-line ownership list and a few dense sentences could be marginally tightened.	4 / 5
Actionability	Provides copy-paste-ready commands ('pnpm nx test electron-backend', 'pnpm nx run electron-backend:build-worker', 'stat ...', 'IPTVNATOR_TRACE_DB=1') and concrete directives ('prepared writes must use .run()'), matching 'mostly executable guidance; concrete code or commands with minor gaps'; not a 5 because several sections are constraints/ownership rather than executable steps.	4 / 5
Workflow Clarity	The 'Rebuild and Verify' section is a clear sequenced workflow with explicit verification checkpoints (stat artifact, confirm timestamp, run E2E/CDP), satisfying the destructive/batch validation requirement; not a 5 because there is no explicit error-recovery feedback loop ('if E2E fails, fix and re-run').	4 / 5
Progressive Disclosure	Well-organized into clear sections (Ownership and Flow, Identity/Progress/Cancellation, Rebuild and Verify) with a one-level-deep pointer to the canonical guide and the SQL-trace summary; matches 'good structure; most content appropriately placed; references mostly clear'.	4 / 5
	Total	16 / 20 Passed

Description

62%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 has a strong, highly specific trigger clause with excellent distinctiveness, but it is missing an explicit 'what this skill does' statement and leans on internal jargon rather than natural user phrasing.

Suggestions

Lead with a short 'what' clause before the 'Use when' trigger, e.g. 'Guides changes to the Electron SQLite database-worker IPC layer and its operations. Use when ...'.

Soften jargon in the trigger list toward terms a developer would naturally say (e.g. 'SQLite IPC', 'database worker', 'progress and cancellation') and add common synonyms.

Keep the 'non-EPG' boundary but consider phrasing it as a positive scope statement to make the trigger read more naturally.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete action areas ('changing Electron SQLite IPC', 'database-worker operations', 'request-scoped progress or cancellation', 'worker packaging', 'runtime verification'), matching the 'lists several specific actions; minor gaps' anchor; not a 5 because some items are scope areas rather than crisply discrete actions.	4 / 5
Completeness	A strong explicit 'Use when...' trigger (the 'when') is present, but there is no explicit 'what does this skill do' statement — the capability is only weakly implied by the trigger list, mirroring the score-3 condition of one half clear and the other weakly implied.	3 / 5
Trigger Term Quality	Relevant keywords exist (SQLite, IPC, database-worker, progress, cancellation) but the phrasing is jargon-heavy ('request-scoped progress', 'non-EPG database work') and lacks natural synonyms a developer would casually say, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	A clear narrow niche (Electron SQLite DB worker) with an explicit 'non-EPG' boundary that actively reduces overlap with the EPG skill, matching 'clear niche with distinct triggers; minimal conflict risk'.	5 / 5
	Total	15 / 20 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: 4gray/iptvnator
Path: .codex/skills/iptvnator-sqlite-db-worker/SKILL.md
Commit: 069b8b3

Reviewed: ~15 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.