skills/confluence/SKILL.md
--- name: confluence description: Create, update, read, and Smart-Link Confluence pages via the Atlassian Remote MCP server. Defaults to the dataforce space on the Simplicity Labs site. Use when user wants to draft a research doc, post meeting notes, or link a Confluence page to a Jira ticket. Pairs with /ro:jira and /ro:confluence-to-wiki. category: project-management argument-hint: [create "title" [--parent <page-id>] [--body-file <path>] | update <page-id> [--body-file <path>] | show <page-id
npx skillsauth add RonanCodes/ronan-skills skills/confluenceInstall 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.
Opinionated wrapper around the Atlassian Remote MCP server's Confluence tools. Reads defaults from ~/.claude/.env. Common case is the dataforce space on simplicitylabs.atlassian.net.
/ro:confluence create "Inventory sync algorithm v2" --body-file ./notes.md
/ro:confluence create "Taskforce x Simplicity weekly — 2026-05-22" --parent <weekly-notes-page-id>
/ro:confluence update <page-id> --body-file ./revised.md
/ro:confluence show <page-id>
/ro:confluence link <page-id> DAFO-42 # Smart Link: append the Jira issue panel
/ro:confluence list --parent <page-id> # children under a parent
Override defaults: --space <key> --site <host>.
Same as /ro:jira:
claude mcp add --transport http --scope user atlassian https://mcp.atlassian.com/v1/mcp/authv2/mcp → OAuth the atlassian server in browser~/.claude/.env:
ATLASSIAN_SITE=simplicitylabs.atlassian.net
ATLASSIAN_CONFLUENCE_SPACE_DEFAULT=dataforce
Use the live mcp__atlassian__* tools at runtime. Typical mapping:
| Verb | What to do | Atlassian MCP tool (typical name) |
|---|---|---|
| create | Convert body to Atlassian storage format (the MCP usually accepts markdown and converts), set space + optional parent, post | createConfluencePage |
| update | Fetch current version, increment, post new body | updateConfluencePage |
| show | Fetch page, render title + URL + body as markdown | getConfluencePage |
| link | Append an inline-card / Smart Link macro for the Jira issue URL to the page body, then update. Alternatively, comment on the Jira ticket with the Confluence URL — do both for two-way visibility | updateConfluencePage + addJiraIssueComment |
| list | List children of a parent page | getConfluenceChildren / searchConfluenceUsingCql |
--body-file <path> over inline --body. Confluence pages are long; quoting markdown on the command line is painful.--raw.When linking a Confluence page to a DAFO ticket:
> Related Jira: <ticket URL>This gives partners a clickable trail in both directions.
create / update: page title + URL + parent path (if any)show: title + URL above, body as markdown belowlink: confirmation that both sides were updated + both URLslist: markdown table of children (title, id, last updated)/ingest/ro:confluence create when authoring partner-facing content the Taskforce people need to see in Confluence (meeting notes, agreements, research summaries, RFCs for partner review)./ingest into llm-wiki-simplicity-taskforce-partnership when capturing private notes, thinking, or research that doesn't need to round-trip with partners. Then /promote selected pages into llm-wiki-research if they're reusable knowledge./ro:confluence-to-wiki to pull an existing Confluence page into the wiki as a source-note (one-way mirror, doesn't sync back).| Symptom | Cause | Fix |
|---|---|---|
| "No atlassian MCP tools" | OAuth not done | /mcp then browser auth |
| Body renders broken (tables, code) | Markdown → storage conversion edge case | Pass --raw and supply storage-format XHTML directly |
| "Space not found" | Default not loaded or space key wrong | Verify ATLASSIAN_CONFLUENCE_SPACE_DEFAULT=dataforce in env; pass --space |
| Update fails with version conflict | Page edited elsewhere between fetch and post | Re-fetch, re-apply, retry |
/ro:jira for ticket ops/ro:confluence-to-wiki for pulling pages into the llm-wiki vaulttesting
--- name: linear-pipeline description: The Fable orchestrator for a single dispatched Linear ticket. Holds almost no context itself; it receives `--issue <ID> --detached`, decides the stage sequence, and fans out a sub-agent per stage, passing forward only each stage's artifact (never re-derived, never inlined into its own context). Step zero, before any planning or stage routing, is a boundary triage against `canon/security-boundary.md` (#199): a match tags Ronan Connolly and stops the run, no
development
--- name: in-your-face description: Capture a chat-only answer into a durable artifact (markdown + HTML, PDF when cheap) and launch it automatically so the user cannot miss it. Use when user says "in your face", "don't let me lose this", "save that answer", "make that durable", or right after answering a substantive side question (a recipe, comparison, how-to, or generated prompt) that would otherwise die with the context. category: workflow argument-hint: [--no-open] [--vault <short>] [hint of
tools
One-shot headless OpenAI Codex CLI calls for background/admin AI tasks — summaries, classification, extraction, admin glue. The default engine for anything that runs AI constantly in the background (daemon-driven, per-event), because it bills the flat ChatGPT subscription instead of Claude usage or per-token API spend, and it keeps working while Claude is rate-limited. NEVER for coding — coding stays Claude. Use when a skill or daemon needs a cheap always-on AI call, when the user says "use codex", "ask codex", "codex as backup", or when building a background summarizer/classifier into a listener or loop. Reads auth from ~/.codex/auth.json (ChatGPT account, no API key).
research
Turn a warranty rejection, repair quote, or RMA email into a cited decision brief — legal read (NL/EU consumer law), is the part user-serviceable, live part and new-unit prices, repair-vs-DIY-vs-new economics, before-you-send-it checklist, deadlines. Use when the user pastes or screenshots a repair quote, warranty rejection, "not covered" email, onderzoekskosten fee, or asks "should I repair or replace this".