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

task.mdevals/scenario-1/

AI-Slop Revision Request

This draft sounds AI-written. Rewrite it into a stronger professional article for product leaders. Keep the supported meaning, but make it more interesting and concrete. Do not invent new facts.

Draft:

In today's rapidly evolving digital landscape, product teams face numerous challenges when adopting customer feedback tools. These tools can be transformative, but only when implemented thoughtfully. It is crucial for organizations to align stakeholders, create a culture of collaboration, and leverage data-driven insights. By breaking down silos and embracing innovation, companies can unlock the full potential of customer feedback and drive meaningful business outcomes.

A successful implementation starts with clear goals. Teams should define success, communicate across departments, and continuously iterate. With the right approach, customer feedback tools can help teams listen better, build better, and succeed in a competitive market.

Known facts:

  • The product team receives 1,400 feedback items per month across sales calls, support tickets, and in-app forms.
  • Before the tool rollout, product managers spent Fridays copying themes into a spreadsheet.
  • The first rollout failed because account managers and support leads used different tags for the same issue.
  • The second rollout worked after the team created a shared taxonomy, assigned one owner for tag hygiene, and reviewed five customer quotes in each roadmap meeting.
  • No revenue or churn impact has been measured yet.

evals

scenario-1

criteria.json

task.md

README.md

tile.json