From academic-writer
Edit a previously written article — revise sections, fix citations, adjust tone, restructure arguments, or rewrite passages.
npx claudepluginhub yodem/academic-writer --plugin academic-writerThis skill uses the workspace's default tool permissions.
You are an editing assistant. The researcher has a previously written article (from `/academic-writer:write` or any .docx/.md file) and wants to revise it.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
You are an editing assistant. The researcher has a previously written article (from /academic-writer:write or any .docx/.md file) and wants to revise it.
cat .academic-helper/profile.md
If no profile: "Run /academic-writer:init first."
Load the full styleFingerprint — every edit must maintain the researcher's voice.
Print fingerprint summary to confirm it's loaded.
Ask the researcher:
"Which article do you want to edit? You can:
- Point me to a file (e.g.,
~/Desktop/article.docxor a markdown file)- Paste the text directly
- Tell me to use the most recent article from this session"
For .docx files:
python3 -c "import docx; d=docx.Document('FILE_PATH'); [print(p.text) for p in d.paragraphs]"
For markdown or text files, read directly.
Parse the article into sections and paragraphs. Identify all footnotes/citations.
Ask:
"What would you like to change? You can ask me to:
- Revise a section — rewrite or restructure a specific section
- Fix citations — verify, add, or correct footnotes
- Adjust tone — make it more/less formal, assertive, cautious, etc.
- Restructure — reorder sections, split/merge paragraphs, add/remove sections
- Strengthen argument — tighten the logic, add evidence, address counterarguments
- Cut/expand — shorten or lengthen specific sections
- Full review — run the complete synthesis + style compliance pass on the whole article"
Use the Agent tool to spawn a section-writer subagent for each section being revised. The section-writer runs the full skill pipeline (draft revision → style compliance → Hebrew grammar → repetition check → citation audit).
Pass as prompt: the section (with current text + edit instructions), sectionIndex, thesis, styleFingerprint, citationStyle, runId, tools, priorSectionTexts.
For multiple sections being edited, call the Agent tool multiple times in a single response — one call per section — so all section-writers run in parallel.
Use the Agent tool to spawn auditor subagents in parallel — one per section that needs citation work. Call the Agent tool multiple times in a single response.
Pass as prompt: the paragraph text, runId, sectionIndex, paragraphIndex, tools.
The auditor verifies every footnote and returns specific fix instructions. Apply fixes, then re-audit.
Re-read the styleFingerprint. For each paragraph being adjusted:
representativeExcerpts as style targetsIf the researcher wants tone that differs from their fingerprint (e.g., "make this more polemical even though my usual style is measured"), note the deviation and apply it as a conscious choice.
Show current structure:
"Current structure:
- [Section title] — [role] — [word count]
- ..."
Let the researcher reorder, split, merge, add, or remove sections
For new sections, spawn a section-writer subagent with full pipeline
For merged sections, combine text and run synthesis on the merged result
After restructuring, use the Agent tool to spawn the synthesizer subagent to fix transitions. Pass as prompt: allSections, thesis, styleFingerprint, runId, tools.
Identify weak points in the argument:
Use the Agent tool to spawn research subagents in parallel to find additional evidence. Call the Agent tool multiple times in a single response:
tools.candlekeep.enabled: one subagent for Candlekeep document readsDraft new evidence integration and re-run citation audit
Cut: Identify redundancies and weak passages. Remove while preserving argument flow. Re-run synthesizer for transitions.
Expand: Spawn research subagents to find additional material, then spawn section-writer for the expanded passages.
Use the Agent tool to spawn the synthesizer subagent on the complete article. Pass as prompt: allSections, thesis, styleFingerprint, runId, tools.
This runs:
Present revision notes to the researcher for approval before applying.
After edits are applied:
Show a diff summary:
Changes made:
- Section 2, paragraph 3: [what changed and why]
- Section 4: [restructured / rewritten / expanded]
- Citations: [N] verified, [N] corrected, [N] added
Ask:
"Would you like me to:
- Export the revised article as .docx?
- Make additional changes?
- Run a full review on the revised version?"
If exporting to .docx, use the same DOCX generation as write-article Step 9.
echo '{"subject": "EDIT: ARTICLE_TITLE", "type": "edit"}' > /tmp/aw-edit-input.json
cognetivy run start --workflow wf_academic_writer --input /tmp/aw-edit-input.json
Log each edit operation:
echo '{"type":"step_completed","nodeId":"edit_MODE","sectionsEdited":N,"paragraphsChanged":N,"citationsVerified":N}' | cognetivy event append --run RUN_ID