editor-methodology

Standardize editorial reviews through a five-pass pipeline and artifact-pyramid outputs.

86|9|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/magnus919/hermes-profiles --skill editor-methodology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: editor-methodology
Source: https://github.com/magnus919/hermes-profiles/tree/main/skills/editor-methodology
Command: npx skills add https://github.com/magnus919/hermes-profiles --skill editor-methodology

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Editorial methodology provides a formal, repeatable workflow for editor profiles to execute multi-pass reviews, ensuring argument coherence, structural integrity, voice consistency, and a transparent artifact-pyramid pipeline.

Core Features & Use Cases

  • Five-pass pipeline reference and authoring templates to standardize editorial reviews.
  • Artifact-pyramid mapping and navigation for organizing outputs from L1 verdict to L3 dossiers.
  • Delegation context templates to reliably spawn sub-agents with consistent context.
  • Reference templates and style rules to maintain site-agnostic voice and formatting.

Quick Start

Load this skill when you need a structured, repeatable editorial process to guide thorough review across drafts and produce standardized artifact pyramids.

Frequently Asked Questions about editor-methodology

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize editorial review workflows across multiple draft stages?

Standardize editorial review workflows by applying a five-pass pipeline that enforces argument coherence, structural integrity, and voice consistency. This methodology produces traceable decisions and an artifact-pyramid output spanning L1 verdicts to L3 dossiers.

What is an artifact pyramid in editorial pipeline governance?

An artifact pyramid in editorial governance is a structured output hierarchy mapping deliverables from L1 verdicts up to L3 dossiers. It organizes multi-pass review results so editorial teams can navigate and trace decisions across publication stages.

Can I use this editorial pipeline for a small content team or does it require enterprise governance?

This editorial pipeline suits any team requiring repeatable governance for drafts across review stages. It provides structured delegation context templates and site-agnostic voice rules, scaling effectively for both small teams and larger editorial operations.

What's the best way to maintain voice consistency across different editorial reviewers?

Maintain voice consistency across reviewers by applying reference templates and style rules embedded in the five-pass pipeline. These enforce site-agnostic formatting and standardized editorial guidance throughout the multi-pass review workflow.

How do I delegate editorial review tasks to sub-agents with consistent context?

Delegate editorial review tasks using delegation context templates provided by the methodology. These templates reliably spawn sub-agents with consistent context, ensuring structured guidance and traceable decisions across the artifact-pyramid pipeline.

When should I not use a structured multi-pass editorial pipeline?

Avoid a structured multi-pass editorial pipeline when drafts require rapid turnaround without governance or when content needs only light copyediting. The five-pass methodology enforces repeatable review stages and artifact generation, adding overhead unsuitable for simple edits.