Team Skills logo

Team Skills

Organization
tikalk
team-skills

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.

Overview

Publishertikalk
Repositoryadlc-team-skills
Skill nameteam-skills
Stars
144
Forks
2
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by tikalk on GitHub. Read the source before you install it.

Installation

Install the Team Skills AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/tikalk/adlc-team-skills/tree/main/skills/team/team-skills
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/tikalk/adlc-team-skills.git /tmp/adlc-team-skills
mkdir -p .claude/skills
cp -r /tmp/adlc-team-skills/skills/team/team-skills .claude/skills/team-skills
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Team Skills in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Team Skills on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Team Skills is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.
text
$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:

json
{
  "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/scripts/bash/team-helpers.sh --json
  • $(Split-Path $PSCommandPath -Parent)/../team-setup/scripts/powershell/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):

SectionDescriptionInstalled by --all?
defaultLocal skills (in skills/{name}/) auto-installed during setupYes
externalRemote skills fetched by URL, installed on demandYes
blockedRejected — must never be installedNever

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

RationalizationWhy it's wrongDo this instead
"I'll add a team- prefix to installed skills"Diverges the on-disk name from the manifest key, breaking lookupsInstall under the original name; frontmatter name stays unchanged
"Search tools will find .adlc/init-options.json"Glob/find silently skip dotfile-prefixed path segmentsRead the exact relative path directly
"Blocked skills are just strong recommendations"blocked means explicitly rejected on installNever install blocked skills
"Default skills already auto-installed elsewhere"Only --all (via team-setup or manual) installs themRun /team-skills --all to onboard the default set
"I'll skip merging the project-root manifest"Project entries are meant to override team defaultsMerge both manifests; project-root wins conflicts

Red Flags

  • Using glob, find, or grep to locate .adlc/init-options.json instead of reading the exact path.
  • Renaming a skill or adding a team- prefix on install — install under the original name so it matches the manifest.
  • Installing a skill listed under the blocked section.
  • Writing skills to any directory other than the agent's configured skills folder.
  • Proceeding past an unset team_ai_directives field instead of stopping with the config message.
  • Fetching an external skill over a non-HTTPS URL.

Verification

  • .adlc/init-options.json was read directly (no search tool) and team_ai_directives resolved to a path.
  • Both {REPO_ROOT}/.skills.json and {TEAM_AI_DIRECTIVES}/.skills.json were merged; project-root entries won any conflicts.
  • Each installed skill lives at {skills_dir}/{name}/SKILL.md with its original name in frontmatter (no prefix).
  • No skill from the blocked section was installed.
  • --all installed every default and external skill (skipping blocked and already-installed).
  • A confirmation block was emitted showing the installed name, on-disk location, and source.

Configuration

  • TEAM_AI_DIRECTIVES — Path to the team AI directives (overrides .adlc/init-options.json).
  • .adlc/init-options.json — Project-level config file with team_ai_directives field.
  • Default fallback: team-ai-directives/ relative to project root.
  • ../team-setup/scripts/bash/team-helpers.sh / ../team-setup/scripts/powershell/team-helpers.ps1 — Shared scripts (canonical in team-setup) used for path resolution.

12-Factor Alignment

Factor XII (Team Capability) — manages team skill catalog and installation.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Team Skills AI skill do?

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.

Why use Team Skills on TypingMind?

Because you install it once and use it with any model. Team Skills is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Team Skills in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/tikalk/adlc-team-skills/tree/main/skills/team/team-skills. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Team Skills?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Team Skills?

As many as you like. As long as a model supports skills, you can use Team Skills with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Team Skills AI skill free?

Yes. It is published on GitHub by tikalk under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇