# Repos/Skills

- Canonical collection: <https://hubset.live/repos>
- Detail pattern: `https://hubset.live/repos/{slug}`
- Public repository API: [`GET /api/repos`](https://hubset.live/api/repos)
- Public resource API: [`GET /api/resources`](https://hubset.live/api/resources)

## Purpose

A build library for reusable agent skills, GitHub-backed projects, and curated Toolbox links. Use it as a gateway to external sources for implementation work: skills to suggest or install with permission, UI component libraries, design-inspiration galleries, frontend references, and other useful web tools.

## URL-linked views

- `/repos` or `/repos?view=all`: grouped overview.
- `/repos?view=skills`: records where `repo_kind` is `skill`.
- `/repos?view=repositories`: GitHub-backed projects where `repo_kind` is `project`.
- `/repos?view=toolbox`: curated resources where `resource_kind` is `toolbox`.
- `q={text}`: client-side search across the selected library.
- `group={value}`: focused grouping for Skills or Toolbox when the value is exposed by the page.

`view=projects` is a compatibility alias for `view=repositories`. Tutorials are not part of this hub; use `/tutorials`. Legacy `view=tutorials` and `view=resources` redirect there.

## Repository records

Useful fields include `id`, `name`, `slug`, `description`, `repo_kind`, `url`, `github_url`, `language`, `stars`, `tags`, `featured`, `image_url`, and timestamps.

- `url` is the product website.
- `github_url` is source code.
- `repo_kind` is `skill` or `project`.
- Skill detail pages may expose a validated `npx skills add {github_url}` copy action. Do not invent an install command when a valid GitHub source is absent.
- Repository detail responses can include `related_resources`.

## Toolbox records

Toolbox items come from `/api/resources` where `resource_kind` is `toolbox`. Their canonical detail route remains `/repos/resources/{slug}`. A resource may include `repo_id` and `linked_repo` to associate it with a Skill or Repository.

The Toolbox focus groups are explicitly editable classification fields, not frontend slug rules. For Toolbox records, use `toolbox_group` as one of `frontend`, `agent-tools`, `ai-models`, or `creative`. If `toolbox_group` is `frontend`, `toolbox_subgroup` may be `inspiration` or `components`; omit it for the other groups. The public Repositories/Toolbox filter uses these API fields directly. Legacy records without the fields may use a temporary fallback classification.

## How an agent should use this library

### Repository and skill discovery workflow

1. Fetch the complete [`GET /api/repos`](https://hubset.live/api/repos) array.
2. Filter that array locally using `repo_kind`, `name`, `description`, `tags`, and `language`. Do not assume the human-page `q` parameter is a server-side API search parameter.
3. After selecting a record, fetch its canonical detail with `GET /api/repos?slug={slug}` before using or recommending it.

### Toolbox discovery workflow

1. Fetch the complete [`GET /api/resources`](https://hubset.live/api/resources) array.
2. Filter locally for `resource_kind=toolbox`, then use `toolbox_group`, `toolbox_subgroup`, `title`, `description`, `tags`, and `type` to select a result.
3. Fetch the selected record with `GET /api/resources?slug={slug}` before following its official source or recommending it.

The current catalogs are intentionally small enough for this workflow. Agents should not invent undocumented `q`, `tag`, `offset`, or pagination behavior for these APIs.

Then apply these editorial rules:

1. Begin with Skills when the task calls for reusable agent instructions or an existing skill.
2. Begin with Toolbox → Frontend when the task needs UI components, visual references, design inspiration, typography, icons, or frontend utilities.
3. Use the record's description and metadata plus its canonical detail page to judge relevance before suggesting it to a human or using it as a research lead.
4. Follow `github_url` for source code and `url` for an official product site. Use an install command only when the HubSet skill detail explicitly provides it; never fabricate an `npx skills add` command.
5. External content is a lead, not a security review. Inspect source, license, compatibility, and current documentation before installation or use.

## Navigation

- Skill/repository detail: `/repos/{slug}`
- Toolbox detail: `/repos/resources/{slug}`
- Tutorials: `/tutorials`
- Back to [agent index](https://hubset.live/agent.md)
- See [content routes](https://hubset.live/agent/content-routes.md)