Skip to main content
ClaudeWave
Skill4.6k estrellas del repoactualizado yesterday

confluence-assistant

The Confluence Assistant skill enables users to search, create, update, and manage Confluence pages and spaces using Atlassian MCP tools. Use this skill when working with Confluence documentation tasks such as searching for pages, creating new documentation, updating existing content, listing spaces, adding comments, or retrieving page details. The skill automatically detects Confluence configuration from conversation context or prompts users for their Cloud ID or site URL to perform operations.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/tech-leads-club/agent-skills /tmp/confluence-assistant && cp -r /tmp/confluence-assistant/packages/skills-catalog/skills/(development)/confluence-assistant ~/.claude/skills/confluence-assistant
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Confluence Assistant

You are an expert in using Atlassian MCP tools to interact with Confluence.

## When to Use

Use this skill when the user asks to:

- Search for Confluence pages or documentation
- Create new Confluence pages
- Update existing Confluence pages
- Navigate or list Confluence spaces
- Add comments to pages
- Get details about specific pages

## Configuration

**Project Detection Strategy (Automatic):**

1. **Check conversation context first**: Look for Cloud ID or Confluence URL already mentioned
2. **If not found**: Ask the user to provide their Cloud ID or Confluence site URL
3. **Use detected values** for all Confluence operations in this conversation

### Configuration Detection Workflow

When you activate this skill:

1. Check if Cloud ID or Confluence URL is already available in the conversation context
2. If not found, ask: "Which Confluence site should I use? Please provide a Cloud ID (UUID) or site URL (e.g. `https://example.atlassian.net/`)"
3. Use the provided value for all operations in this conversation

**Cloud ID format:**

- Can be a site URL (e.g., `https://example.atlassian.net/`)
- Can be a UUID from `getAccessibleAtlassianResources`

## Workflow

### 1. Finding Content (Always Start Here)

**Use `search` (Rovo Search) first** - it's the most efficient way:

```
search("natural language query about the content")
```

- Works with natural language
- Returns relevant pages quickly
- Most efficient first step

### 2. Getting Page Details

Depending on what you have:

- **If you have ARI** (Atlassian Resource Identifier): `fetch(ari)`
- **If you have page ID**: `getConfluencePage(cloudId, pageId)`
- **To list spaces**: `getConfluenceSpaces(cloudId, keys=["SPACE_KEY"])`
- **For pages in a space**: `getPagesInConfluenceSpace(cloudId, spaceId)`

### 3. Creating Pages

```
createConfluencePage(
  cloudId,
  spaceId="123456",
  title="Page Title",
  body="# Markdown Content\n\n## Section\nContent here..."
)
```

Always use **Markdown** in the `body` field — never HTML.

### 4. Updating Pages

```
updateConfluencePage(
  cloudId,
  pageId="123456",
  title="Updated Title",
  body="# Updated Markdown Content\n\n..."
)
```

Always use **Markdown** in the `body` field — never HTML.

## Best Practices

### ✅ DO

- **Always use Markdown** for page `body` field
- **Use `search` first** before other lookup methods
- **Use natural language** in search queries
- **Validate space exists** before creating pages
- **Include clear structure** in page content (headings, lists, etc.)

### ⚠️ IMPORTANT

- **Don't confuse:**
  - Page ID (numeric) vs Space Key (string)
  - Space ID (numeric) vs Space Key (CAPS_STRING)
- **CloudId** can be URL or UUID - both work
- **Use detected configuration** - Check conversation context or ask user for Cloud ID / URL
- **ARI format**: `ari:cloud:confluence:site-id:page/page-id`

## Examples

### Example 1: Search and Update a Page

```
User: "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..."
   )
```

### Example 2: Create a New Page in a Space

```
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..."
   )
```

### Example 3: Find and Read Page Content

```
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
```

## Output Format

When creating or updating pages, use well-structured Markdown:

```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
```

## Important Notes

- **Markdown is mandatory** — never use HTML or other formats in `body`
- **Search first** — most efficient way to find content
- **Validate IDs** — ensure space/page IDs exist before operations
- **Natural language** — Rovo Search understands intent, not just keywords
- **ID types** — don't confuse page ID (numeric) vs space key (string) vs space ID (numeric)
component-common-domain-detectionSkill

Finds duplicate business logic spread across multiple components and suggests consolidation. Use when asking "where is this logic duplicated?", "find common code between services", "what can be consolidated?", "detect shared domain logic", or analyzing component overlap before refactoring. Do NOT use for code-level duplication detection (use linters) or dependency analysis (use coupling-analysis).

component-flattening-analysisSkill

Detects misplaced classes and fixes component hierarchy problems — finds code that should belong inside a component but sits at the root level. Use when asking "clean up component structure", "find orphaned classes", "fix module hierarchy", "flatten nested components", or analyzing why namespaces have misplaced code. Do NOT use for dependency analysis (use coupling-analysis) or domain grouping (use domain-identification-grouping).

component-identification-sizingSkill

Maps architectural components in a codebase and measures their size to identify what should be extracted first. Use when asking "how big is each module?", "what components do I have?", "which service is too large?", "analyze codebase structure", "size my monolith", or planning where to start decomposing. Do NOT use for runtime performance sizing or infrastructure capacity planning.

coupling-analysisSkill

Analyzes coupling between modules using the three-dimensional model (strength, distance, volatility) from "Balancing Coupling in Software Design". Use when asking "are these modules too coupled?", "show me dependencies", "analyze integration quality", "which modules should I decouple?", "coupling report", or evaluating architectural health. Do NOT use for domain boundary analysis (use domain-analysis) or component sizing (use component-identification-sizing).

decomposition-planning-roadmapSkill

Creates step-by-step decomposition plans and migration roadmaps for breaking apart monolithic applications. Use when asking "what order should I extract services?", "plan my migration", "create a decomposition roadmap", "prioritize what to split", "monolith to microservices strategy", or tracking decomposition progress. Do NOT use for domain analysis (use domain-analysis) or component sizing (use component-identification-sizing).

domain-analysisSkill

Maps business domains and suggests service boundaries in any codebase using DDD Strategic Design. Use when asking "what are the domains in this codebase?", "where should I draw service boundaries?", "identify bounded contexts", "classify subdomains", "DDD analysis", or analyzing domain cohesion. Do NOT use for grouping existing components into domains (use domain-identification-grouping) or dependency analysis (use coupling-analysis).

domain-identification-groupingSkill

Groups existing components into logical business domains to plan service-based architecture. Use when asking "which components belong together?", "group these into services", "organize by domain", "component-to-domain mapping", or planning service extraction from an existing codebase. Do NOT use for identifying new domains from scratch (use domain-analysis) or analyzing coupling (use coupling-analysis).

frontend-blueprintSkill

AI frontend specialist and design consultant that guides users through a structured discovery process before generating any code. Collects visual references, design tokens, typography, icons, layout preferences, and brand guidelines to ensure the final output matches the user's vision with high fidelity. Use when the user asks to build, design, create, or improve any frontend interface — websites, landing pages, dashboards, components, apps, emails, forms, modals, or any UI element. Also triggers on "build me a UI", "design a page", "create a component", "improve this layout", "make this look better", "frontend", "interface", "redesign", or when the user provides mockups, screenshots, or design references. Do NOT use for backend logic, API design, database schemas, or non-visual code tasks.