Bundle catalog

roles bundle

Editor

A free, open-source set of 11 Markdown files that gives an AI assistant practical guidance for the Editor role.

Use this bundle to plan and review Editor work with evidence, assumptions, owners, and review points made explicit. The page previews a role guide, an overview, a workflow, and a template; the intended output is Source-aware editorial review. Start source review with O*NET Editors profile.

Project-reviewed beta

11 Markdown files · 1,086 words · no signup · CC-BY-4.0

Inspect before downloading

See what is inside

These previews come from the published bundle files, so you can judge the method and writing before using it.

Is this bundle right for your task?

Who it is for

  • People performing or supporting Editor work, plus teams reviewing its decisions and outputs
  • Teams working in General

When to use it

  • An Editor task needs a structured plan, evidence checklist, or review-ready output.
  • A recommendation needs its assumptions, owners, risks, dependencies, and success measures made explicit.

What you need to provide

  • The task objective, intended audience, working context, constraints, source material, and decision owner.
  • Relevant reports, exports, examples, policies, prior decisions, and success measures available for the task.

Tasks and expected outputs

Questions it helps answer

  • Turn draft text, source material, style guidance, and publication goals into a reviewable editorial plan.
  • Separate verified source facts, author-provided claims, assumptions, and missing evidence before revising or approving copy.
  • Improve clarity, consistency, structure, and publication readiness without inventing facts or silently changing meaning.

What it helps produce

  • Source-aware editorial review

Practical example

Use it with an agent

Load the bundle as context, provide the evidence named above, then adapt this example to your situation.

Provide the task objective, intended audience, working context, constraints, source material, and decision owner. Ask the agent to approach Editor work by producing Source-aware editorial review with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with O*NET Editors profile, then confirm that the reference is current and applicable. Inspect Editor Role before drafting.

Context path: bundles/roles/editor

What the bundle includes

Frameworks

  • source-evidence matrix
  • meaning-preservation review
  • publication-readiness gate

Evaluations

  • Editorial source-awareness check

Sources used to build this bundle

These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.

Limitations and safe use

Do not use this for

  • Treating the bundle as a substitute for organization-specific authority, firsthand evidence, or accountable review.

Known limitations

  • This bundle supports editorial review and revision planning; it is not legal, medical, financial, scientific, compliance, or publication approval.
  • Fact-sensitive edits require current source material, author intent, citation evidence, rights/licensing review, and accountable publication review.
  • Do not invent facts, citations, quotations, permissions, claims, endorsements, or publication approvals.

Safety notes

  • Minimize personal, customer, confidential, unpublished, and rights-restricted material in prompts and examples.
  • Require explicit confirmation before publishing, submitting, sending, licensing, attributing, or materially changing author meaning.
  • Route legal, compliance, medical, scientific, brand, rights, and reputational issues to accountable reviewers.

Next step

Inspect it before relying on it

Download the bundle for use, review its source files and evidence, or read the agent guidance. If the project is useful, starring the repository helps others discover it.