메뉴
Sync Obsidian documents to Confluence wiki pages via browser automation. Use when pushing docs to Confluence, pulling or replying to comments, incorporating comment feedback, checking page status, or creating new wiki pages.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | confluence-sync |
| description | Sync Obsidian documents to Confluence wiki pages via browser automation. Use when pushing docs to Confluence, pulling or replying to comments, incorporating comment feedback, checking page status, or creating new wiki pages. |
| version | 1.0.0 |
| tags | ["confluence","wiki","sync","obsidian","browser-automation"] |
| metadata | {"related-skills":"doc-standards, obsidian:obsidian-markdown"} |
Sync Obsidian documents to Confluence wiki pages using Chrome DevTools MCP. No Confluence API access required -- all interaction is browser-based.
doc-standards before pushing -- content must
follow the team's documentation code of conductobsidian:obsidian-markdown conventions when
reading or writing frontmatteropen -a "Google Chrome" --args
--remote-debugging-port=9222
--user-data-dir="$(mktemp -d)"google-chrome
--remote-debugging-port=9222
--user-data-dir="$(mktemp -d)".mcp.json
(port 9222)Accepts an Obsidian note path as argument. If no path provided, ask the user. If no command specified, infer from context or ask.
The skill reads and writes a confluence field in the
note's YAML frontmatter:
confluence: >-
https://INSTANCE.atlassian.net/wiki/spaces/
SPACE_KEY/pages/PAGE_ID/Page+Title
confluence URL| Command | Reference | Load When |
|---|---|---|
| push | references/push.md | Pushing or creating |
| pull-comments | references/pull-comments.md | Extracting comments |
| reply-comments | references/reply-comments.md | Replying to comments |
| apply-feedback | references/apply-feedback.md | Incorporating comment feedback |
| status | references/status.md | Checking page metadata |
| Reference | Purpose |
|---|---|
references/confluence-native-elements.md | Native editor elements and shortcuts |
references/diagram-conversion.md | Rendering diagrams for upload |
Handle errors by reporting clearly and stopping. No retry loops.
| Condition | Action |
|---|---|
No confluence (push) | Ask: create new or abort? |
No confluence (pull/status) | Abort with message |
| Page 404 or not found | Report stale URL |
| Edit button not found | Report permission issue |
| Editor not found | Report editor structure change |
| Publish button not found | Report not in edit mode |
| Chrome DevTools fails | Report debug port issue |
| No comments found | Report no comments |
| Reply field not found | Report editor structure change |
| Comment resolved unexpectedly | Report and stop |
| Diagram render fails | Report tool/dependency issue |
| Image upload fails | Report and suggest manual step |
Shape answers so they are immediately actionable instead of long. Use on any response that would otherwise run long — multi-step tasks, explanations, plans, reviews with many findings, or answers that hand back commands, paths, or snippets to run. Leads with the next action, numbers steps, restates progress, caps lists, and gives concrete time estimates. Complements caveman (which handles tone); this handles shape.
Senior software architect for system design, ADRs, microservices evaluation, technology trade-off analysis. Use when designing system architecture, evaluating patterns, creating ADRs, analyzing technology choices, or planning migrations.
Go CLI development with Cobra command hierarchy, Bubbletea interactive TUI, Lipgloss terminal styling, Charmbracelet ecosystem (Bubbles, Huh forms, Glamour markdown rendering), and shell completions. Use when building CLI tools, adding subcommands, creating interactive TUI, styling terminal output, or implementing shell completions.
Cloud architecture design, migration, optimization, and disaster recovery across AWS and Azure. Use when designing VPCs/VNets, IAM/RBAC, compute/storage architectures, cost optimization, multi-cloud patterns, or planning migrations. Both Terraform and CLI approaches.
Datadog monitoring strategy, alert design, tagging governance, dashboard patterns, SLO strategy, log management, cost optimization, and cross-pillar correlation workflows. Use when making architectural decisions about what to monitor, how to alert, how to tag, or how to structure Datadog for a service or platform. Delegates execution to pup CLI and infrastructure-as-code to sre-engineer.
Kubernetes workload management, Helm chart development, cluster troubleshooting, custom operators, configuration management, and multi-cluster administration. Use when deploying workloads, writing Helm charts, debugging pods, creating operators, managing ConfigMaps/Secrets/RBAC, or working with multi-cluster setups.