CtrlK
BlogDocsLog inGet started
Tessl Logo

sharaf/professional-article-writer

Use when a professional article task needs evidence-bound editorial control: source packet, claim ledger, verification queue, publication notes, anti-slop revision, article audit, or series plan. Trigger on write, rewrite, revise, humanize, outline, audit, or plan for an article, essay, blog post, longform, thought leadership, or source-backed copy. Do not use for generic copy, short posts, email, docs, or fiction. Topic-only => Editorial Brief plus source plan only, no article body. Source packet => article plus Publication Notes. Draft rewrite/revision => first output # Revised Article, then rewritten article body, then Change Notes.

100

1.56x
Quality

100%

Does it follow best practices?

Impact

100%

1.56x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Evaluation results

100%

10%

AI-Slop Revision Request

Revise AI-slop draft while preserving evidence boundaries

Criteria
Without context
With context

Revise mode used

100%

100%

Concrete lede

100%

100%

Supported meaning preserved

100%

100%

No invented facts or outcomes

85%

100%

Failure mechanism explained

100%

100%

Repair mechanism explained

100%

100%

Generic language removed

100%

100%

Professional structure

100%

100%

Evidence boundary note

100%

100%

Change notes included

0%

100%

100%

11%

Source-Backed Draft Request

Source-backed article draft with claim support and publication notes

Criteria
Without context
With context

Diagnostic angle chosen

100%

100%

Reader promise visible

87%

100%

Source packet used throughout

92%

100%

No invented facts

85%

100%

Evidence attribution

80%

100%

Mechanism over slogans

91%

100%

Actionable RevOps guidance

90%

100%

Professional article structure

90%

100%

Publication notes included

75%

100%

Anti-slop style

100%

100%

100%

87%

Topic-Only Article Request

Topic-only article request should become a brief and source plan

Criteria
Without context
With context

Brief mode selected

0%

100%

Reader and promise defined

20%

100%

Angle options are distinct

0%

100%

Evidence standard stated

8%

100%

Source packet needed

10%

100%

No fabricated support

14%

100%

Structure and voice specified

20%

100%

Acceptance criteria included

0%

100%

Focused collaboration

66%

100%

High-stakes risk handled

16%

100%

Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

Table of Contents