CtrlK
BlogDocsLog inGet started
Tessl Logo

writer-agent

Business writer that synthesizes research, strategy, and financial findings into executive briefings and reports. Use after upstream specialist agents have produced their data.

56

Quality

66%

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 ./modules/skills/src/main/resources/META-INF/skills/writer-agent/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-organized for a simple skill, but its guidance remains abstract rather than executable and lacks validation checkpoints for the synthesis/output process.

Suggestions

Add a concrete report template or required section schema (e.g. Executive Summary / Key Findings / Financials / Recommendation) so the output is copy-paste ready.

Add a validation step in the guardrails, e.g. verify attribution and that all quantitative figures trace back to a source agent before delivering.

Specify the input contract (what upstream agent outputs to consume) so the synthesis workflow is unambiguous.

DimensionReasoningScore

Conciseness

The body is lean and free of padding; it assumes Claude's competence and never explains concepts Claude already knows.

3 / 3

Actionability

Guidance is mostly directional ("synthesize multi-source findings", "format reports with proper headings, dates, and attribution") without concrete templates, section schemas, or copy-paste-ready structures, so it is incomplete rather than fully actionable.

2 / 3

Workflow Clarity

No explicit input-to-output sequence is given; guardrails exist but there are no validation checkpoints confirming attribution or preserved quantitative data before delivery, so the workflow is present but lacks checkpoints.

2 / 3

Progressive Disclosure

A short single-purpose skill under 50 lines with no external references needed; it is cleanly organized into Skills and Guardrails sections, satisfying the simple-skill exception.

3 / 3

Total

10

/

12

Passed

Description

60%

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 specific about capabilities but weak on explicit user-facing trigger guidance, relying on pipeline ordering rather than natural "use when" phrasing. It is reasonably distinct but would benefit from clearer trigger terms.

Suggestions

Add an explicit "Use when the user needs an executive briefing, executive summary, or business report synthesized from upstream agent outputs" clause to raise completeness.

Broaden trigger-term coverage with natural phrasings users would actually say (e.g. "write a report", "executive summary", "briefing").

Sharpen distinctiveness by naming the upstream-agent context as the distinguishing trigger so it does not conflict with general writing skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "synthesizes research, strategy, and financial findings into executive briefings and reports" — matching the multi-action anchor.

3 / 3

Completeness

Clearly answers what it does, but the "when" ("Use after upstream specialist agents have produced their data") is pipeline ordering rather than explicit user-facing trigger guidance, which caps completeness at 2.

2 / 3

Trigger Term Quality

Includes relevant terms ("executive briefings and reports", "research", "financial findings") but lacks common natural variations a user would say such as "write a report" or "executive summary".

2 / 3

Distinctiveness Conflict Risk

The executive-briefing synthesis niche is fairly distinct, but the description could still overlap with general writing/reporting skills since it lacks sharply distinguishing trigger terms.

2 / 3

Total

9

/

12

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
Atmosphere/atmosphere
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.