repo-add

name	repo-add
description	Use when the user asks to register or add a source repository for aim — the repo that provides skills, sub-agents, and/or rules. Handles `aim repo add`, `aim repo list`, `aim repo refresh`, and `aim repo remove`.

Repo Add

A skill for registering source repositories with aim.

When to use

Use this skill whenever the user wants to:

• Add a skill/agent/rule source repo to aim
• Register a git URL so skills, agents, or rules become installable
• Refresh or remove a registered repo

Workflow

1. Ensure aim is installed. Before running any command, check whether aim is available:

   • Try command -v aim or aim --version.
   • If the command succeeds, continue with the workflow.
   • If the command is not found, tell the user: "aim is not installed. Install it with uv tool install? Defaults to the latest version; say a version number if you want a specific one."
   • If the user agrees, run:
     • Latest: uv tool install git+https://github.com/JasperHG90/agent-integrations-manager.git
     • Specific version: uv tool install git+https://github.com/JasperHG90/agent-integrations-manager.git@<version>
   • After installing, verify with aim --version before continuing.
   • If the user declines, stop and explain that this skill requires aim.

2. Gather inputs with AskUserQuestion. If the alias, URL, or ref are not already clear from context, ask using AskUserQuestion. The tool requires header, question, type, and options fields; each option must be an object with label, value, and description. For text inputs, supply example options as quick-select suggestions.

   Example:

   [
     {
       "header": "Repository alias",
       "question": "What alias should I use for this repository? (short, lowercase identifier)",
       "type": "text",
       "options": [
         {"label": "local", "value": "local", "description": "Local filesystem alias"},
         {"label": "anth", "value": "anth", "description": "Anthropic-related alias"},
         {"label": "google", "value": "google", "description": "Google-related alias"}
       ]
     },
     {
       "header": "Repository URL",
       "question": "What is the repository URL?",
       "type": "text",
       "options": [
         {"label": "https repo", "value": "https://github.com/user/repo.git", "description": "Public HTTPS git URL"},
         {"label": "ssh repo", "value": "[e-mail]:user/repo.git", "description": "SSH git URL"},
         {"label": "local repo", "value": "file:///path/to/repo", "description": "Local filesystem path as file URL"}
       ]
     },
     {
       "header": "Git ref (optional)",
       "question": "Which git ref should I pin? Leave blank for HEAD.",
       "type": "text",
       "options": [
         {"label": "main", "value": "main", "description": "Track the main branch"},
         {"label": "v1.0.0", "value": "v1.0.0", "description": "Pin to a specific release tag"},
         {"label": "develop", "value": "develop", "description": "Track a development branch"}
       ]
     }
   ]
   

   If AskUserQuestion is unavailable, ask in plain text and confirm the values before running the command.

3. Register with aim repo add. This clones the repo and indexes its skills, sub-agents, and rules in one operation:

   aim repo add <alias> <url> [--ref <branch-or-tag>]
   

4. After adding, show what became available. Run one or more of:

   aim skill list --compact
   aim subagent list --compact
   aim rule list --compact
   

5. Echo the exact command used and the short SHA/head if the CLI returned it.

Tips

• Alias names must be lowercase alphanumeric, _, or -.
• aim repo add fails if the repo contains no skills, sub-agents, or rules.
• Use aim repo refresh <alias> to pull upstream changes and re-index, and aim repo remove <alias> to unregister.
• Surface any git authentication hints the CLI provides; do not reword them.