CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

write-in-informational-style

Rewrite text in a dense, factual informational style with no fluff or marketing. Use when the user asks to write or rewrite docs or notes concisely or to apply a neutral informational tone.

56

Quality

71%

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 ./plugins/flowai-engineering/skills/write-in-informational-style/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 delivers genuinely concrete rewriting guidance with strong few-shot examples, but it is padded with four overlapping restatements of the same rules and its output-format instruction is broken and misrendered in its own example. The mismatch with the description (the body instructs summarization rather than style rewriting) further muddies what the skill actually produces.

Suggestions

Collapse the chain-of-thought, task-execution, what-not-to-do, and final-instruction sections into one non-redundant rule list; roughly half the body repeats the same guidance.

Fix the primary example's broken nested code fences and replace the ambiguous four-backticks instruction with a plain, correctly rendered markdown output spec.

Reconcile the body with the description: the body commands summarization ("SUMMARIZE IT FOR MAXIMUM CLARITY") while the description promises style rewriting, so state one unambiguous deliverable.

DimensionReasoningScore

Conciseness

The same rules (short words, active voice, no subjective claims, no jargon) are restated four times across "chain of thought", "task execution instructions", "what not to do", and "final instruction", and the chain-of-thought framing is unnecessary padding. This matches anchor 2 ("Noticeably verbose; several unnecessary explanations or padded sections") rather than 3, where verbosity would be incidental.

2 / 5

Actionability

Guidance is concrete: specific word substitutions ("Utilize"→"Use"), a concrete preference ("delivery in 24 hours" over "fast delivery"), and three clean few-shot original→summary pairs. It falls short of anchor 5 because the primary example's output is malformed (empty/broken code fences around "Water supply off May 1-13.") and the four-backticks format instruction is ambiguous.

4 / 5

Workflow Clarity

A clear 7-step sequence exists (understand → consolidate → simplify → build → final answer) with an explicit "RE-READ and REVISE" checkpoint, but the output-format specification is broken and demonstrated incorrectly in the skill's own example, leaving the final deliverable ambiguous. This places it at anchor 3 rather than 4, where checkpoints and the sequence would be solidly defined.

3 / 5

Progressive Disclosure

The single file has clear section headers with examples grouped together and needs no external references, matching anchor 4 ("Good structure; most content is appropriately placed... minor organization gaps"). It is not 5 because the redundant overlapping sections and the malformed first example slightly impede navigation.

4 / 5

Total

13

/

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 clearly and explicitly states both what the skill does and when to use it, with reasonably natural trigger phrasing. It is held back by limited action coverage and trigger terms broad enough to collide with summarization or editing skills.

Suggestions

Expand the 'what' with the skill's other concrete actions (e.g., 'summarize and simplify text') so capability coverage is comprehensive rather than a single rewrite action.

Add missing natural trigger synonyms such as 'summarize', 'simplify', or 'plain language' that users would say when they need this skill.

Narrow the 'when' clause to the distinctive style transformation (e.g., 'strip fluff, marketing, and formality') to reduce overlap with generic editing/summarization skills.

DimensionReasoningScore

Specificity

"Rewrite text in a dense, factual informational style" names the domain and one concrete action with modifiers ("no fluff or marketing"), but does not list several distinct actions. This matches anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive") rather than 4, which requires several specific actions.

3 / 5

Completeness

It explicitly answers both what ("Rewrite text in a dense, factual informational style with no fluff or marketing") and when ("Use when the user asks to write or rewrite docs or notes concisely or to apply a neutral informational tone") with concrete trigger phrases. This matches anchor 5 exactly.

5 / 5

Trigger Term Quality

"write or rewrite docs or notes concisely" and "neutral informational tone" are natural phrases users would say. It sits at anchor 4 ("Good keyword coverage; a few natural terms missing") rather than 5 because common variations like "summarize", "simplify", or "plain language" are absent.

4 / 5

Distinctiveness Conflict Risk

The style niche ("dense, factual informational style") is somewhat specific, but the trigger "write or rewrite docs or notes concisely" broadly overlaps with summarization, editing, and general writing skills. It fits anchor 3 ("could still overlap with similar skills") better than 4, whose overlap risk is only minor.

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

korchasa/flowai-plugins

Path

plugins/flowai-engineering/skills/write-in-informational-style/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.