CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

database-operation

Use this skill when you need to inspect, query, maintain, or carefully modify the MoviePilot database. This skill uses the bundled scripts/mp-db.py helper, which reads MoviePilot local settings itself and never requires database passwords or full PostgreSQL DSNs in the agent prompt. Applicable scenarios include data statistics, counts, aggregations, inspecting or fixing records, cleanup requests, and questions like "how many downloads", "show site stats", "delete old records", or "why is this subscription stuck".

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-structured skill body with executable commands, ready-made SQL examples, and meaningful safety checkpoints for destructive writes. Its weaknesses are token efficiency and file structure: a ~220-line inline table catalog (partly redundant with the live schema command the skill itself designates as authoritative) and a repeated systemconfig gating explanation.

Suggestions

Move the Core Tables catalog (the per-table Purpose/Useful queries/Write boundary/Columns entries) into a references/ file such as references/core-tables.md, keeping only the most-frequently-used tables (downloadhistory, subscribe, transferhistory, site) inline with a pointer to the full catalog.

Explain the systemconfig gate once (e.g., in Built-in Safety) and reference it briefly from the other sections instead of restating the rule in Scope And Boundaries, Commands, and Built-in Safety.

Add a post-write verification step to the Workflow (e.g., re-run the query after a write to confirm the intended rows changed and the affected row count matched expectations), which would also raise workflow clarity.

DimensionReasoningScore

Conciseness

The command, workflow, and safety sections are tight, but the ~220-line Core Tables catalog inlines full column lists even though the document itself says 'Always treat the live schema <table> result as authoritative', and the systemconfig gating rule is explained three separate times (Scope And Boundaries, Commands, Built-in Safety). This is 'mostly efficient but includes some unnecessary explanation or could be tightened' — above the 2 anchor's pervasive padding but below the 4 anchor's minor trimmings.

3 / 5

Actionability

Every command is copy-paste ready ('python scripts/mp-db.py tables', 'schema downloadhistory', 'query --file /path/to/query.sql', the --show-secrets example) and the Common Queries section provides nine complete SQL examples covering the common cases, plus a dialect-comparison table and troubleshooting entries. This matches the 5 anchor's 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.

5 / 5

Workflow Clarity

The Workflow is a clear five-step sequence (prefer existing tools → tables → schema → narrow SELECT with LIMIT → write and report affected row count) with real checkpoints for destructive operations: confirm first, suggest a backup, require WHERE clauses, and 'verify the managed API can read the repaired value' for systemconfig repairs. This satisfies the database-operations feedback-loop expectation enough to avoid the cap-at-3, but a general post-write re-verification step (re-query to confirm the change) is missing, so it sits at the 4 anchor's 'most checkpoints present; minor validation gaps' rather than 5.

4 / 5

Progressive Disclosure

Section headers are clear and the single bundle reference (scripts/mp-db.py) is real, correctly pathed, and one level deep, but the Core Tables catalog is roughly 200 lines of schema-reference material inlined in SKILL.md — exactly the anchor-3 pattern of '[200 lines of API reference that could be in a separate file]'. It is better organized than anchor 3's example and has no nesting problems, but the bulk reference content that should live in references/ keeps it below anchor 4's 'most content is appropriately placed'.

3 / 5

Total

15

/

20

Passed

Description

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

A strong description that clearly states what the skill does, when to use it, and includes realistic quoted trigger phrases, all scoped to a distinct MoviePilot-database niche. The only flaw is the second-person opening ('Use this skill when you need to...'), which costs it a specificity point under the rubric's voice rule.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'inspect, query, maintain, or carefully modify the MoviePilot database' plus 'data statistics, counts, aggregations, inspecting or fixing records, cleanup requests' — which is comprehensive coverage matching the 5 anchor. However, it opens in second person ('Use this skill when you need to...'), which the rubric guidelines penalize by reducing specificity by 1. It is above the 4 anchor's 'minor gaps in coverage' on content, but the voice penalty brings it to 4.

4 / 5

Completeness

It explicitly answers both questions: what ('inspect, query, maintain, or carefully modify the MoviePilot database' via 'the bundled scripts/mp-db.py helper') and when ('Use this skill when you need to...' plus 'Applicable scenarios include...' with concrete trigger phrases). This matches the 5 anchor's 'clearly and explicitly answers both what AND when with concrete trigger phrases' and exceeds the 4 anchor where 'when' is less specific.

5 / 5

Trigger Term Quality

It quotes natural user phrasings users would actually say: 'how many downloads', 'show site stats', 'delete old records', and 'why is this subscription stuck', alongside scenario terms like 'data statistics', 'aggregations', and 'cleanup requests'. This is comprehensive natural-term coverage (file extensions are inapplicable to a database skill), matching the 5 anchor and clearly above the 4 anchor's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

The description is tightly scoped to 'the MoviePilot database' with a unique mechanism (the bundled mp-db.py helper and its no-passwords-in-prompt behavior), giving it a clear niche with distinct triggers and minimal conflict risk, matching the 5 anchor rather than the 4 anchor's 'minor overlap risk with closely related skills'.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

jxxghp/MoviePilot

Path

skills/database-operation/SKILL.md

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.