skills/confluence-to-wiki/SKILL.md
Pull a Confluence page into an llm-wiki vault as a source-note via the wiki's /ingest convention. One-way (Confluence → wiki), defaults to llm-wiki-simplicity-taskforce-partnership. Use when partner-shared research in Confluence needs to live in the wiki for query, synthesis, or cross-vault linking. Pairs with /ro:confluence and /ingest.
npx skillsauth add RonanCodes/ronan-skills confluence-to-wikiInstall 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.
Mirrors a Confluence page (or page tree) into an llm-wiki-* vault as a source-note. Conforms to the wiki's /ingest source-note conventions: frontmatter, inline ## Sources section, and the canonical wiki page-type fields.
One-way: changes in Confluence are reflected by re-running this skill; changes in the wiki do not flow back. The Confluence page remains the source of truth for partner-shared content.
/ro:confluence-to-wiki 123456789
/ro:confluence-to-wiki https://simplicitylabs.atlassian.net/wiki/spaces/dataforce/pages/123456789/Inventory+sync+algorithm+v2
/ro:confluence-to-wiki 123456789 --vault llm-wiki-simplicity-taskforce-partnership
/ro:confluence-to-wiki 123456789 --with-children # pull the page and all descendants
Default vault: llm-wiki-simplicity-taskforce-partnership (matches the dataforce Confluence space).
/ro:confluence for setup)~/Dev/ai-projects/llm-wiki/vaults/<vault-name>/. If not, run /vault-create first.getConfluencePage). Get title, body, last-updated, author, space, parent.vaults/<vault>/wiki/sources/confluence-<page-id>-<slug>.md:
---
title: <Confluence page title>
page-type: source-note
source-type: confluence
source-url: <full Confluence URL>
source-id: <page-id>
source-space: <space-key>
author: <Confluence author display name>
created: <ISO date>
updated: <ISO date — Confluence last-modified>
mirrored: <today's ISO date>
domain: <vault default domain>
tags: [confluence, partnership]
sources:
- <full Confluence URL>
related: []
---
# <Confluence page title>
> Mirrored from Confluence on <date>. Source of truth: <URL>
<converted body as markdown>
## Sources
- [<page title>](<full Confluence URL>) — Confluence page, space `<space-key>`, last updated <date>
vaults/<vault>/log.md:
- <date>: mirrored Confluence page "<title>" (<id>) → wiki/sources/confluence-<id>-<slug>.md
--with-children: recurse, mirroring each descendant. Link parent ↔ children in the related: frontmatter array.obsidian://open URL so the user can jump straight in.The Atlassian MCP typically returns Confluence content as ADF (Atlassian Document Format) or markdown. Convert to clean wiki markdown:
<ac:image> macros →  (download the image to vaults/<vault>/wiki/assets/ and rewrite the URL to relative)> Embedded Confluence: <url> blockquote@<display name> (lookup their actual entity page in the vault is out-of-scope for v1)If conversion is lossy enough that the page reads badly, fall back to including the raw ADF JSON as a code block at the bottom of the source-note and flag in the body: > Raw ADF preserved below — markdown conversion was partial.
/ingest/ro:confluence-to-wiki — for pages already in Confluence. Wiki-side becomes a mirror. Re-run to refresh./ingest <url> with a Confluence URL — should route here automatically once the confluence: source-type handler is added to the wiki's /ingest router. Until then, this skill is the explicit path./ro:confluence create — when authoring NEW content that needs to live in Confluence (partner-facing). After publishing, optionally mirror back to the wiki via this skill if it's worth querying.| Symptom | Cause | Fix |
|---|---|---|
| "No atlassian MCP tools" | OAuth not done | /mcp → browser auth |
| "Vault not found" | Target vault doesn't exist | Run /vault-create <name> first |
| Body conversion mangles tables | ADF table → markdown is lossy for complex tables | Include raw ADF block as fallback (see above) |
| Page has restricted access | OAuthed user doesn't have view permission on the page | Have the page owner share it, or use an account with broader access |
/ro:confluence — page CRUD inside Confluence/ingest — wiki's generic ingestion router (will get a confluence: handler hooked in separately)/promote — graduate a Confluence-sourced page from this Spoke vault into llm-wiki-research (Hub) if it's reusable knowledgellm-wiki-simplicity-taskforce-partnership — default target vaultdevelopment
Close the loop on a Linear ticket when its work ships - move the status and post a deploy comment with the PR link, what shipped, and a try-it link, mentioning the collaborator. Used as the tail of /ro:linear-nightshift for every merged mirror, or manually after an ad-hoc build. Triggers on "linear update", "update the linear ticket", "mark NUT-x done", "tell eoin it shipped", "/ro:linear-update".
devops
Run a night-shift against a collaborator's Linear board. Pulls the team's Grilled tickets (/ro:linear-grill moves a ticket to Grilled once its questions are answered), VERIFIES the questions were actually answered (unanswered → bounce the ticket to the "Question for <name>" state), mirrors verified tickets to ephemeral GitHub issues with ready-for-agent, then runs the standard /ro:night-shift machinery on GitHub. Tail-calls /ro:linear-update for everything that merged + deployed. Triggers on "linear nightshift", "nightshift linear", "drain the linear board", "run the shift off linear", "/ro:linear-nightshift".
development
Grill a collaborator's Linear tickets and move every processed ticket to where it belongs. Resolves the board from the repo's .ro-linear.json, reads the collaborator's Backlog / Ready-for-agent issues, then per ticket either posts 3-5 decision-extracting questions (state moves to "Question for <name>") or confirms it build-ready (state moves to "Grilled", the gate /ro:linear-nightshift consumes); shipped-and-confirmed tickets close as Done. The async-collaborator counterpart of /ro:day-shift for people who never touch GitHub. Triggers on "grill linear", "grill eoin's tickets", "linear grill", "add questions to the linear tickets", "/ro:linear-grill".
development
--- name: about-page description: Add a standard About page to any web app, what it is, the tech stack, and an FAQ, wired into a footer link with a sticky footer. Built with Spartan + Tailwind (the canonical component layer) and falls back to semantic HTML so it ships reliably. Use whenever building, polishing, or shipping an app, every app should have one. Triggers on "add an about page", "about page", "footer about link", or as a standard step in app build/polish. category: frontend argument-h