rai-adapter-setup

Discover Jira and Confluence backends, generate validated YAML configs, and verify via rai doctor.

71|8|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/humansys/raise --skill rai-adapter-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rai-adapter-setup
Source: https://github.com/humansys/raise/tree/main/packages/raise-cli/src/raise_cli/skills_base/rai-adapter-setup
Command: npx skills add https://github.com/humansys/raise --skill rai-adapter-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual adapter setup for Jira and Confluence is error-prone and slow because developers must discover instance details, project keys, and space trees, then hand-edit YAML while avoiding secrets. This Skill automates live discovery, reduces user questions to a few choices, validates generated configuration, and prevents accidental secret writes.

Core Features & Use Cases

  • Live backend discovery: Detects which adapters are available from environment credentials and lists discovered Jira projects and Confluence spaces.
  • Validated config generation: Generates and model-validates YAML for .raise/jira.yaml and .raise/confluence.yaml before writing.
  • Safe write & verification: Previews changes, requires explicit overwrite confirmation, never writes secrets to files, and runs rai doctor to verify results.
  • Use Case: Onboarding a new developer or initializing a repository integration after rai init to quickly register project keys, spaces, and routing without manual ID lookup.

Quick Start

Ask the skill to detect available Jira and Confluence backends, generate validated .raise/jira.yaml and .raise/confluence.yaml, preview the YAML, and confirm writing to disk.

Frequently Asked Questions about rai-adapter-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically discover and configure Jira and Confluence adapters?

Jira and Confluence adapter configuration is automated by detecting available backends from environment credentials, discovering projects and spaces, and generating validated YAML files after explicit user confirmation. This live discovery process requires minimal input and avoids writing secrets to disk.

What is the safest way to generate YAML configuration files for Jira and Confluence integrations?

YAML configuration generation is safe because the system model-validates the output, previews the changes, requires explicit overwrite confirmation, and never writes secrets to files. It securely generates validated .raise/jira.yaml and .raise/confluence.yaml configurations.

How do I verify that my Jira and Confluence adapter setup is working correctly?

Adapter setup is verified by running rai doctor after writing the configuration files. This verification step checks the generated YAML to ensure the Jira and Confluence backend connections are successfully configured and operational.

Do I need to manually find Jira project keys and Confluence spaces before setting up adapters?

Manual discovery of Jira project keys and Confluence spaces is not needed. The setup process performs live backend discovery to automatically detect available projects and spaces, reducing user input to a few simple choices during onboarding.

When should I run the adapter setup for Jira and Confluence during project onboarding?

Adapter setup should be run after running rai init or when adapter configuration is missing. It is designed for project onboarding to quickly register project keys, spaces, and routing without manual ID lookup.

Why does manual adapter setup for Jira and Confluence fail?

Manual adapter setup fails because developers must hand-edit YAML while discovering instance details and avoiding secrets. Automated discovery and validated configuration generation prevent these errors by soliciting minimal input and verifying success.