Use this skill when visual quality and design identity matter for a PDF. CREATE (generate from scratch): "make a PDF", "generate a report", "write a proposal", "create a resume", "beautiful PDF", "professional document", "cover page", "polished PDF", "client-ready document". FILL (complete form fields): "fill in the form", "fill out this PDF", "complete the form fields", "write values into PDF", "what fields does this PDF have". REFORMAT (apply design to an existing doc): "reformat this document", "apply our style", "convert this Markdown/text to PDF", "make this doc look good", "re-style this PDF". This skill uses a token-based design system: color, typography, and spacing are derived from the document type and flow through every page. The output is print-ready. Prefer this skill when appearance matters, not just when any PDF output is needed.
Read-only queue dashboard for workspace-aware ship. (gstack)
Use when asked to debug, fix a bug, investigate an error, or do root cause analysis, and when users report errors, stack traces, unexpected behavior, or say something stopped working.
Report-only QA testing. (gstack)
Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.
Turn raw notes, ticket/task data, metrics, and standup updates into polished, consistent status reports and executive summaries in a reusable house format. Use this skill whenever the user wants to write, draft, generate, or clean up a weekly status report, team/project update, exec or leadership summary, stakeholder update, or "what I did this week / where things stand" report — or asks to define a house format for reports, make last week's format consistent, or summarize progress for leadership. Trigger even when the user just pastes messy notes, a task export, or last week's report and says "turn this into an update," and even if they don't use the exact word "status report.
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.