Guides conversational setup of JIRA Assistant Skills: checks prerequisites, installs jira-as package, collects credentials and API token, configures environment variables, validates connection.
How this command is triggered — by the user, by Claude, or both
Slash command
/jira-assistant-skills:jira-assistant-setupFiles this command reads when invoked
The summary Claude sees in its command listing — used to decide when to auto-load this command
# JIRA Assistant Setup You are helping the user set up JIRA Assistant Skills. Guide them through the process conversationally. ## Step 1: Check Prerequisites First, verify the environment: Check if the jira-as package is installed: If the library is missing, install it: ## Step 2: Get API Token Tell the user they need an API token from Atlassian. Offer to open the browser: "To connect to JIRA, you'll need an API token from Atlassian. I can open the page where you can create one. Would you like me to open https://id.atlassian.com/manage-profile/security/api-tokens ?" If they ag...
You are helping the user set up JIRA Assistant Skills. Guide them through the process conversationally.
First, verify the environment:
python3 --version
Check if the jira-as package is installed:
pip show jira-as 2>/dev/null && echo "Library installed" || echo "Library missing"
If the library is missing, install it:
pip install jira-as>=0.1.5
Tell the user they need an API token from Atlassian. Offer to open the browser:
"To connect to JIRA, you'll need an API token from Atlassian. I can open the page where you can create one.
Would you like me to open https://id.atlassian.com/manage-profile/security/api-tokens ?"
If they agree, use:
python3 -c "import webbrowser; webbrowser.open('https://id.atlassian.com/manage-profile/security/api-tokens')"
Guide them:
Ask the user for their JIRA credentials:
JIRA Site URL: Ask "What is your JIRA site URL? It should look like https://yourcompany.atlassian.net"
Email: Ask "What email address do you use to log into JIRA?"
API Token: Ask "Please paste your API token (I'll store it securely)"
Profile Name: Ask "What would you like to name this profile? (default: production)"
Guide the user to set environment variables:
For bash/zsh (add to ~/.bashrc or ~/.zshrc):
export JIRA_SITE_URL="https://company.atlassian.net"
export JIRA_EMAIL="[email protected]"
export JIRA_API_TOKEN="their-token-here"
For PowerShell (add to profile):
$env:JIRA_SITE_URL="https://company.atlassian.net"
$env:JIRA_EMAIL="[email protected]"
$env:JIRA_API_TOKEN="their-token-here"
After setting, reload the shell:
source ~/.bashrc # or source ~/.zshrc
Test the connection using the CLI:
jira-as issue get {any_issue_key}
Or test with a Python script:
python3 -c "
from jira_as import get_jira_client
client = get_jira_client()
me = client.get('/rest/api/3/myself')
print(f'Connected as: {me.get(\"displayName\", \"Unknown\")}')
"
If validation succeeds, tell the user:
"Your JIRA Assistant Skills are now set up! Here's what you can do:
Test with a known issue:
jira-as issue get PROJ-123
Or just ask me naturally:
I'm ready to help you with JIRA!"
If authentication fails:
If the CLI is not found:
pip install -e /path/to/pluginpython "${CLAUDE_PLUGIN_ROOT}/skills/jira-issue/scripts/get_issue.py" PROJ-123If import errors occur:
pip install jira-as>=0.1.5npx claudepluginhub grandcamel/jira-assistant-skills --plugin jira-assistant-skills/configure-jiraSets up Jira API credentials interactively, via environment variables, or config file, enabling issue import. Verifies the connection and provides troubleshooting guidance.
/jiraManages Jira tickets: fetch and analyze requirements, add comments, transition status, or search issues with JQL.
/f5-jiraManages unified Jira integration: setup connection, sync issues/files, check status, convert Excel/CSV, handle issues/attachments via subcommands.
/setupGuides interactive setup wizard for Jira Orchestrator v7.5.0: adds Atlassian MCP server, completes OAuth auth, configures Neon PostgreSQL/Redis/Temporal, verifies connections.
/jira-importImports Jira issue or epic by creating local pm/issues or pm/epics directory with kebab-case name and displays details, summary, and acceptance criteria. For epics, prompts for bulk child import.