Norman-bury/research-writing-skill is an agent skill that turns academic paper writing into a tracked, reusable workflow with planning, drafting, reviews, figures, literature work, and LaTeX outputs. It is intended for undergraduate students, graduate students, and early-career researchers working on theses, coursework papers, or initial submissions. Its catalogue entries are the skills, instructions, plugin, and hook that implement the workflow across coding-agent platforms.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Norman-bury/research-writing-skill --skill paper-orchestrationgit clone --depth 1 https://github.com/Norman-bury/research-writing-skillWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/norman-bury/research-writing-skill/paper-orchestration)<a href="https://agentmods.dev/skills/norman-bury/research-writing-skill/paper-orchestration"><img src="https://agentmods.dev/badge/skills/norman-bury/research-writing-skill/paper-orchestration/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/norman-bury/research-writing-skill/paper-orchestration"><img src="https://agentmods.dev/badge/skills/norman-bury/research-writing-skill/paper-orchestration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium System Prompt Leakage · line 129 Skill contains patterns that could indirectly extract system prompts through rephrasing, translation, summarization, or side-channel techniques.Fix: Guard against indirect extraction by refusing to summarize, translate, or rephrase system instructions. Add explicit anti-extraction clauses.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00027 | $0.01281 |
| Opus 5 | $0.00014 | $0.00641 |
| Sonnet 5 | $0.00005 | $0.00256 |
| Haiku 4.5 | $0.00003 | $0.00128 |
Grade A, and why
paper-orchestration scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paper Orchestration
This skill controls the workflow around the writing skills. It prevents "one prompt writes the paper" behavior by forcing stage detection, task packets, review gates, and a capability-use audit.
Hard Gate
For any medium task or full-paper task, do not write manuscript text until these exist or are created:
plan/project-overview.mdplan/outline.mdplan/progress.md- a task packet for the current section or deliverable
- for full-paper drafting or redrafting,
plan/chapter-architecture.md
Medium task means any request that affects more than one paragraph, one subsection, one chapter, one figure/table set, or any claim tied to references or experiments.
Full-Paper Redraft Gate
For a full-paper draft, the controller must first lock the chapter architecture. Do not inherit an old chapter split if the user, target venue, or paper type implies a different structure.
For computer science / engineering SCI papers, use this body structure unless the user or target template explicitly requires otherwise:
- Introduction, with related work integrated into the motivation and research-gap argument.
- Methodology.
- Dataset and Experimental Setting, either standalone or integrated into Methodology/Results when short.
- Experimental Results and Analysis.
- Discussion.
Abstract, Conclusion, and References may be generated as supporting files, but they must not hide weak body chapters or inflate the chapter count. A standalone Related Work chapter is only allowed when the target outline explicitly demands it.
Create plan/chapter-architecture.md before drafting. It must list the exact required chapter files, target role, minimum body length, owner agent, and whether the chapter may use planning placeholders.
## Required chapter files
- chapters/01_Introduction.md | min_chars=4500 | agent=required | placeholders=no
- chapters/02_Methodology.md | min_chars=4500 | agent=required | placeholders=no
If this file exists, the quality gate must treat extra or missing chapter files as failures.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 136 lines · 27 tokens per session scan A 363361770e33
paper-orchestration is a skill published in the GitHub repository Norman-bury/research-writing-skill (3,195 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 1,281 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…