skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
dedalus-erp-pas/foundation-skills72 installs

setup

Installe les outils CLI prérequis (gh, glab, jq), guide l'authentification GitHub/GitLab, installe uvx et configure le serveur MCP mcp-atlassian existant pour Jira dans OpenCode. Idempotent : relancer le skill est sans danger. Déclenché quand l'utilisateur dit « setup », « install prerequisites » ou « configurer jira ». Pour construire un nouveau serveur MCP (et non configurer un existant), utiliser plutôt mcp-builder.

How do I install this agent skill?

npx skills add https://github.com/dedalus-erp-pas/foundation-skills --skill setup
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill is a setup utility that installs standard developer tools like the GitHub and GitLab CLIs, jq, and the uv/uvx tool suite. It downloads these components from official, well-known sources (GitHub, GitLab, and Astral) and configures a local Jira integration using credentials provided interactively by the user. The skill follows security best practices by setting restrictive file permissions on the configuration file.

  • Socketwarn

    1 alert: gptAnomaly

  • Snykfail

    Risk: HIGH · 3 issues

  • ZeroLeakspass

    1 finding · Score: 82/100

What does this agent skill do?

Setup — Prerequisites & MCP Configuration

Install CLI tools, authenticate to GitHub/GitLab, and configure the mcp-atlassian Jira integration for OpenCode.

Prerequisites

  • Linux with apt package manager
  • bash and curl available
  • Internet access (for apt packages and uv installer)

Trigger

User says: "setup", "install prerequisites", "configure jira", or similar.

Important — interactive skill only. This skill requires user interaction (auth prompts, Jira credentials). It must not be called as a sub-step from autonomous skill pipelines (fast-meeting, issue-review, etc.) — doing so will stall the pipeline waiting for input that will never arrive.


Workflow

Phase 1 — Install CLI tools

Run the bundled script to install missing tools (idempotent — skips already-installed ones):

bash "$(dirname "$0")/reference/setup.sh"

The script installs (via apt if not already present):

  • gh — GitHub CLI
  • glab — GitLab CLI
  • jq — JSON processor
  • uvx — via the official uv installer (curl -LsSf https://astral.sh/uv/install.sh | sh)

After running, inform the user of what was installed vs. already present.

Phase 2 — CLI Authentication

Check and authenticate each CLI:

gh auth status 2>&1
  • Show the full output to the user (current logged-in account, token scopes, etc.)
  • If not authenticated → tell the user: "Run gh auth login and follow the prompts."
  • Do NOT run gh auth login automatically (requires interactive input).
glab auth status 2>&1
  • Show the full output to the user (GitLab instance, current user, token validity, etc.)
  • If not authenticated → tell the user: "Run glab auth login and follow the prompts."
  • Do NOT run glab auth login automatically.

Phase 3 — Configure mcp-atlassian for Jira

Step 3.1 — Check if uvx is available:

uvx --version 2>&1 || ~/.local/bin/uvx --version 2>&1

If not found, remind the user to restart their shell or source ~/.bashrc / ~/.profile after the Phase 1 script ran.

Step 3.2 — Read existing OpenCode config:

Use the Read tool to read ~/.config/opencode/opencode.json.

  • If the file does not exist, treat it as {}.
  • If mcp.mcp-atlassian is already present → confirm to the user and skip the rest of Phase 3.

Step 3.3 — Gather credentials (if not already configured):

Ask the user these two questions in a single message:

  1. Jira URL — default https://jira.dedalus.com/ (Server/Data Center). Press Enter to accept.
  2. Jira Personal Access Token (PAT) — steps to generate one:
    • Log in to your Jira instance
    • Go to Profile → Personal Access Tokens
    • Click Create token, give it a name, set an expiry
    • Copy the token and paste it here

For Jira Cloud users: use JIRA_USERNAME (your email) + JIRA_API_TOKEN (from https://id.atlassian.com/manage-profile/security/api-tokens) instead of a PAT.

Step 3.4 — Write the config:

Merge the mcp-atlassian block into ~/.config/opencode/opencode.json, preserving any existing content. Use the Write tool to write the final JSON.

For Server/Data Center (default):

{
  "mcp": {
    "mcp-atlassian": {
      "type": "local",
      "command": ["uvx", "mcp-atlassian"],
      "environment": {
        "JIRA_URL": "<jira-url>",
        "JIRA_PERSONAL_TOKEN": "<pat>"
      },
      "enabled": true
    }
  }
}

For Cloud (if user specifies):

{
  "mcp": {
    "mcp-atlassian": {
      "type": "local",
      "command": ["uvx", "mcp-atlassian"],
      "environment": {
        "JIRA_URL": "<jira-url>",
        "JIRA_USERNAME": "<email>",
        "JIRA_API_TOKEN": "<api-token>"
      },
      "enabled": true
    }
  }
}

Step 3.5 — Secure the config file:

chmod 600 ~/.config/opencode/opencode.json

Phase 4 — Summary

Print a clear summary table:

ComponentStatus
ghinstalled / already ok
glabinstalled / already ok
jqinstalled / already ok
uvxinstalled / already ok
gh authauthenticated / action needed
glab authauthenticated / action needed
mcp-atlassianconfigured / already ok / skipped

End with: "Restart OpenCode to load the new MCP configuration."

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/dedalus-erp-pas/foundation-skills/setup">View setup on skillZs</a>