CtrlK
BlogDocsLog inGet started
Tessl Logo

feedback-issue

Use this skill ONLY when the user EXPLICITLY requests filing an upstream issue for MoviePilot core, frontend, or an installed plugin, for example "反馈 issue", "提 issue", "报 bug", "给 MP 提 issue", "让上游修一下", "提交错误报告", "提问题", "提需求", "功能请求", or English "file an issue / report a bug / open an upstream issue / feature request". A bare problem report is not enough: diagnose locally first. This skill uses its own scripts under `scripts/`; it does not add or call dedicated Agent tools for collect / prepare / submit.

74

Quality

92%

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 well-structured, highly actionable workflow with clear validation checkpoints and appropriate use of bundle scripts. The only weakness is some over-explanation of environment and implementation internals that an intelligent model does not need.

Suggestions

Trim the interpreter/virtualenv aside in 'Required Scripts' (lines 53-55) to a single sentence; the exact interpreter choice can be inferred at runtime.

Compress the log-relevance rules block (lines 91-104) into a short bullet list; the detailed redaction mechanics belong in the collect script, not the skill body.

Shorten the submit-script implementation detail paragraph (lines 247-253) to what the model must do (relay results, never echo a token) rather than how the script imports settings internally.

DimensionReasoningScore

Conciseness

The body is mostly lean and directive, but passages over-explain environment/interpreter details ('User installations typically run MoviePilot directly in that environment rather than inside a repository-local virtualenv...') and implementation internals, matching the 'mostly efficient but could be tightened' anchor.

2 / 3

Actionability

Provides copy-paste executable script invocations with real flags, two complete draft-JSON templates with all required fields, allowed-value tables, and exact per-reason-code handling, matching the 'fully executable code/commands; copy-paste ready' anchor.

3 / 3

Workflow Clarity

Six clearly sequenced steps with explicit validation checkpoints (gate on no_explicit_feedback_intent, rejection handling, explicit '确认'/'confirm' before submit) and a keyword-mismatch feedback loop, matching the 'clear sequence with explicit validation steps; feedback loops for error recovery' anchor.

3 / 3

Progressive Disclosure

References real, present bundle scripts (collect/prepare/submit_feedback_issue.py plus shared feedback_issue_common.py) via one-level-deep pointers, keeping heavy detail in the scripts while the body stays an overview, matching the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

11

/

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 highly specific, well-gated description with rich bilingual trigger terms and clear what/when guidance. Its main risk is verbosity for a description field, though it remains clear rather than padded.

DimensionReasoningScore

Specificity

Names multiple concrete actions across three target types (core, frontend, plugin) and explicit operational constraints ('diagnose locally first', script-based, no dedicated Agent tools), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers what (filing an upstream issue for MoviePilot core/frontend/plugin) and when (explicit 'Use this skill ONLY when...' trigger with example phrases and a negative gate), matching the 'clearly answers both what AND when with explicit triggers' anchor.

3 / 3

Trigger Term Quality

Enumerates extensive natural user phrasings in both Chinese ('反馈 issue', '提 issue', '报 bug', '功能请求', ...) and English ('file an issue', 'report a bug'), matching the 'good coverage of natural terms' anchor.

3 / 3

Distinctiveness Conflict Risk

A narrow niche gated to explicit upstream-issue requests, with the 'bare problem report is not enough' exclusion preventing conflicts with ordinary diagnosis skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

12

/

12

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.

Validation15 / 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
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.