Generate PDF from a spec. Use when: exporting documentation to PDF, generating a print-friendly spec. Do NOT use for: creating documentation (use aide-create)
2 stars
0 votes
0 copies
0 views
Added November 18, 2026
ai-agentsbashdocumentation
Security analysis
A96/100
mediumInstalls packages at runtime which could introduce malicious dependencies
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Aide To Pdf?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/ragnarwestad-aide-to-pdf)
---
name: aide-to-pdf
description: >-
Generate PDF from a spec.
Use when: exporting documentation to PDF, generating a print-friendly spec.
Do NOT use for: creating documentation (use aide-create)
argument-hint: "[ISSUE_ID]"
effort: medium
---
You will help the user **generate a PDF** from a spec.
## Input
**Input:** $ARGUMENTS (a spec number, a full folder ID, or an issue key its title began with)
The user has run:
```bash
/aide-to-pdf <ISSUE_ID>
```
**Examples:**
- `/aide-to-pdf 17` - by number
- `/aide-to-pdf 17-fix-validation` - by folder
- `/aide-to-pdf PROJ-7637` - by the issue key the title began with
## Your task
1. **Validate input:**
- If the input matches an issue key (`PROJ-<number>`): the key is part of the slug
- If the input is a number only (`NN`): number shorthand
- Anything else: full directory ID (`NN-slug`)
- If no input: Ask the user for a number or full ID
2. **Determine REPORTS_ROOT:**
```bash
# The lib resolves it: .aide/config in the project root wins,
# otherwise <project-root>/specs
source ~/.local/bin/_aide-spec-lib.sh
REPORTS_ROOT="$(aide_specs_root)"
```
3. **Resolve to the full directory ID** (flat structure: everything lives as `<NN>-slug/` directly under REPORTS_ROOT):
```bash
if echo "$INPUT" | grep -qE '^PROJ-[0-9]+$'; then
# Issue key: find the directory containing it
DIR=$(find "$REPORTS_ROOT" -maxdepth 1 -type d -name "*${INPUT}*" | head -1 | xargs basename)
elif echo "$INPUT" | grep -qE '^[0-9]+$'; then
# Number shorthand: find <NN>-*
NN=$(printf '%02d' "$INPUT")
DIR=$(find "$REPORTS_ROOT" -maxdepth 1 -type d -name "${NN}-*" | head -1 | xargs basename)
else
# Assume full directory ID
DIR="$INPUT"
fi
if [ -z "$DIR" ] || [ ! -d "$REPORTS_ROOT/$DIR" ]; then
echo "Found no issue for: $INPUT"
exit 1
fi
# Example: 27 → finds 27-step-ts-conversion-analysis
```
4. **Check that documentation exists:**
- `$REPORTS_ROOT/<NN-slug>/` (flat structure)
- If not: Inform the user that the spec must be created first (`aide create`)
5. **Generate PDF:**
```bash
# Pass the resolved directory ID (full NN-slug) to the script
aide-generate-pdf "$DIR"
```
The `aide-generate-pdf` script resolves the specs root the same way (via `aide_specs_root`).
The script will:
- Combine all markdown files (1-description, 2-analysis, 3-solution, 4-status)
- Add a cover page with metadata
- Convert to PDF with header/footer
- Output: `$REPORTS_ROOT/<NN-slug>/<NN-slug>.pdf`
6. **Give the user the result:**
- Show the path to the PDF file
- Explain how to open it: `open <path>`
## Error handling
**If `md-to-pdf` is not installed:**
```text
md-to-pdf is not installed
Install with:
npm install -g md-to-pdf
Or run from the project:
npx md-to-pdf
```
**If documentation does not exist:**
```text
Could not find documentation for <ISSUE_ID>
Has the spec been created on the board?
aide create <project> "<title>" # the description on standard input
aide analyze <number>
```
## Notes
- **Input detection:** a spec number, a full folder name, or an issue key its title began with
- **Output location:** Same directory as the markdown files (keeps everything together)
- **AIDE_SPECS_PATH:** read from `.aide/config` in the project root (no environment variable)
- **Styling:** The PDF includes a header with the issue number and a footer with page numbers