CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-skill

A skill for writing and content creation

35

Quality

44%

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 ./agentscope-core/src/test/resources/test-skills/writing-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

36%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 brief and uncluttered but provides no actionable guidance — just abstract task categories with no methods, examples, or workflow. The existing reference file is also orphaned, never referenced from the body.

Suggestions

Replace the abstract bullet list with concrete, executable guidance (e.g., specific editing checks, style heuristics, or worked before/after examples).

Link the existing references/guide.md from the body (e.g., 'See [guide.md](references/guide.md) for detailed best practices') so the bundle is discoverable.

Define a clear sequence for common writing tasks (draft -> review -> proofread) with explicit checkpoints.

DimensionReasoningScore

Conciseness

The body is lean with no over-explanation of concepts Claude already knows, though the closing line "Use this skill to enhance your writing capabilities" is mildly redundant fluff that could be trimmed.

4 / 5

Actionability

The body only lists abstract categories ("Content creation", "Editing and proofreading", "Style improvement") with no concrete code, commands, or specific steps, matching the entirely-vague anchor.

1 / 5

Workflow Clarity

There is no sequence of steps and the listed tasks are vague and multiple rather than a single unambiguous action, so the simple-skill exception does not fully apply; it sits between incoherent and rough-sequence.

2 / 5

Progressive Disclosure

The body itself is reasonably organized with a heading and bullet list, but the bundle file references/guide.md is never linked or signaled from the body, leaving a navigation gap that prevents a higher score.

3 / 5

Total

10

/

20

Passed

Description

25%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 is too generic: it names a broad domain without concrete actions, trigger phrases, or a use-when clause, leaving it indistinguishable from many other skills. It would rarely be selected confidently for a specific user need.

Suggestions

List 2-4 concrete actions the skill performs (e.g., 'Drafts, edits, and proofreads text; improves tone and structure').

Add an explicit trigger clause such as 'Use when the user asks for help writing, editing, proofreading, or refining text.'

Narrow the niche and add natural synonyms (drafting, copyediting, rewriting) to reduce overlap with other skills.

DimensionReasoningScore

Specificity

"A skill for writing and content creation" names a domain but lists no concrete actions, matching the anchor where actions are minimal or generic; it stops short of score 1 because a domain is at least named.

2 / 5

Completeness

It offers a vague "what" (writing and content creation) with no "Use when..." trigger guidance at all, which per the rubric caps completeness and matches the vague-what/no-when anchor.

2 / 5

Trigger Term Quality

The only keywords are the generic "writing" and "content creation", missing the natural phrases and synonyms (drafting, editing, proofreading) users would actually say, matching one-or-two generic keywords.

2 / 5

Distinctiveness Conflict Risk

"Writing and content creation" is very broad with high overlap risk against many general skills, matching the very-broad anchor rather than the entirely-generic score 1.

2 / 5

Total

8

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
agentscope-ai/agentscope-java
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.