agent writing skill risk: low
Article Draft Section Editor
Divides an article into sections based on headings while respecting information dependencies modeled as a directed acyclic graph, confirms the sections with the user, and rewrites…
SKILL 1 file
SKILL.md
--- name: edit-article description: "Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft." --- 1. First, divide the article into sections based on its headings. Think about the main points you want to make during those sections. Consider that information is a directed acyclic graph, and that pieces of information can depend on other pieces of information. Make sure that the order of the sections and their contents respects these dependencies. Confirm the sections with the user. 2. For each section: 2a. Rewrite the section to improve clarity, coherence, and flow. Use maximum 240 characters per paragraph.
REQUIRED CONTEXT
- article draft
ROLES & RULES
- Divide the article into sections based on its headings
- Make sure that the order of the sections and their contents respects these dependencies
- Confirm the sections with the user
- Rewrite the section to improve clarity, coherence, and flow
- Use maximum 240 characters per paragraph
EXPECTED OUTPUT
- Format
- plain_text
- Constraints
-
- maximum 240 characters per paragraph
- confirm sections with user before rewriting
SUCCESS CRITERIA
- Improve clarity, coherence, and flow
- Respect information dependencies
CAVEATS
- Missing context
-
- The article text to edit
- What to do after rewriting all sections (e.g., global review, title, conclusion)
- Output format or presentation style for rewritten sections
- Ambiguities
-
- 'Think about the main points you want to make during those sections' does not specify whose points or perspective.
- DAG dependency instruction is abstract and its application to headings/sections is not operationalized.
QUALITY
- OVERALL
- 0.60
- CLARITY
- 0.70
- SPECIFICITY
- 0.55
- REUSABILITY
- 0.75
- COMPLETENESS
- 0.40
IMPROVEMENT SUGGESTIONS
- Add a step 3 that performs a final pass for overall consistency, tone, and length after all sections are rewritten.
- Specify how rewritten sections should be returned to the user (e.g., markdown with change notes).
USAGE
Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.
MORE FOR AGENT
- Technical Wiki Documentation Page Writer agent writing
- Systems Paper Paragraph Blueprint agent writing
- ML Paper Outline Generator agent writing
- Documentation Co-Authoring Workflow Guide agent writing
- ML Paper Outline from Results agent writing
- Academic Paper Outline from Reviews agent writing
- ML/AI Theory Rigorous Proof Writer agent writing
- TDD Skill Authoring Methodology agent writing
- Conversational Markdown Article Shaper agent writing
- Marketing Copy Seven-Sweeps Editor agent writing
- Release Notes from Tickets and Changelogs agent writing
- Technical Wiki Documentation Page Writer agent writing
- LaTeX Paper PDF Compiler agent writing
- AI Writing Patterns Audit and Rewrite agent writing
- Codebase Wiki Catalogue Architect agent writing
- Technical Wiki Page Documentation Writer agent writing
- AI Writing Patterns Auditor and Rewriter agent writing
- Internal Communications Drafter agent writing
- Codebase Wiki Catalogue and Onboarding Guide Generator agent writing
- AI Writing Patterns Audit and Rewrite agent writing
- Overleaf Git Bridge Two-Way Sync agent writing
- Overleaf Git Bridge Sync Workflow agent writing
- Comprehensive Codebase Bug Analysis and Fixer agent analysis
- Xcode MCP Usage Guidelines for Agents agent tool_use
- Xcode MCP Usage Guidelines agent tool_use