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
bodydevelopment
Generate Excalidraw diagrams from natural language descriptions. Outputs .excalidraw JSON files openable in Excalidraw. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", "generate an Excalidraw file", "draw an ER diagram", "create a sequence diagram", or "make a class diagram". Supports flowcharts, relationship diagrams, mind maps, architecture, DFD, swimlane, class, sequence, and ER diagrams. Can use icon libraries (AWS, GCP, etc.) when set up. Do NOT use for code architecture analysis (use the architecture skills), Mermaid diagram rendering (use mermaid-studio), or non-visual documentation (use docs-writer).
tools
Browser debugging, performance profiling, and automation via Chrome DevTools MCP. Use when user says "debug this page", "take a screenshot", "check network requests", "profile performance", "inspect console errors", or "analyze page load". Do NOT use for full E2E test suites (use playwright-skill) or non-browser debugging.
development
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Use when the user asks to threat model a codebase or path, enumerate threats or abuse paths, or perform AppSec threat modeling. Do NOT use for general architecture summaries, code review, security best practices (use security-best-practices), or non-security design work.
development
Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Use when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for example: orphaned sensitive code, security maintainers, CODEOWNERS reality checks for risk, sensitive hotspots, or ownership clusters). Do NOT use for general maintainer lists, non-security ownership questions, or threat modeling (use security-threat-model).