菜单
Cache management, API diagnostics, and operational utilities. Use when optimizing performance, managing cache, diagnosing API issues, or troubleshooting Confluence connectivity.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | confluence-ops |
| description | Cache management, API diagnostics, and operational utilities. Use when optimizing performance, managing cache, diagnosing API issues, or troubleshooting Confluence connectivity. |
| triggers | ["cache","cache status","cache clear","cache warm","api diagnostics","performance","rate limit","troubleshoot","connectivity","health check"] |
Cache management, API diagnostics, and operational utilities for Confluence Assistant.
This skill manages operational aspects of Confluence integration. Use for:
| Use This Skill | Use Instead |
|---|---|
| Check cache status | - |
| Clear/warm cache | - |
| Diagnose API issues | - |
| Check rate limits | - |
| Manage pages | confluence-page |
| Search content | confluence-search |
| Manage spaces | confluence-space |
| Operation | Risk | Notes |
|---|---|---|
| Cache status | - | Read-only |
| API diagnostics | - | Read-only |
| Cache warm | - | Adds cache entries |
| Cache clear | ⚠️ | Removes cache, may slow next requests |
Use this skill when you need to:
Trigger conditions:
# Check cache status
confluence ops cache-status
# Clear all cache
confluence ops cache-clear --force
# Warm cache with space metadata
confluence ops cache-warm --spaces
# Test API connectivity
confluence ops health-check
# Full API diagnostics
confluence ops api-diagnostics
| Command | Purpose | Risk |
|---|---|---|
confluence ops cache-status | Display cache statistics | - |
confluence ops cache-clear | Clear cache entries | ⚠️ |
confluence ops cache-warm | Pre-warm cache | - |
confluence ops health-check | Test API connectivity | - |
confluence ops rate-limit-status | Check rate limit usage | - |
confluence ops api-diagnostics | Diagnose API issues | - |
# Basic status
confluence ops cache-status
# Output as JSON
confluence ops cache-status --output json
# Verbose output with entry details
confluence ops cache-status --verbose
Output example:
Cache Status
────────────────────────────
Total entries: 1,234
Total size: 45.2 MB
Hit rate: 78.5%
By category:
spaces: 23 entries (1.2 MB)
pages: 892 entries (38.4 MB)
users: 156 entries (2.1 MB)
search: 163 entries (3.5 MB)
Oldest entry: 2024-01-15 10:30:00
Newest entry: 2024-01-20 14:45:00
# Cache space list
confluence ops cache-warm --spaces
# Cache specific space metadata
confluence ops cache-warm --space DOCS
# Cache all available metadata
confluence ops cache-warm --all --verbose
# JSON output for scripting
confluence ops cache-warm --spaces --output json
# Clear all cache (with confirmation)
confluence ops cache-clear
# Clear all cache (skip confirmation)
confluence ops cache-clear --force
# Clear only page cache
confluence ops cache-clear --category pages --force
# Preview what would be cleared
confluence ops cache-clear --dry-run
# Clear keys matching pattern
confluence ops cache-clear --pattern "DOCS-*" --category pages --force
# Clear entries older than N days
confluence ops cache-clear --older-than 7 --force
# JSON output for scripting
confluence ops cache-clear --force --output json
# Full health check
confluence ops health-check
# Test specific endpoint
confluence ops health-check --endpoint "/api/v2/spaces"
# Verbose output with timing
confluence ops health-check --verbose
# JSON output for scripting
confluence ops health-check --output json
Output example:
Confluence Health Check
────────────────────────────
Site URL: https://your-site.atlassian.net
Status: ✓ Connected
API Version: v2
Response Time: 234ms
Endpoint Tests:
/api/v2/spaces ✓ 156ms
/api/v2/pages ✓ 189ms
/rest/api/search ✓ 312ms
Authentication: ✓ Valid
User: your-email@example.com
# Check current rate limit status
confluence ops rate-limit-status
# JSON output
confluence ops rate-limit-status --output json
Output example:
Rate Limit Status
────────────────────────────
Status: ✓ No rate limit errors detected
Note: Confluence Cloud does not expose rate limit headers in API responses.
Rate limits are applied server-side and vary by endpoint and account tier.
Recommendations:
- Monitor for HTTP 429 responses
- Implement exponential backoff on retries
- Limit bulk operations to 5-10 concurrent requests
- Add small delays between rapid sequential calls
| Category | Description | Default TTL |
|---|---|---|
spaces | Space metadata | 1 hour |
pages | Page content and metadata | 5 minutes |
users | User information | 1 hour |
search | Search results | 2 minutes |
labels | Label data | 15 minutes |
permissions | Permission data | 5 minutes |
Cache is stored in ~/.confluence-skills/cache/ with configurable TTL per category.
Environment variables:
CONFLUENCE_CACHE_DIR - Custom cache directoryCONFLUENCE_CACHE_ENABLED - Enable/disable caching (default: true)CONFLUENCE_CACHE_TTL - Default TTL in seconds (default: 300)| Code | Meaning |
|---|---|
| 0 | Success |
| 1 | General error |
| 2 | Configuration error |
| 3 | Cache database error |
| 4 | Network/connectivity error |
| Issue | Solution |
|---|---|
| Slow API responses | Run cache-warm --all to pre-populate cache |
| Stale data | Run cache-clear --force then cache-warm |
| 429 Rate limit | Wait for reset, reduce request frequency |
| Connection timeout | Check health-check, verify credentials |
| Cache corruption | Run cache-clear --force |
View analytics, statistics, and popularity metrics for Confluence content. ALWAYS use when user wants to see views, popularity, or contributor stats.
Manage file attachments - upload, download, list, and delete attachments. ALWAYS use when user wants to work with files on pages.
Manage comments on Confluence pages - add, get, update, delete, and resolve comments. ALWAYS use for feedback, discussions, and inline annotations.
Navigate and manage Confluence page hierarchies, ancestors, descendants, and trees. ALWAYS use for parent/child relationships and page tree navigation.
JIRA integration - embed issues, create links between products. ALWAYS use when user wants to connect Confluence and JIRA.
Manage content labels - add, remove, and search by labels. ALWAYS use when user wants to tag, label, or categorize content.