Confluence

Skill yuelenghan/orbit/skills/confluence

An open-source arsenal of reusable skills for AI agents — repo understanding, code review, delivery workflows, security pentests, and plug-and-play integrations with Jira, GitHub, GitLab, Jenkins & more. Drop into Claude Code, Codex, or any skill-aware host.

Install

npx -y skills add yuelenghan/orbit --skill confluence

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when the user needs Confluence Data Center page, space, attachment, comment, metadata, search, configuration, create, update, or read operations.

SKILL.md

4.3 KB, as published. Nobody here has run it

Confluence Skill

Use this skill to operate Confluence Data Center through the packaged local CLI runtime.

Treat the user-facing term PAT as the packaged CLI --token value when you need to save auth config.

Runtime and execution

Use <skill-dir> below to mean the installed skill directory root.

Always run the packaged launcher from the installed skill directory so it works from the user's current working directory:

macOS/Linux: <skill-dir>/bin/confluence
Windows: <skill-dir>\bin\confluence.cmd

The packaged launcher first reuses a compatible system Node runtime when available. If no compatible system Node runtime is available, the launcher uses a bundled runtime when present or bootstraps a target-specific runtime from the configured mirror.

Do not call node dist/cli.js directly. Do not call Confluence REST API directly from the skill layer.

Scope and boundaries

Confluence Data Center only (not Cloud).
CLI-mediated operations only.
PAT authentication only.
Content body format is Confluence storage.
Use page labels and page properties for page metadata.
Use attachment and comment command groups for page-linked collaboration objects.

Capability Domain

Domain:

docs

Provides:

docs.config.get
docs.config.set
docs.content.search
docs.content.get
docs.content.create
docs.content.update
docs.content.label.add
provider-specific workflow helpers

Config check:

confluence config get

Config check

Run confluence config get when configuration state is unknown or before the first provider-scoped task in a new session.

Supporting files

Read references/commands.md for command families and packaged launcher forms.
Read references/usage.md for execution policy, read/write behavior, update/version rules, and help-based recovery.
Read examples/common-workflows.md for end-to-end examples.

When the command family or option spelling is uncertain, use packaged CLI help before guessing:

<skill-dir>/bin/confluence <group> --help
<skill-dir>/bin/confluence <group> <action> --help

Use help probes to correct uncertainty, not to rediscover the whole CLI from scratch. If a help-guided retry still fails, return the real CLI failure.

Keep the config bootstrap exception: do not run config set --help before saving recovered config.

Provider-specific caveats

When a packaged CLI command fails with CONFIG_ERROR, collect only the missing values and recover configuration in the skill flow.

Run packaged config get first to check existing values.
If the initial failure is stored config was not found, skip config get and collect config directly.
If the user already provided both baseUrl and PAT, skip extra config probing and save immediately.
Ask only for values still missing.
Run the packaged config set command yourself through <skill-dir>/bin/confluence.
Always map the user-provided PAT to the CLI --token option, never --pat.
Always use the documented CLI option spelling --base-url, never guessed variants such as --baseUrl.
Do not run config set --help or other help probes before saving recovered config.
Never echo the PAT back in chat output.
Retry the original command once.
If retry still fails, return the real failure.

Search behavior

search pages accepts only --cql for the query input.
Never guess undocumented query flags such as --query or --keyword for search pages.
When the user asks for a natural-language page search, translate that request into CQL first, then run search pages --cql <CQL>.
search pages returns the current page or current batch by default.
Use search pages --all only when the user explicitly wants every matching page.
Only describe search results as “all pages” when the CLI response includes fetchedAll: true.
For search pages --limit / --start, describe the output as the current page or current batch.
Use packaged CLI help only when the action family or option spelling is still uncertain after applying this contract.