CtrlK
BlogDocsLog inGet started
Tessl Logo

inkos-story-deslop

识别并修复空泛、模板化、总结腔和其他AI写作痕迹,同时保留作者声音。Use for semantic prose cleanup, not keyword deletion.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/core/skills/inkos-story-deslop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 content is a tight, well-structured diagnostic guide that respects token budget and uses a single clean reference, with only slightly under-numbered workflow steps and room for more concrete examples.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it lists diagnostic principles and a single reference pointer with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Concrete, specific guidance is given throughout (named defect types to scan for, what to preserve), and as an instruction-only skill the absence of code is not penalized; it stops just short of fully copy-paste-ready examples.

4 / 5

Workflow Clarity

A clear diagnostic sequence is implied (diagnose → distinguish defect vs voice → scan → audit/reviser → preserve → respond) with a scope checkpoint ("audit first when scope is unclear; use the reviser") and a truthfulness guardrail, though steps are not explicitly numbered.

4 / 5

Progressive Disclosure

A concise overview points to one clearly signaled, one-level-deep reference ("Load `references/semantic-cleanup.md`") that exists as a real file, with the split appropriately placed.

5 / 5

Total

18

/

20

Passed

Description

67%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 conveys a clear, distinct niche with concrete actions and an explicit use clause, but its trigger terms are somewhat jargony and lack the natural phrasings a user would actually say.

Suggestions

Add concrete user-facing trigger phrases to the description (e.g. "Use when the user says prose feels generic, mechanical, over-explained, or AI-generated").

Soften the jargony "semantic prose cleanup" with a natural synonym users would say, such as "de-AI prose" or "fix AI-sounding writing".

DimensionReasoningScore

Specificity

Names several concrete actions — "识别并修复" (identify and fix) plus "保留作者声音" (preserve author voice) — across named defect types (空泛、模板化、总结腔、AI写作痕迹), with only minor coverage gaps.

4 / 5

Completeness

It states both what (识别并修复...保留作者声音) and when ("Use for semantic prose cleanup, not keyword deletion"), but the when clause is scope-oriented rather than a concrete trigger phrase, so it stops short of fully explicit trigger guidance.

4 / 5

Trigger Term Quality

"Use for semantic prose cleanup" and "AI写作痕迹" give some relevant keywords, but the natural phrasings a user would say ("prose feels AI-generated", "sounds robotic") live in the body rather than the description, leaving common synonyms missing.

3 / 5

Distinctiveness Conflict Risk

The AI-writing-traces niche is clearly bounded, and the explicit "not keyword deletion" boundary reduces overlap with adjacent editing skills, leaving only minor overlap risk.

4 / 5

Total

15

/

20

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
Narcooo/inkos
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.