write-editorial

Writes competitive programming editorials with progressive hints and brute-force to optimal solution progression.

1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/vaskoyudha/agent-skills-problem-gen --skill write-editorial-vaskoyudha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-editorial
Source: https://github.com/vaskoyudha/agent-skills-problem-gen/tree/main/.qwen/skills/write-editorial
Command: npx skills add https://github.com/vaskoyudha/agent-skills-problem-gen --skill write-editorial-vaskoyudha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a good competitive programming editorial is hard: most editorials either dump the optimal solution with no motivation or condescend to the reader. This Skill produces pedagogically structured editorials that build the "aha moment" through a brute-force to optimal progression, so learners understand why the technique works, not just what it is. ## Core Features & Use Cases - Progressive Hint Scaffolding: Generates exactly 3 hints calibrated by difficulty rating (direction, approach, key insight) so readers at any level gain value. - Brute-Force to Optimal Bridge: Documents the naive approach, computes why it fails against constraints, identifies the bottleneck, and motivates the optimal solution as a natural evolution. - Complete Editorial Package: Produces step-by-step walkthroughs traced on samples, accessible correctness explanations, verified complexity analysis, alternative approaches, and common mistakes with concrete counterexamples. - Use Case: After a problem passes quality review in a problem-generation pipeline, feed the approved architect spec, problem draft, solution, test suite, and review verdict into this Skill to produce the final editorial.json section. ## Quick Start Write the editorial for the approved problem using the outputs from the architect, writer, solution engineer, test generator, and quality reviewer agents.

Frequently Asked Questions about write-editorial

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

FAQPage Schema
How do I write a competitive programming editorial?▼

Structure the editorial as a brute-force to optimal progression: describe the naive approach, compute why it fails against the constraints, identify the bottleneck, then motivate the optimal solution as the natural fix. Add progressive hints, a sample walkthrough, and common mistakes with counterexamples.

How to write progressive hints for programming problems?▼

Use exactly three hints at increasing levels: Hint 1 gives a direction without naming the technique, Hint 2 names the technique and why it applies, Hint 3 reveals the key insight. Calibrate depth to the problem's difficulty rating so each hint reveals strictly new information.

What inputs does the editorial writer skill need?▼

It requires all five approved upstream agent outputs: architect_spec.json, problem_draft.json, solution.json, test_suite.json, and review_verdict.json with an APPROVED verdict. If inputs are missing, it returns a NEEDS_CONTEXT status instead of guessing.

Why should an editorial include the brute-force solution?▼

The brute force motivates the optimization: without showing why the naive approach fails against the constraints, the optimal solution appears unmotivated. The editorial computes worst-case operations, names the bottleneck, and bridges to the optimal approach.

What are common mistakes to include in a problem editorial?▼

Include 2-3 plausible mistakes such as failing greedy approaches, off-by-one errors, missed edge cases, integer overflow, or wrong binary search bounds. Each mistake needs a concrete counterexample with specific input, the wrong output, and the lesson learned.