CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ai-subtitle-remover

550W Watermark & Text Eraser: remove image text/watermarks, local video subtitles/visual watermarks, and platform watermarks from TikTok or X share links. OAuth MCP or API Key access depends on the host.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/550w-ai-mcp-subtitle-watermark-removal/SKILL.md
SKILL.md
Quality
Evals
Security

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 disciplined, policy-dense overview that routes correctly to real workflow references with strong safety checkpoints around billing, consent, and failure handling. Weaknesses are mild: some duplicated rules, and two bundled reference files left unlinked from the main body.

Suggestions

State the resolved-URL download-failure rule once (in the capabilities block) and drop its duplicate in 'Files and results'.

Add one-line pointers to references/agent-compatibility.md and references/api-contract.md with their read conditions, so all bundle files are navigable from SKILL.md.

Break the longest compound sentences (e.g. the route-selection and cancellation rules) into shorter imperative sentences to reduce re-reading cost.

DimensionReasoningScore

Conciseness

The body contains no explanations of concepts Claude already knows and nearly every sentence carries an operational rule (URLs, env var names, param names), so it is well above the verbose anchors. It misses anchor 5 because of repetition and dense multi-clause sentences: the resolved-URL download-failure rule appears in both the capabilities block ("If the agent cannot download the resolved video URL... give the user the resolved data.video URL") and again in Files and results ("If resolved video downloading fails, return the resolved data.video URL"), and 'a share link is not a substitute for a local video' is likewise stated twice.

4 / 5

Actionability

Concrete, executable elements are present: the MCP endpoint "https://www.550wai.cn/mcp/global", a full stdin JSON example for the CLI fallback ("node {baseDir}/dist/550w-skill.cjs" with {"action":"queryCredits",...}), exact env vars, and the confirmProcessing=true parameter semantics. It is below anchor 5 because the primary upload/submit/poll request shapes are not shown inline — they are delegated to the workflow references — so the body alone leaves minor gaps for the most common operations.

4 / 5

Workflow Clarity

Route selection is a clear numbered sequence with explicit checkpoints for the risky (billed/destructive) operations: consent plus confirmProcessing=true before paid submission, "check the original task before doing anything else; never resubmit" on timeout, and 'Task deletion requires separate user approval', so the destructive-operation cap at 3 does not apply. It stops short of anchor 5 because the end-to-end media processing sequence (inspect → prepare → upload → submit → poll) is not laid out in the body — it lives one level deep in the references — and checkpoints are scattered across prose sections rather than one coherent checklist.

4 / 5

Progressive Disclosure

The body is a genuine overview that cleanly routes to one-level-deep, existing references ([OAuth workflow](references/oauth-access.md) and [API Key workflow](references/openapi-access.md), both present in the bundle) and mentions scripts/550w-upload.cjs; the detailed numbered workflows are appropriately split out rather than inlined. It misses anchor 5 because two bundle references, references/agent-compatibility.md and references/api-contract.md, are never linked or named from SKILL.md — they are discoverable only by listing the directory — leaving a minor navigation gap.

4 / 5

Total

16

/

20

Passed

Description

75%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 communicates concrete, well-scoped capabilities with natural trigger terms and a distinct niche, but it never tells Claude when to use the skill. Adding an explicit 'Use when...' clause and file extensions/synonyms (MP4, erase) would round it out.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user wants to remove a watermark, erase text from an image, or strip subtitles or platform watermarks from an MP4/MOV video or a TikTok/X share link.'

Add file extensions and synonyms users actually say: MP4, MOV, 'erase', 'clean up', 'subtitle remover'.

Drop the trailing 'OAuth MCP or API Key access depends on the host' sentence — it is host configuration detail that spends description budget without aiding triggering.

DimensionReasoningScore

Specificity

"remove image text/watermarks, local video subtitles/visual watermarks, and platform watermarks from TikTok or X share links" lists multiple specific concrete actions covering all capability areas of the skill (image, local video, share-link), matching the comprehensive-coverage anchor. It is not a level below because anchor 4 requires only 'several specific actions' with minor gaps, while here coverage spans every documented capability with named input types.

5 / 5

Completeness

The 'what' is clear (removes image text/watermarks, video subtitles/visual watermarks, platform watermarks), but there is no 'Use when...' clause or equivalent explicit trigger guidance; the judging guidelines explicitly cap completeness at 3 in that case. The trailing "OAuth MCP or API Key access depends on the host" is configuration detail, not a 'when' statement, so it does not reach anchor 4.

3 / 5

Trigger Term Quality

Natural user terms are present: "watermark", "subtitles", "remove", "image", "TikTok or X share links" — phrases a user would plausibly say. It falls short of anchor 5 because common synonyms and file extensions are missing: no "MP4/MOV", no "erase/clean up" (only the product name says "Eraser"), and no generic "video watermark" phrasing beyond the platform-specific mentions.

4 / 5

Distinctiveness Conflict Risk

The niche is clear and distinct — watermark/subtitle removal tied to named platforms ("TikTok or X share links") and a specific product — so triggers would not fire for unrelated document or code skills. It fits the 'clear niche with distinct triggers; minimal conflict risk' anchor rather than anchor 4, which contemplates residual overlap with closely related skills, which is not the case here.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

sunshinehu/550w-ai-subtitle-remover

Path

skills/550w-ai-mcp-subtitle-watermark-removal/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.