quarto-authoring
SolidUse when the user is explicitly working with Quarto, .qmd files, _quarto.yml, Quarto projects, or Quarto features such as callouts, cross-references, citations, Mermaid diagrams, extensions, websites, books, presentations, and reports. Also use for explicit migration from or comparison with R Markdown, bookdown, blogdown, xaringan, distill, or Jupyter notebooks to Quarto. Do not use for general R Markdown or related-format questions unless Quarto or migration to Quarto is explicitly mentioned.
Install
Quality Score: 91/100
Skill Content
Details
- Author
- posit-dev
- Repository
- posit-dev/skills
- Created
- 6 months ago
- Last Updated
- today
- Language
- R
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
document
Draft a technical document from an intent or a source. Triggers on "write the runbook / ADR / RCA / PR description / commit message / changelog / diagram / README / migration guide / API reference / experiment report / incident summary / onboarding doc / design doc". Markdown-first: produces a draft in a local file and NEVER publishes (no Confluence / Jira / Slack / GitHub posting — that is a separate concern). Reader-first voice: leads with the reader's question, cites every non-trivial claim to a repo path or quoted source, caps external quotes at 15 words, cuts filler. Audience-tuned (engineer / pm / exec / mixed) — the voice does not mix. GitHub context (PR / issue) is read via the gh CLI.
advanced-skill-authoring
Use when authoring or revising a skill and needing patterns beyond the basics — structure choice (XML tags vs markdown), tool-preference phrasing, composition with other loaded skills, post-deployment compliance monitoring, or choosing between skill/hook/CLAUDE.md/slash-command/subagent mechanisms.
adk-document
Document, write, draft, write-up, summarize. Generates any professional markdown artifact: runbook, ADR, RCA, PR body, commit message, changelog, Mermaid diagram, README, migration guide, API reference, experiment report, incident summary, onboarding doc, design doc, handoff doc. Markdown-first; repo-bound: output goes to `<repo>/.temp/adk/document/<task>/draft.md` (or repo-canonical path with --write-to). Does NOT publish — that's /adk-sync. Composable: any other adk skill can call this to generate a writeup, then call /adk-sync to push it. Cites every non-trivial claim to a repo path or quoted source; no filler phrases (anti-pattern grep enforced). Audience-tuned (engineer / pm / exec / mixed) — voice doesn't mix. Loads adk-agent-doc-writer always; loads relevant shared/guidelines (observability for runbook/RCA, api-design for api-reference, security for RCA, accessibility for UI docs) by --type. Quotes from external sources capped at 15 words.