edit-article

Route article markdown files through two parallel editor agents and report blocking fixes.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/venturecrane/crane-console --skill edit-article
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edit-article
Source: https://github.com/venturecrane/crane-console/tree/main/.agents/skills/edit-article
Command: npx skills add https://github.com/venturecrane/crane-console --skill edit-article

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates editorial review by routing articles through two parallel editor agents, applying blocking fixes directly, and reporting changes. Advisory issues are reported but not auto-fixed.

Core Features & Use Cases

  • Runs two parallel editor agents to review articles concurrently.
  • Applies blocking fixes directly to the article when possible.
  • Reports changes and highlights advisory issues for human follow-up.

Quick Start

Run /edit-article <path> to process an article and trigger dual-editor review.

Frequently Asked Questions about edit-article

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

FAQPage Schema
How do I automate editorial review for article markdown files?

Automated editorial review routes article markdown files through two parallel editor agents, applying blocking fixes directly and reporting advisory issues for human follow-up to streamline the review process.

What is dual-editor article review and how does it work?

Dual-editor article review orchestrates two parallel editor agents to concurrently evaluate content, parsing frontmatter and running pre-flight checks against terminology and venture registries before generating a structured report.

Can I apply blocking fixes automatically while keeping advisory issues manual?

Yes, the workflow applies blocking fixes directly to the article file when possible, while advisory findings are reported separately without auto-fixing, requiring human follow-up for resolution.

How do I run pre-flight validation checks against terminology registries before publishing?

Pre-flight validation checks terminology and venture registries by parsing article frontmatter and routing content through paired editor agents, outputting exact article titles and paths for targeted review.

Does the editorial agent-orchestration workflow require any external dependencies?

No external dependencies are required; the agent-orchestration workflow operates independently, using frontmatter parsing and built-in registry validation to process articles without additional packages.