Skip to content
Back to skills

Generating Writeup

ASecurity

Generates academic/technical writeups with IEEE citations and pandoc PDF output. Use when creating research papers, technical reports, or documentation with references.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 5, 2026
ai-agentsgobashapidocumentation

Works with

  • claude code
  • cli
  • api

Security analysis

A100/100

Pro scans all 20 files and shows the line behind each finding

Scanned September 25, 2026

npx -y skills add qte77/claude-code-plugins --skill generating-writeup --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Generating Writeup?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Generating Writeup
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/qte77-generating-writeup/badge)](https://www.skillsdirectory.com/skills/qte77-generating-writeup)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: generating-writeup
description: Generates academic/technical writeups with IEEE citations and pandoc PDF output. Use when creating research papers, technical reports, or documentation with references.
compatibility: Designed for Claude Code
metadata:
  allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebSearch, WebFetch
  argument-hint: "[topic] [template] [citation-style]"
  stability: stable
  content-hash: sha256:9e500bc5e5b4c840c55fdb360e80ad198953af3b1be65784df0f00ae22cbf5ad
  last-verified-cc-version: 1.0.34
---

# Writeup Generation

**Target**: $ARGUMENTS

Generates **structured academic/technical writeups** as markdown with citation
support. IEEE `[1]` style by default. PDF export via pandoc is optional.

## Workflow

1. **Parse arguments** - Extract topic, template (default: `project-report-IMRaD`), and citation style
2. **Create directory** - `docs/write-up/<topic>/`
3. **Copy template** - Copy from `templates/` to `docs/write-up/<topic>/`:
   - `project-report-IMRaD` — scientific/academic (Introduction, Methods, Results, Discussion)
   - `technical-doc` — software documentation (Overview, Architecture, API, Config, Deployment)
4. **Fill sections** - Replace TODO comments in each chapter file
5. **Setup bibliography** - Add entries to `09a_bibliography.bib`
6. **Run markdownlint** - `npx markdownlint-cli docs/write-up/<topic>/*.md`
7. **Generate PDF** (optional) - If pandoc is available, run `make pandoc_run`

## Additional Resources

- Templates: [project-report-IMRaD/](templates/project-report-IMRaD/) | [technical-doc/](templates/technical-doc/)
- Setup help: `make -f $CLAUDE_PLUGIN_ROOT/Makefile setup_pdf_converter HELP`
- Pandoc help: `make -f $CLAUDE_PLUGIN_ROOT/Makefile pandoc_run HELP=1`

## Citation Styles

| Style | CSL File | Notes |
| ----- | -------- | ----- |
| IEEE (default) | Bundled (`scripts/writeup/citation-styles/ieee.csl`) | Numeric `[1]` |
| APA | Bundled (`scripts/writeup/citation-styles/apa.csl`) | Author-date `(Smith, 2024)` |
| Chicago | Bundled (`scripts/writeup/citation-styles/chicago-author-date.csl`) | Author-date `(Smith 2024)` |

Additional CSL files are available from the
[Zotero Style Repository](https://www.zotero.org/styles).

## PDF Export (Optional)

If pandoc and LaTeX are installed, generate PDF using the bundled Makefile:

```bash
dir=docs/write-up/<topic> && \
make -f $CLAUDE_PLUGIN_ROOT/Makefile pandoc_run \
  INPUT_FILES="$$(printf '%s\036' $$dir/*.md)" \
  OUTPUT_FILE="$$dir/output.pdf" \
  BIBLIOGRAPHY="$$dir/09a_bibliography.bib"
```

With custom citation style:

```bash
dir=docs/write-up/<topic> && \
make -f $CLAUDE_PLUGIN_ROOT/Makefile pandoc_run \
  INPUT_FILES="$$(printf '%s\036' $$dir/*.md)" \
  OUTPUT_FILE="$$dir/output.pdf" \
  BIBLIOGRAPHY="$$dir/09a_bibliography.bib" \
  CSL="$CLAUDE_PLUGIN_ROOT/scripts/writeup/citation-styles/apa.csl"
```

Full writeup build (content generation + PDF):

```bash
make -f $CLAUDE_PLUGIN_ROOT/Makefile writeup \
  WRITEUP_DIR=docs/write-up/<topic>
```

## Section Numbering (MANDATORY)

**NEVER add manual section numbers to headings.** Pandoc `--number-sections`
handles all numbering automatically.

- **Wrong**: `# 2. Projektvorstellung`, `## 2.1 Motivation`, `### 2.1.1 Details`
- **Correct**: `# Projektvorstellung`, `## Motivation`, `### Details`

Manual numbers in markdown headings conflict with pandoc auto-numbering and
produce duplicated numbers in the PDF output.

## Quality Checks

Before completing:

1. **No manual section numbers** - Headings must not contain `N.`, `N.N`, `N.N.N` prefixes
2. **Markdownlint** - `npx markdownlint-cli docs/write-up/<topic>/*.md`
3. **Citation validation** - Verify all `[@key]` references exist in `.bib` file
4. **PDF generation** (optional) - If pandoc available, run `make pandoc_run`

## Further Reading

- [Pandoc User's Guide](https://pandoc.org/MANUAL.html)
- [Zotero Style Repository](https://www.zotero.org/styles)
- [Citation Style Language Specification](https://citationstyles.org/)
- [BibTeX Entry Types](https://www.bibtex.org/Format/)

Files in this skill

  • SKILL.md4 KB
  • templates/project-report-IMRaD/00_title_abstract_abbrev.tex1.2 KB
  • templates/project-report-IMRaD/01_build_settings.md114 B
  • templates/project-report-IMRaD/02_project_introduction.md97 B
  • templates/project-report-IMRaD/03_desired_state.md99 B
  • templates/project-report-IMRaD/04_planning_and_solution.md93 B
  • templates/project-report-IMRaD/05_implementation.md85 B
  • templates/project-report-IMRaD/06_control_of_success.md81 B
  • templates/project-report-IMRaD/07_results.md63 B
  • templates/project-report-IMRaD/08_summary_outlook.md80 B
  • templates/project-report-IMRaD/09a_bibliography.bib209 B
  • templates/project-report-IMRaD/10_appendices.md67 B
  • templates/project-report-IMRaD/11_index.md49 B
  • templates/technical-doc/01_build_settings.md101 B
  • templates/technical-doc/02_overview.md75 B
  • templates/technical-doc/03_architecture.md89 B
  • templates/technical-doc/04_api.md93 B
  • templates/technical-doc/05_configuration.md89 B
  • templates/technical-doc/06_deployment.md85 B
  • templates/technical-doc/07_troubleshooting.md87 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.