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.

53

Quality

60%

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

58%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 compact, well-organized role definition with useful guardrails and no wasted tokens. Its main gaps are the absence of any workflow sequence and the lack of concrete output specifications (template or example) that would make the produced briefings reliably well-formed.

Suggestions

Add a brief report skeleton or example structure (e.g., heading order: Executive Summary, Key Findings, Strategy, Financials, Recommendation) so the output format is fully specified.

Include a short ordered workflow (read upstream outputs → preserve quantitative data → draft sections → check guardrails before finalizing) so the multi-step process is sequenced.

Specify what inputs to expect and how to handle missing or conflicting upstream data, turning the vague 'preserve key quantitative data' guardrail into actionable guidance.

DimensionReasoningScore

Conciseness

The body is short and lean with no padding or explanation of concepts Claude already knows — every line is a role statement, capability, or guardrail. There is minor redundancy (the intro sentence "You synthesize research, strategy, and financial data into polished executive briefings and reports" repeats the "Skills" bullet "Synthesize multi-source findings into executive briefings"), which keeps it just below the lean-and-efficient level-5 anchor.

4 / 5

Actionability

Some concrete guidance exists — "Format reports with proper headings, dates, and attribution" and "Keep executive summaries concise (3-5 bullet points)" — but there is no report template, section skeleton, or worked example showing the expected output structure. It matches 'some concrete guidance but incomplete; missing key details' rather than the mostly-executable level-4 anchor, which for an instruction-only skill would mean specific, ready-to-follow output specifications.

3 / 5

Workflow Clarity

No sequence is given for turning upstream agent output into a finished briefing — there is no step ordering (gather inputs, extract key data, draft sections, verify guardrails) and no checkpoints such as confirming all source findings were preserved. The "Skills" bullets are capabilities, not a process, so it sits at 'rough sense of what to do but many gaps' rather than the level-3 anchor, which requires a listed sequence of steps.

2 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into clean, clearly headed sections ("Skills", "Guardrails") with nothing that belongs in a separate file. Per the rubric's simple-skill guidance, a short, well-organized skill with no external reference needs scores at the top anchor.

5 / 5

Total

14

/

20

Passed

Description

62%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 states what the skill does and includes an explicit usage condition, giving it solid completeness and reasonable distinctiveness. Its weaknesses are limited action coverage, trigger language framed for an agent pipeline rather than natural user phrases, and missing synonyms and common variations.

Suggestions

Expand the 'what' with two or three more concrete actions (e.g., drafting executive summaries, structuring findings into sections, producing investment-decision briefs) to move specificity beyond one to two actions.

Add natural user trigger phrases and synonyms to the 'when' clause — e.g., "Use when the user asks for an executive briefing, a business report, or a write-up of research, strategy, or financial findings".

Sharpen distinctiveness by naming the distinguishing context (multi-source synthesis from upstream agents into a single polished document) to reduce overlap with generic writing or summarization skills.

DimensionReasoningScore

Specificity

Names the domain (business/executive writing) and one to two concrete actions — "synthesizes research, strategy, and financial findings into executive briefings and reports" — but offers no further actions or detail beyond synthesizing and writing. It matches the anchor for a domain with 1-2 concrete actions that is not comprehensive, not the level-4 anchor that lists several specific actions.

3 / 5

Completeness

The 'what' is clear ("synthesizes research, strategy, and financial findings into executive briefings and reports") and an explicit 'when' clause is present ("Use after upstream specialist agents have produced their data"), so it avoids the cap at 3 for missing trigger guidance. However, the 'when' is a pipeline condition rather than a concrete user trigger phrase, so it does not reach the level-5 anchor of answering both with concrete trigger phrasing.

4 / 5

Trigger Term Quality

Relevant keywords exist ("executive briefings", "reports", "research", "strategy", "financial findings") but common user phrasings and synonyms (e.g., "write up", "summarize findings", "executive summary", "business memo") are missing. The trigger is framed as a pipeline condition ("Use after upstream specialist agents have produced their data") rather than natural user language, so it sits at 'some relevant keywords, missing variations' rather than good coverage.

3 / 5

Distinctiveness Conflict Risk

The niche is fairly clear — executive-facing synthesis of research/strategy/financials, with a pipeline position after specialist agents — making it mostly distinct from generic writing skills. There is minor overlap risk with general report-writing or summarization skills ("reports" is a broad term), which keeps it below the level-5 clear-niche anchor.

4 / 5

Total

14

/

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_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.