Connectors

Connectors give Slo tools for the systems your work already lives in. Today that's Jira and Confluence. Once connected, you can say "read PAY-412 and write a spec for it" and Slo pulls the ticket itself.

What Slo can do with Jira and Confluence

Tool	What it does
`search_jira_using_jql`	Find issues with a JQL query.
`get_jira_issue`	Read one issue: summary, description, type, status, project and parent.
`create_jira_issue`	Create an issue or sub-task. Plain-text descriptions are converted for Jira.
`search_confluence_using_cql`	Find pages with a CQL query.
`get_confluence_page`	Read a page's title, URL and body.

The tools only appear once credentials are set, so a session without them won't try to reach Atlassian.

Connect Atlassian

Create an API token in your Atlassian account settings, then set all three variables:

export SLO_ATLASSIAN_SITE_URL="https://your-team.atlassian.net"
export SLO_ATLASSIAN_EMAIL="you@example.com"
export SLO_ATLASSIAN_API_TOKEN="your-api-token"

Start slo and ask it something that needs Jira:

"Find the open bugs in the PAY project assigned to me and summarise them."

Requests time out after 30 seconds. Change that with SLO_ATLASSIAN_TIMEOUT_SECONDS.

Storing credentials in a file instead

If you'd rather not keep tokens in your shell profile, Slo also reads credentials.json from its connectors folder:

~/.slo/connectors/atlassian/credentials.json

The folder follows SLO_HOME, or set SLO_CONNECTORS_DIR to put it somewhere else. Keep the file readable only by you (chmod 600).

When both exist, the file wins. On CI, where secrets usually arrive as environment variables, set SLO_CONNECTOR_PREFER_ENV=1 to flip that order.

Good things to ask for

"Read PAY-412 and its sub-tasks, then write a feature specification."
"Create a sub-task under PAY-412 for each task in the breakdown."
"Search Confluence for our refund policy and check the spec against it."

Pair this with the feature specifications workflow and a ticket can go from Jira to a reviewed spec without copy and paste.