Help Center Writer

What it does

Help Center Writer is a Cursor agent playbook named help-writer. AgenticKit installs it so a session can adopt this role instead of acting as a generic coding assistant.

The help-writer agent turns a ticket or a 'how do I' into a help-center article: who it's for, numbered steps, expected result, troubleshooting. It does not write Swagger or SDK guides.

User how-to from a ticket. Not OpenAPI. Writes step-by-step help articles users can follow. technical-writer owns API and developer docs.

Why it exists

A pile of agent files is not a team. help-writer exists so one job, help center writer, has a written brief, required skills, and a stop condition.

It ships in the Marketing Kit. Skills it must read: User Help Center Articles; Brand Voice Guidelines & Jargon Elimination; Marketing Deliverable Auto-Save & Repo Sync. Commands that adopt this role: /help-article: User Help Center Article; /ticket: Customer Ticket to Fix and Reply; /write-docs: Technical Documentation & API Reference Writer.

When to use it

• Same question in support three times
• A feature shipped with no user docs
• Help center that currently is a blog

When not to use it

• Do not ask help-writer to do a different role's job. If you need a migration, switch agents.
• Do not keep the same chat after this agent has finished its artifact. Start a reviewer in a new thread.
• Do not invoke every agent in the kit for a small change.

Example workflow

1. Install the Marketing Kit so .cursor/agents/help-writer is on disk.
2. Run /help-article: User Help Center Article, or start a chat and tell Cursor to adopt the help-writer role.
3. The agent should read: User Help Center Articles; Brand Voice Guidelines & Jargon Elimination; Marketing Deliverable Auto-Save & Repo Sync.
4. It produces the artifact for this role only, then stops.
5. A different agent or you review. Same-chat self-review is not a review.

Example usage

Example: "You are help-writer. Same question in support three times. Read help-center before you edit."

Or let the pipeline invoke it: /help-article: User Help Center Article.

Capabilities you should actually see: Task-based help articles from real tickets

Example output

• help-writer should leave files or a written verdict, not a vibe check. Task-based help articles from real tickets Troubleshooting branches
• Marketing agents write markdown under docs/marketing/ so later commands can reuse positioning and voice.

Best practices

• Task-based help articles from real tickets
• Troubleshooting branches
• Plain-language steps that match the live UI
• Related-article links
• One role per chat unless a command is explicitly orchestrating a sequence.

Common mistakes

• Using help-writer as a synonym for 'the Cursor agent'. It is a brief, not the product.
• Skipping the required skills and hoping the role name is enough.
• Publishing the first draft of launch copy without a human edit.
• Invoking this agent and three unrelated ones in the same prompt.