Content Brief

skill

Assemble an SEO content brief (outline, entities, target terms) as a writer-ready file.

Download .md

Content Brief

Assemble an SEO (search engine optimization) content brief — outline, target entities, and priority terms — into a writer-ready file for a given topic.

When to use

  • A topic or target keyword needs to be turned into a structured brief before a writer starts drafting.
  • Content ops requests a refreshed brief for an existing underperforming page.
  • A campaign or editorial calendar hands off a new topic that needs research framing before writing begins.

Tools

  • read-file — load prior briefs, topic notes, or keyword lists already saved to the workspace.
  • write-file — save the assembled content brief as the writer-ready artifact.
  • complete-task — finish the task with a structured result summarizing the brief once it is written.

Playbook

  1. Read the task description to identify the target topic, primary keyword, and any audience or intent notes.
  2. If a prior brief, keyword list, or research note exists for this topic, load it with read-file to avoid duplicating work.
  3. Draft a working title and a one-sentence statement of search intent (informational, comparison, transactional) for the topic.
  4. Build a proposed outline: H1, then H2/H3 sections in a logical reading order that covers the topic comprehensively.
  5. List target entities (named concepts, products, people, or terms) the page should mention to signal topical relevance.
  6. List priority terms and secondary terms to work naturally into the copy, grouped by section where relevant.
  7. Add a short competitive/differentiation note if prior research or notes (read via read-file) suggest gaps competitors leave open.
  8. Assemble the outline, entities, terms, and notes into a single markdown brief and save it with write-file under a clear, topic-based filename.
  9. Call complete-task with a structured result pointing to the saved brief file and a one-line summary of the topic and intent covered.

Failure modes

  • 401/403 on any related call: this indicates a missing Integration — stop and message a human via send-message rather than retrying.
  • Empty or missing prior research when read-file is expected to find something: proceed with a brief built from the task description alone, and note in the output that no prior research was found.
  • Rate limit encountered on any dependent call: back off and note the delay in memory before retrying.
  • Source page structure changed or is unreadable: fall back to browser-search for fresh reference material before finalizing the outline.

Done when

  • A single markdown content brief file exists, saved via write-file, containing outline, entities, and target terms.
  • The brief's outline fully covers the requested topic and states the target search intent.
  • complete-task has been called with a result referencing the saved brief file path.