/team-skills

name: team-skills
description: Use when listing, adding, or onboarding team skills from the directives repo to the agent's skills directory; --all installs every default and external skill at once.
disable-model-invocation: true

team-skills

Overview

Browse available skills from the team AI directives and install selected ones to the current agent's skills directory. Use `--all` to install every `default` and `external` skill in one pass. Skills are installed under their **original names** (no prefix) so they stay in sync with the manifest.

When to Use

• When the user asks to browse, list, or install team skills.
• When the input names a specific skill to install.
• When extending the agent's capabilities with team-shared skills.
• When `team-setup` delegates `/team-skills --all` after initial configuration.

$ARGUMENTS

Core Process

Setup

Read the file `.adlc/init-options.json` directly. Do NOT use glob, find, or any file-search tool to locate it — search tools may silently skip dotfile-prefixed path segments. Read the file at the exact relative path `.adlc/init-options.json` from the current working directory.

If that read fails (file not found), walk up parent directories by reading `../.adlc/init-options.json`, then `../../.adlc/init-options.json`, and so on — up to 4 levels. Stop at the first successful read.

From the JSON, extract the `team_ai_directives` field:

{
  "team_ai_directives": "/path/to/team-ai-directives"
}

If `team_ai_directives` is not set, STOP:

Team AI directives not configured.
Run: /team-setup

Helper scripts (canonical in `team-setup`, referenced relative to skill directory):

• `$(dirname "$0")/../team-setup/team-helpers.sh --json`
• `$(Split-Path $PSCommandPath -Parent)/../team-setup/team-helpers.ps1 -Json`

Step 1: Read Skills Manifest

Read `{REPO_ROOT}/.skills.json` (where `{REPO_ROOT}` denotes the project root — the directory where `.adlc/` lives) and `{TEAM_AI_DIRECTIVES}/.skills.json` (team directives manifest). Merge both, with project-root entries taking precedence. Parse the manifest sections (schema v2.0.0):

| Section | Description | Installed by `--all`? | |---------|-------------|-----------------------| | `default` | Local skills (in `skills/{name}/`) auto-installed during setup | Yes | | `external` | Remote skills fetched by URL, installed on demand | Yes | | `blocked` | Rejected — must never be installed | Never |

Step 2: Show Available Skills

Present skills grouped by section. For each skill show:

• Name (the key, e.g. `github-actions` for local, `react-best-practices` for external)
• Description
• Whether it's already installed (check agent skills directory)

Format:

Team Skills from {TEAM_AI_DIRECTIVES}

Default (local, installed by --all):
  [installed] dbt-template - DBT project templates and best practices
  [available] github-actions - GitHub Actions CI/CD pipeline patterns
  [available] helm-charts - Helm chart patterns for Kubernetes
  [available] crossplane - Crossplane Composition and XRD patterns
  [available] external-secrets - External Secrets Operator patterns
  [available] gke-workload-identity - GKE Workload Identity patterns

External (remote, installed by --all):
  [available] react-best-practices - React performance optimization
  [available] web-design-guidelines - Web interface best practices

Step 3: Install Selected Skills

Determine the install target from the arguments:

• **`--all`**: Install every `default` skill **and** every `external` skill,

skipping anything in `blocked` and anything already installed.

• **A skill name**: Install that one skill directly.
• **No input**: Ask the user which skills to install.

Determine the agent's skills directory: 1. Read `.adlc/integration.json` to get the current agent 2. Use `{agent_folder}/skills/` as the destination

Install under the **original name** (no prefix), frontmatter `name` unchanged:

For **local skills** (`default` list — names map to `skills/{name}/`):

1. Locate `{TEAM_AI_DIRECTIVES}/skills/{name}/SKILL.md` 2. Copy `SKILL.md` to `{skills_dir}/{name}/SKILL.md`

For **external skills** (`external` map — entries have a `url`):

1. Check the name against `blocked` first — refuse immediately if listed. 2. Verify the entry's `url` starts with `https://` — refuse any other scheme (`http://`, `file://`, bare paths) and report it. 3. Show the user the URL and destination, and ask for confirmation before downloading (preview first, no silent network fetch). 4. Download `SKILL.md` from the entry's `url` field. 5. Save to `{skills_dir}/{name}/SKILL.md`. 6. Never execute downloaded content — install means copy the file only.

Never install any skill listed in `blocked`. Skip skills already present at the destination (report them as `[installed]`).

Step 4: Confirm

Installed: github-actions
Location: .opencode/skills/github-actions/SKILL.md
Source: default (local:./skills/github-actions)

Notes

• Default skills are installed via `--all`, typically invoked by `team-setup`

after initial configuration or run manually at any time.

• Skills are installed under their original names — no `team-` prefix — so the

on-disk name matches the manifest key.

• Skills from the `blocked` list are never installed.
• External skills are fetched over HTTPS from the URL in the manifest.

Common Rationalizations

| Rationalization | Why it's wrong | Do this instead | |---|---|---| | "I'll add a `team-` prefix to installed skills" | Diverges the on-disk name from the manifest key, breaking lookups | Install under the original name; frontmatter `name` stays unchanged | | "Search tools will find `.adlc/init-options.json`" | Glob/find silently skip dotfile-prefixed path segments | Read the exact relative path directly | | "Blocked skills are just strong recommendations" | `blocked` means explicitly rejected on install | Never install blocked skills | | "Default skills already auto-