packages/skills-catalog/skills/(development)/confluence-assistant/SKILL.md
Expert in Confluence operations using Atlassian MCP. Use when the user says "search Confluence", "create a Confluence page", "update a page", "find documentation in Confluence", "list spaces", or "add a comment to a page". Do NOT use for Jira issues, general web search, or local file creation.
npx skillsauth add tech-leads-club/agent-skills confluence-assistantInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert in using Atlassian MCP tools to interact with Confluence.
Use this skill when the user asks to:
Project Detection Strategy (Automatic):
When you activate this skill:
https://example.atlassian.net/)"Cloud ID format:
https://example.atlassian.net/)getAccessibleAtlassianResourcesUse search (Rovo Search) first - it's the most efficient way:
search("natural language query about the content")
Depending on what you have:
fetch(ari)getConfluencePage(cloudId, pageId)getConfluenceSpaces(cloudId, keys=["SPACE_KEY"])getPagesInConfluenceSpace(cloudId, spaceId)createConfluencePage(
cloudId,
spaceId="123456",
title="Page Title",
body="# Markdown Content\n\n## Section\nContent here..."
)
Always use Markdown in the body field — never HTML.
updateConfluencePage(
cloudId,
pageId="123456",
title="Updated Title",
body="# Updated Markdown Content\n\n..."
)
Always use Markdown in the body field — never HTML.
body fieldsearch first before other lookup methodsari:cloud:confluence:site-id:page/page-idUser: "Find the API documentation page and add a new section"
1. search("API documentation")
2. getConfluencePage(cloudId, pageId="found-id")
3. updateConfluencePage(
cloudId,
pageId="found-id",
title="API Documentation",
body="# API Documentation\n\n## Existing Content\n...\n\n## New Section\nNew content here..."
)
User: "Create a new architecture decision record"
1. getConfluenceSpaces(cloudId, keys=["TECH"])
2. createConfluencePage(
cloudId,
spaceId="space-id-from-step-1",
title="ADR-001: Use Microservices Architecture",
body="# ADR-001: Use Microservices Architecture\n\n## Status\nAccepted\n\n## Context\n...\n\n## Decision\n...\n\n## Consequences\n..."
)
User: "What's in our onboarding documentation?"
1. search("onboarding documentation")
2. getConfluencePage(cloudId, pageId="id-from-results")
3. Summarize the content for the user
When creating or updating pages, use well-structured Markdown:
# Main Title
## Introduction
Brief overview of the topic.
## Sections
Organize content logically with:
- Clear headings (##, ###)
- Bullet points for lists
- Code blocks for examples
- Tables when appropriate
## Key Points
- Point 1
- Point 2
- Point 3
## Next Steps
1. Step 1
2. Step 2
3. Step 3
bodytools
Reviews a GitHub pull request and posts inline comments plus one consolidated summary, adapting to any codebase by discovering the project's own test runner, requirement specs, and architecture conventions before running six specialized review agents in parallel. Stack-agnostic across language and framework; targets GitHub PRs via the gh CLI. Use when the user says "review PR 128", "review this PR", "code review this PR", or "check this pull request". Do NOT use for creating PRs or responding to review comments (use gh-address-comments), or debugging failing CI checks (use gh-fix-ci).
development
Opinionated Rails conventions: rich models, concerns, CRUD-everything, state-as-records, minimal dependencies, Minitest with fixtures. Load this skill BEFORE any code-level thinking, not only before editing a file. It is required the moment a task touches Rails code in ANY way: designing or even just discussing a data model, schema, migration, entity, association, field, validation, class, or method name; writing, planning, reviewing, analyzing, testing, debugging, or refactoring; or proposing any model, table, column, route, or code snippet inline in chat. If you are about to name a model or sketch a column you are already in scope, even in an exploratory back-and-forth where no file is written yet. Do not let a "we're just discussing" framing defer it. Do NOT use for non-Rails backends, NestJS, or general architecture (use nestjs-modular-monolith or coding-guidelines).
testing
Feature planning and implementation with 4 adaptive phases — Specify, Design, Tasks, Execute. Auto-sizes depth by complexity. Creates atomic tasks with verification criteria, atomic git commits, and requirement traceability. Features an independent Verifier (author != verifier, evidence-or-zero), persistent decision log (STATE.md), and test-coverage-matrix-driven tests, plus a self-improving lessons layer that turns verification failures into reusable project-local guidance. Stack-agnostic. Use when (1) Planning features (requirements, design, task breakdown), (2) Implementing with verification and atomic commits, (3) Validating or verifying an implementation against a spec. Triggers on "specify feature", "discuss feature", "design", "tasks", "implement", "validate", "verify work", "UAT", "record decision", "pause work", "resume work". Do NOT use for architecture decomposition analysis (use architecture skills) or technical design docs (use create-technical-design-doc).
development
Generative Engine Optimization (GEO) specialist — the technical, on-page publishing work that makes a given page or site discoverable, understandable, trustworthy, quotable, and fresh for AI answer engines (Google AI Overviews, ChatGPT Search, Bing Copilot, Perplexity). Use when asked to 'optimize this page/site for GEO', 'optimize for AI search / answer engines', 'get my page cited by ChatGPT/Perplexity', 'improve AI visibility/citability', 'write an llms.txt', 'add citation-ready structure or schema for AI answers', 'otimizar para busca com IA', or to audit/create/improve a codebase for generative search. Do NOT use for AI-driven SEO content strategy or programmatic pages at scale (use ai-seo), classic keyword/SERP ranking (use seo), accessibility (use web-accessibility), or multi-area site audits (use web-quality-audit).