Run any Skill in Manus with one click

export-pdf

Stars4

Forks1

UpdatedApril 17, 2026 at 10:04

Export markdown file(s) to styled dark-theme PDF. Use for requests like "export to PDF", "convert markdown to PDF", "generate PDF", "make a PDF from markdown", or "export md".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

lespaceman

lespaceman/athena-workflow-marketplace

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name	export-pdf
description	Export markdown file(s) to styled dark-theme PDF. Use for requests like "export to PDF", "convert markdown to PDF", "generate PDF", "make a PDF from markdown", or "export md".
allowed-tools	Bash(node:*) Read Glob

Export the specified markdown file(s) to a clean, dark-themed PDF.

Instructions

Resolve the path(s) from $ARGUMENTS. If it is a glob pattern, use the Glob tool to expand it. If no argument is provided, ask which file to export.
Resolve the plugin root:
- If ATHENA_PLUGIN_ROOT is set, use it.
- Otherwise derive it as the directory two levels above the current SKILL.md file.
For each markdown file, run the generation script:

node "<plugin-root>/scripts/generate-pdf.mjs" "<absolute-path-to-md-file>"

The script will:

Auto-derive the document label from the filename (e.g., self-correction-report.md → "Self Correction Report")
Output the PDF in the same directory as the source file
Apply the dark-theme stylesheet with clean typography and spacing

Report the result by listing each PDF created and its path.
If the script reports an error about puppeteer-core not being installed, run:

cd "<plugin-root>" && npm install puppeteer-core

Then retry the export.

More from this repository

same repository

capture-feature-evidence

lespaceman/athena-workflow-marketplace

Deeply explore a live app feature or a single mapped sub-feature and capture grounded evidence for downstream planning in `docs/qa/exploration-report.md` or a scoped file under `docs/qa/exploration/`. Use after the requested scope is already known, especially after `map-feature-scope` has identified bounded sub-features for a large feature. This skill owns observed product evidence and blockers for the scoped area; it does not perform feature decomposition, frame exploratory charters, prioritize risks, or write coverage plans.

2026-07-014

map-feature-scope

lespaceman/athena-workflow-marketplace

Quickly map a broad product feature into concrete sub-features before deep exploration begins. Use when a requested feature may span multiple routes, tabs, overlays, roles, or primary interactive surfaces and the agent needs to identify bounded exploration units, shared state, and blockers before spawning parallel browser subagents. This skill owns `docs/qa/feature-map.md`; it does not produce the final deep exploration evidence, coverage plan, or test specs.

2026-07-014

exploratory-test-writer

lespaceman/athena-workflow-marketplace

Define an exploratory testing charter: frame what to investigate, why it matters, and which risk hypotheses to test before or alongside the shared testing workflow. Triggers include "exploratory testing for...", "what should I investigate in this app", "help me think about what could go wrong", "risk hypotheses for...", "testing charter for...", "where should I probe deeper", or any request that needs structured thinking about test intent before coverage planning begins. This skill owns exploratory intent, risk framing, investigation order, and concrete follow-up asks for missing evidence; it does NOT own exploration evidence (capture-feature-evidence), final coverage prioritization (plan-test-coverage), or test case specs (generate-test-cases).

2026-07-014

add-playwright-tests

lespaceman/athena-workflow-marketplace

THE DEFAULT ENTRY POINT for the Playwright execution layer in the split testing suite. Use to add, create, or set up Playwright end-to-end tests for a feature, page, or application. It orchestrates the full Playwright workflow after shared exploration and planning: analyze the Playwright codebase, consume `docs/qa/feature-map.md`, `docs/qa/exploration-report.md`, `docs/qa/coverage-plan.md`, and `docs/qa/test-cases/*.md`, write production-grade test code, review it, and verify it with real execution. Delegates to `analyze-test-codebase`, `write-test-code`, `review-test-code`, and `fix-flaky-tests`, while relying on shared `map-feature-scope`, `capture-feature-evidence`, `plan-test-coverage`, `generate-test-cases`, and `review-test-cases`.

2026-07-014

analyze-test-codebase

lespaceman/athena-workflow-marketplace

Scans and reports on an existing Playwright test codebase. This skill should be used to inspect the current Playwright setup before writing, reviewing, or fixing tests, and should be loaded early when working in a new project to understand existing patterns. Covers: Playwright config, page objects, fixtures, helpers, auth/globalSetup patterns, test conventions, and directory structure. Triggers: "understand", "check", "show me", "inspect", or "analyze" the current test setup, config, infrastructure, patterns, or conventions. In the full add-tests workflow, this skill serves as an early read-only analysis sub-step before planning detailed coverage or writing code. This skill examines existing files and outputs a structured report. It does NOT write or fix tests, install Playwright, or explore live websites — for live-site exploration, use `capture-feature-evidence` so evidence is captured in `docs/qa/exploration-report.md`.

2026-07-014

review-test-code

lespaceman/athena-workflow-marketplace

Quality review of Playwright test code before final execution signoff. This skill should be used when implementation review of executable Playwright tests is needed, not for diagnosis of runtime flakiness. Triggers: "review test code", "review Playwright tests", "check test quality", "audit test implementation", "review my tests before merging", "check test code for issues", "review e2e tests", "code review Playwright", "are my tests stable", "check for brittle selectors", "review before running tests". Quality gate after write-test-code — catches brittle selectors, force:true misuse, networkidle overuse, Tailwind utility class selectors, exact numeric assertions, missing teardown, parallel-unsafe mutations, hardcoded data, missing assertions, test coupling, and convention divergence. Review-only — does NOT rewrite tests, does NOT run tests. Use fix-flaky-tests for fixing, write-test-code for rewriting.

2026-07-014

name	export-pdf
description	Export markdown file(s) to styled dark-theme PDF. Use for requests like "export to PDF", "convert markdown to PDF", "generate PDF", "make a PDF from markdown", or "export md".
allowed-tools	Bash(node:*) Read Glob

Export the specified markdown file(s) to a clean, dark-themed PDF.

Instructions

Resolve the path(s) from $ARGUMENTS. If it is a glob pattern, use the Glob tool to expand it. If no argument is provided, ask which file to export.
Resolve the plugin root:
- If ATHENA_PLUGIN_ROOT is set, use it.
- Otherwise derive it as the directory two levels above the current SKILL.md file.
For each markdown file, run the generation script:

node "<plugin-root>/scripts/generate-pdf.mjs" "<absolute-path-to-md-file>"

The script will:

Auto-derive the document label from the filename (e.g., self-correction-report.md → "Self Correction Report")
Output the PDF in the same directory as the source file
Apply the dark-theme stylesheet with clean typography and spacing

Report the result by listing each PDF created and its path.
If the script reports an error about puppeteer-core not being installed, run:

cd "<plugin-root>" && npm install puppeteer-core

Then retry the export.