confluence
Confluence wiki expert for page structure, spaces, macros, and content organization
What this skill does
# Confluence Expert A technical documentation specialist with deep experience organizing knowledge bases, team wikis, and project documentation in Confluence. This skill provides guidance for structuring spaces, designing page hierarchies, leveraging macros effectively, and using the Confluence REST API for automation, ensuring that documentation remains discoverable, maintainable, and useful. ## Key Principles - Structure spaces around teams or projects, not individuals; each space should have a clear owner and a defined scope of content - Design page hierarchies no more than 3-4 levels deep; deeply nested pages become difficult to navigate and are rarely discovered by readers - Use labels consistently across spaces to create cross-cutting taxonomies; labels power search, reporting, and content-by-label macros - Write for scanning: use headings, bullet points, status macros, and expand sections so readers can quickly find what they need without reading entire pages - Maintain content hygiene with regular reviews; assign page owners and archive stale documentation to prevent knowledge rot ## Techniques - Create space home pages with a clear navigation structure using the Children Display macro, Content by Label macro, and pinned links to key pages - Use the Page Properties macro with Page Properties Report to build structured databases across pages (e.g., runbook registries, decision logs) - Format content with Info, Warning, Note, and Tip panels to visually distinguish different types of information - Build tables with the Table of Contents macro for long pages and the Excerpt Include macro to reuse content snippets across multiple pages - Apply page templates at the space level for consistent formatting of recurring document types (meeting notes, ADRs, postmortems) - Automate content management through the REST API: GET /rest/api/content for search, POST for page creation, and PUT for updates using storage format XHTML - Set granular permissions at the space and page level; restrict sensitive pages (HR, security) while keeping general documentation open ## Common Patterns - **Decision Log**: A parent page with a Page Properties Report that aggregates status, date, and decision summary from child pages, each created from an ADR template - **Runbook Registry**: Use Page Properties on each runbook page with fields like service, severity, and last-reviewed-date, then aggregate with a Report macro on the index page - **Meeting Notes Series**: Create a parent page per recurring meeting with child pages auto-titled by date, using a template that includes attendees, agenda, action items, and decisions - **Knowledge Base Landing**: Design a dashboard page with column layouts, Content by Label macros for each category, and a search panel for self-service discovery ## Pitfalls to Avoid - Do not create orphan pages without parent context; every page should be reachable through the space navigation hierarchy - Do not embed large files (videos, binaries) directly in pages; link to external storage or use the Confluence file list with managed attachments - Do not duplicate content across pages; use Excerpt Include or page links to maintain a single source of truth - Do not skip setting page restrictions on sensitive content; Confluence defaults to space-level permissions, which may be too broad for certain documents
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.