atlassian-setup

Configure Atlassian API credentials for Jira and Confluence access.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/al-stev/field-eng-skills --skill atlassian-setup-al-stev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atlassian-setup
Source: https://github.com/al-stev/field-eng-skills/tree/main/.claude/skills/atlassian-setup
Command: npx skills add https://github.com/al-stev/field-eng-skills --skill atlassian-setup-al-stev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eliminates the friction and security risk of manually configuring Atlassian credentials by guiding users to create an API token, save it securely, and validate access to Jira and Confluence.

Core Features & Use Cases

  • Secure credential storage: Instructs how to save ATLASSIAN_EMAIL and ATLASSIAN_TOKEN to ~/.fe-skills/.env with restricted file permissions.
  • Token generation guidance: Walks through creating an Atlassian API token and the expected account scopes.
  • Optional CLI setup: Shows how to install and configure the jira-cli for ad-hoc terminal use and provides verification commands for both Jira and Confluence.
  • Troubleshooting: Lists common failure modes (401s, incorrect instance URL, permission issues) and recovery steps.

Quick Start

Run the atlassian-setup skill to create an API token, save ATLASSIAN_EMAIL and ATLASSIAN_TOKEN into ~/.fe-skills/.env with secure permissions, and verify Jira and Confluence connectivity.

Frequently Asked Questions about atlassian-setup

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

FAQPage Schema
How do I set up an Atlassian API token for Jira and Confluence access?

To set up an Atlassian API token, create a token in your Atlassian account, then save your ATLASSIAN_EMAIL and ATLASSIAN_TOKEN to the ~/.fe-skills/.env file with restricted file permissions to enable secure CLI and scripted Jira and Confluence access.

Why does my Atlassian API token return a 401 error?

An Atlassian API token returns a 401 error due to incorrect credentials, wrong instance URL, or insufficient account scopes. Verify your ATLASSIAN_EMAIL and ATLASSIAN_TOKEN in ~/.fe-skills/.env and ensure your token has the required permissions for Jira and Confluence.

Do I need jira-cli to interact with Jira tickets from the terminal?

You do not need jira-cli to interact with Jira tickets as it is an optional dependency for ad-hoc terminal use. The core setup only requires an Atlassian email and API token stored in ~/.fe-skills/.env to enable scripted tool access.

Can I configure credentials for specific Atlassian instances like W&B and CoreWeave?

You can configure credentials for specific Atlassian instances like W&B and CoreWeave by storing your ATLASSIAN_EMAIL and ATLASSIAN_TOKEN in the ~/.fe-skills/.env file, which validates access to those specific Jira and Confluence instances during ticketing workflows.

What is the best way to securely store Atlassian API credentials for automation?

The best way to securely store Atlassian API credentials for automation is saving the ATLASSIAN_EMAIL and ATLASSIAN_TOKEN variables in the ~/.fe-skills/.env file with restricted file permissions, preventing unauthorized access during scripted ticketing and documentation workflows.