Git integrations

capa fetches remote capabilities from Git hosts: skills, plugins, rules, hooks, and agent instruction snippets. Public repos need no auth. Private repos use capa auth or the Web UI Integrations flow; tokens live in ~/.capa/capa.db.

Repo string grammar

The same @ / :: grammar applies on both GitHub and GitLab (and in capabilities.yaml def.repo fields):

Form	Meaning
`owner/repo@name`	Recursive search for a basename (skill dir with `SKILL.md`, or a file basename for rules/snippets). No slashes on the right-hand side.
`owner/repo::path/inside/repo`	Exact path from the repo root. No search.

Pinning (both forms):

:tag-or-branch — e.g. @skill:v1.2.0, ::rules/git.md:main
#sha — commit SHA, e.g. @skill#abc1234

Resolved commits are recorded in capabilities.lock.

GitHub

GitHub is the default host. No prefix required.

CLI
capabilities.yaml

# Search by skill folder name
capa add vercel-labs/agent-skills@web-researcher

# Exact path
capa add my-org/skills::skills/team-a/web-researcher

# Pin tag or SHA
capa add vercel-labs/agent-skills@web-researcher:v1.2.0
capa add vercel-labs/agent-skills@web-researcher#abc1234

# Tree URL (capa parses branch/tag/SHA)
capa add https://github.com/vercel-labs/agent-skills/tree/v1.2.0/skills/web-researcher

# Plugin
capa add --plugin slackapi/slack-mcp-plugin
capa add --plugin anthropics/claude-plugins-official::plugins/frontend-design

skills:
  - id: web-researcher
    type: github
    def:
      repo: vercel-labs/agent-skills@web-researcher
      description: Web research skill
      requires:
        - '@brave.search'

plugins:
  - id: frontend-design
    type: github
    def:
      repo: anthropics/claude-plugins-official::plugins/frontend-design

Private GitHub

capa auth github.com or Web UI → Integrations → Connect GitHub
capa add my-org/private-skills@team-helper
capa install

Public repos need no token.

GitLab

Prefix CLI sources with gitlab:. Nested groups are supported (any number of path segments before the project).

CLI
capabilities.yaml

# Search
capa add gitlab:mygroup/myrepo@web-researcher

# Nested groups
capa add gitlab:mygroup/subgroup/skills@data-analyst

# Exact path
capa add gitlab:mygroup/skills::skills/team/web-researcher

# Pin
capa add gitlab:mygroup/myrepo@web-researcher:v1.2.0

# Tree URL
capa add https://gitlab.com/mygroup/myrepo/-/tree/main/skills/web-researcher

# Plugin
capa add --plugin gitlab:acme/platform/team/services/devops-skills:v1.0.1

skills:
  - id: custom-skill
    type: gitlab
    def:
      repo: mygroup/subgroup/myrepo@skill-name
      description: Skill from GitLab
      requires:
        - '@server1.tool1'

In YAML, type: gitlab uses def.repo without the gitlab: CLI prefix (group/project@name).

Self-hosted GitLab

Prefer a full HTTPS URL when the host is not gitlab.com:

capa add https://gitlab.mycompany.com/mygroup/myrepo.git

Or a raw/remote skill URL with type: remote in the capabilities file when you only need a single SKILL.md.

Private GitLab

capa auth gitlab.com or Web UI → Integrations → Connect GitLab
capa add gitlab:my-org/private-skills@team-helper
capa install

Optional PAT alternative:

export GITLAB_TOKEN=glpat-yourtoken
capa add gitlab:mygroup/private-skills@my-skill

What can come from Git

Resource	Typical `def.repo` / CLI
Skills	`capa add owner/repo@skill`
Plugins	`capa add --plugin owner/repo`
Rules	Usually `owner/repo::path/to/rule.md`
Agent instructions	Snippets via `github` / `gitlab` / `local`
Registries	Adapter sources from git or HTTPS

Auth commands

capa auth                 # default Git provider
capa auth github.com
capa auth gitlab.com

See Credentials and CLI: auth.