> ## Documentation Index
> Fetch the complete documentation index at: https://ai-development-environment.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Skill group details

> Manage a skill group's membership, repository assignments, and deployment.

<Frame>
  <img className="block dark:hidden" src="https://mintcdn.com/ai-development-environment/XmuMCFv09SOCZYoa/images/light/skill-group-detail.png?fit=max&auto=format&n=XmuMCFv09SOCZYoa&q=85&s=e35c37fd4655f9a4843f0b68e56d8cff" alt="Skill group details page in light theme" width="3840" height="2160" data-path="images/light/skill-group-detail.png" />

  <img className="hidden dark:block" src="https://mintcdn.com/ai-development-environment/aldo79nFpNgOg3HT/images/dark/skill-group-detail.png?fit=max&auto=format&n=aldo79nFpNgOg3HT&q=85&s=9eb34e5819dd381cc839ffb8a19e0c56" alt="Skill group details page in dark theme" width="3840" height="2160" data-path="images/dark/skill-group-detail.png" />
</Frame>

The skill group details page at `/skills/groups/{id}` sets the two halves of a group: which skills are in it, and which repositories use it. Saving the group is what changes the *intended* state; a sync is what makes disk match.

## Editing a group

<Steps>
  <Step title="Name the group" icon="pencil">
    Up to 80 characters. The name is how the group is identified everywhere else, including the inline group picker during a sync.
  </Step>

  <Step title="Choose skills" icon="sparkles">
    **Skills in this group** lists every database skill with a checkbox and a searchable filter over names and descriptions. Ticking a skill here is equivalent to ticking this group in the [skill editor](/skills/skill-detail).
  </Step>

  <Step title="Choose repositories" icon="folder-git-2">
    **Repositories using this group** lists every registered repository with its display origin, again with a search filter. Every checkout and worktree of a selected repository becomes a deployment target.
  </Step>

  <Step title="Save" icon="save">
    **Save group** persists membership and assignment together and reloads the page from the saved state.
  </Step>
</Steps>

## Deploying

**Sync group** prepares a reconciliation scoped to this group and opens the resulting [sync run](/skills/skill-sync-run), where you review the proposed changes before anything is written. A group sync touches only the repositories this group is assigned to, which makes it the safer choice while iterating on one project's skills.

<Note>
  With **Auto-sync project skill groups** enabled in **Settings** on the [Skills](/skills/skills) page, assignments reconcile into registered checkouts and worktrees automatically and a manual sync is only needed when you want to see the plan first.
</Note>

## Deleting

<Warning>
  **Delete** removes the group and, during synchronization, removes the deployed copies of its skills that no longer belong to another group assigned to the same repository. Skills themselves are not deleted — only the group and the deployments it alone justified.
</Warning>

## Notes

* A skill can belong to several groups. Its copy survives in a repository as long as at least one assigned group still contains it.
* Removing a repository from the group has the same effect as deleting the group for that repository: the skills stop being justified there and are cleaned up on the next sync.

## Related pages

<Columns cols={2}>
  <Card title="Skill groups" icon="folder-tree" href="/skills/skill-groups">
    The list this page opens from.
  </Card>

  <Card title="Skill editor" icon="file-pen" href="/skills/skill-detail">
    The other side of group membership.
  </Card>

  <Card title="Skill synchronization" icon="refresh-cw" href="/skills/skill-sync-run">
    Review and apply what a group sync proposes.
  </Card>

  <Card title="Repository details" icon="folder-git-2" href="/codebases/repository-detail">
    The repositories a group targets.
  </Card>
</Columns>
