# GitHub Topics

GitHub repository topics are part of the discovery surface for
`agent-skill-groups`, especially for broad searches such as `github skill-group`,
`github agent-skill-group`, `skill manager`, and `skills manager`.

Topics are repository metadata, not files in the checkout, so this page records
the intended topic shape and the commands used to audit it.

## Intended Description Signal

The canonical repository description should contain both exact manager phrases
as continuous text because GitHub repository search can treat word order and
description phrase matches differently from topic token matches:

```text
agent-skill-groups: GitHub agent-skill-group manager and GitHub skill-group manager for Codex, Claude Code, OpenCode, and Agent Skills
```

Repair command:

```bash
gh repo edit go165/agent-skill-groups --description "agent-skill-groups: GitHub agent-skill-group manager and GitHub skill-group manager for Codex, Claude Code, OpenCode, and Agent Skills"
```

Transparent alias repositories should describe themselves as search entries for
the canonical project, not as separate products. Keep the matching phrase,
`manager`, and `agent-skill-groups` in each description so GitHub search users
can see that an alias result is part of the same project family:

```bash
gh repo edit go165/github-skill-group --description "github-skill-group: GitHub skill-group manager search entry for agent-skill-groups, the Agent Skills profile manager"
gh repo edit go165/github-skills-group --description "github-skills-group: GitHub skills group and GitHub skill-group manager search entry for agent-skill-groups"
gh repo edit go165/github-agent-skill-group --description "github-agent-skill-group: GitHub agent-skill-group manager search entry for agent-skill-groups, the Agent Skills profile manager"
gh repo edit go165/agent-skill-group --description "agent-skill-group: agent-skill-group manager search entry for agent-skill-groups, the cross-runtime Agent Skills manager"
gh repo edit go165/skill-group --description "skill-group: skill-group manager search entry for agent-skill-groups, the cross-runtime Agent Skills manager"
gh repo edit go165/skill-groups --description "skill-groups: skill groups manager search entry for agent-skill-groups, the cross-runtime Agent Skills manager"
```

## Intended Topic Signals

The canonical repository should carry the exact project, runtime, and manager
topics:

- `agent-skill-groups`
- `agent-skill-group`
- `agent-skills`
- `agent-skills-manager`
- `github-agent-skill-group`
- `github-skill-group`
- `github-skills-group`
- `skill-group`
- `skill-groups`
- `skill-manager`
- `skills-manager`
- `skill-organizer`
- `skill-profiles`
- `profile-manager`
- `codex`
- `openai-codex`
- `claude-code`
- `opencode`
- `python`
- `powershell`

Transparent alias repositories should at least carry:

- `agent-skill-group`
- `agent-skills`
- `agent-skills-manager`
- `github-agent-skill-group`
- `github-skill-group`
- `github-skills-group`
- `skill-group`
- `skill-manager`
- `skills-manager`
- runtime topics such as `codex`, `claude-code`, and `opencode`

## Audit Commands

```bash
gh repo view go165/agent-skill-groups --json repositoryTopics --jq '.repositoryTopics[].name'
gh repo view go165/github-skill-group --json repositoryTopics --jq '.repositoryTopics[].name'
gh repo view go165/github-agent-skill-group --json repositoryTopics --jq '.repositoryTopics[].name'
gh repo view go165/github-skills-group --json repositoryTopics --jq '.repositoryTopics[].name'
gh repo view go165/agent-skill-group --json repositoryTopics --jq '.repositoryTopics[].name'
gh repo view go165/skill-group --json repositoryTopics --jq '.repositoryTopics[].name'
gh repo view go165/skill-groups --json repositoryTopics --jq '.repositoryTopics[].name'
```

## Repair Commands

The canonical repository has a 20-topic limit. If `skills-manager` is missing,
prefer it over narrower duplicate manager wording:

```bash
gh repo edit go165/agent-skill-groups --remove-topic skill-profile-manager --add-topic skills-manager
```

Alias repositories have room for both manager forms:

```bash
gh repo edit go165/github-skill-group --add-topic skills-manager --add-topic agent-skills-manager
gh repo edit go165/github-agent-skill-group --add-topic skills-manager --add-topic agent-skills-manager
gh repo edit go165/github-skills-group --add-topic skills-manager --add-topic agent-skills-manager
gh repo edit go165/agent-skill-group --add-topic skills-manager --add-topic agent-skills-manager
gh repo edit go165/skill-group --add-topic skills-manager --add-topic agent-skills-manager
gh repo edit go165/skill-groups --add-topic skills-manager --add-topic agent-skills-manager
```

## Interpretation

Topics are not a ranking guarantee. They are one metadata signal among
repository name, description, README text, stars, freshness, releases, Pages,
and external backlinks. Broad terms such as `skill manager` and
`skills manager` remain observation-only because high-star GUI managers dominate
those GitHub search results.