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.

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

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 content is concise and well-structured for a simple skill, but as an output-producing agent it lacks concrete templates/examples and any sequenced workflow with verification, which limits actionability and workflow clarity.

Suggestions

Add a short output template or worked example (e.g. a sample briefing structure with headings, date, attribution, and a 3-5 bullet executive summary) to make the guidance copy-paste ready.

Provide an explicit workflow sequence: read upstream agent outputs → synthesize findings → draft sections → format with headings/date/attribution → verify quantitative data is preserved.

Include a verification step in the workflow (e.g. confirm all source quantitative figures and attributions are present before finalizing) to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is lean and free of padding or explanations of concepts Claude already knows; only the opening paragraph lightly restates the frontmatter, which keeps it just short of a 5.	4 / 5
Actionability	Guardrails like "Include date and attribution" and "Keep executive summaries concise (3-5 bullet points)" are concrete, but there are no output templates, formatting specs, or worked examples showing how to shape the actual document.	3 / 5
Workflow Clarity	There is no sequenced process — only a skills list and guardrails — so for a document-producing skill the workflow (gather inputs → synthesize → structure → format → verify) is largely absent with poorly defined steps.	2 / 5
Progressive Disclosure	This is a simple under-50-line skill with no bundle files and clean "## Skills" / "## Guardrails" section organization, which per the simple-skill exception earns a top progressive_disclosure score.	5 / 5
	Total	14 / 20 Passed

Description

53%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 conveys the skill's purpose and domain with concrete actions, but its trigger guidance is a sequencing condition rather than explicit user-trigger phrasing, capping completeness. Trigger-term coverage omits common natural variations users would actually say.

Suggestions

Add an explicit 'Use when...' clause tied to user intents, e.g. "Use when the user asks for an executive briefing, board memo, or summary report from research/strategy/financial findings."

Expand trigger terms to include natural phrases and synonyms users say ("executive summary", "write a report", "board memo", "investment memo").

List a few more concrete actions (e.g. "drafts executive summaries", "structures findings into sections", "attributes sources") to broaden action coverage toward a 4-5 specificity score.

Dimension	Reasoning	Score
Specificity	"synthesizes research, strategy, and financial findings into executive briefings and reports" names the domain plus a couple of concrete actions, but the action list is not comprehensive enough for a 4.	3 / 5
Completeness	The "what" is clear, but the "Use after upstream specialist agents have produced their data" clause is a workflow sequencing condition rather than an explicit user trigger, so the 'when' is only weakly implied and completeness is capped at 3.	3 / 5
Trigger Term Quality	Terms like "business writer", "executive briefings and reports", and "research, strategy, and financial findings" are relevant but miss common natural phrasings (e.g. "executive summary", "write a report", "board memo") and file-type triggers.	3 / 5
Distinctiveness Conflict Risk	The executive-business writing niche is mostly distinct with only minor overlap risk against a generic writer skill, but triggers are not fully spelled out so it does not reach 5.	4 / 5
	Total	13 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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
Path: modules/skills/src/main/resources/META-INF/skills/writer-agent/SKILL.md
Commit: b600b8a

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.