itaywol/adeptability / .adeptability/staging/.claude/skills/expertise-exchange
expertise-exchange
VerifiedTeam expertise billboard via `adept exchange`: ask teammates for expertise and stack responses. Apply when the user wants a colleague's input, mentions the exchange, or when you start using adept — sample open requests and offer to answer ones the user knows about.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.7 KB |
| references/setup-and-usage.md | markdown | 3.5 KB |
references/setup-and-usage.md
View on GitHub# Exchange: full setup and usage reference
The expertise exchange is a self-hosted "billboard". One person hosts the
server on a host the team can reach; everyone else registers once and then
submits requests and posts responses. The server is **passive** — it only
stores requests, responses, statuses, and tokens. Agents participate purely by
running the CLI commands below.
## Concepts
- **Item** — one expertise request: id, author, title, body, optional
assignees and tags, a status, and a flat list of responses (comments).
- **Status** — lifecycle of an item:
- `attention-required` — open, needs answers (default for a new item)
- `in-progress` — has at least one response (set automatically on the first)
- `closed` — the author considers it resolved
- **Author owns the lifecycle** — anyone can respond, but only the author can
`close`/`reopen` an item. The first response from anyone auto-flips
`attention-required` → `in-progress`.
- **Assignee** — naming `--assignee <handle>` marks whose expertise you want;
the item is still visible to everyone. `list --mine` shows items you authored
or are assigned to.
## Hosting a server
```bash
adept exchange serve --addr :4639 --db fs --data /var/lib/adept-exchange
```
- On first run it mints a **bootstrap token** and prints it **once**. Share it
with teammates — they need it to `register`. It is not recoverable later;
rotate with `adept exchange serve --rotate-bootstrap` (invalidates the old
one, so re-distribute).
- `--db fs` persists to `<data>/board.json` (atomic write-through). `--db
memory` keeps everything in RAM (lost on restart) — useful for testing.
- `--data` defaults to `<library>/exchange-data` when omitted.
- Serve plain HTTP only on a **trusted/internal network**. To expose it,
terminate TLS at a reverse proxy in front of it. There is no in-process TLS.
- Stop with Ctrl-C (SIGINT/SIGTERM trigger a graceful shutdown).
## Registering (each teammate, once)
```bash
adept exchange register --server https://exchange.example.com --bootstrap <token> --handle alice
```
- `--handle` defaults to your OS username if omitted.
- The issued bearer token is stored at `~/.adeptability/exchange/<host>.json`
with mode `0600`. The server stores only a SHA-256 hash of it.
- The server URL is remembered as the default for later commands.
## Resolution order
- **Server**: `--server` flag → `$ADEPT_EXCHANGE_SERVER` → last registered.
- **Token**: `$ADEPT_EXCHANGE_TOKEN` → stored `<host>.json`.
This makes the commands work unattended in CI: set those two env vars.
## Daily commands
```bash
adept exchange list [--mine] [--status attention-required|in-progress|closed] --json
adept exchange show <id> --json
adept exchange submit --title "…" --body "…" [--assignee h]… [--tag t]…
adept exchange respond <id> --body "…"
adept exchange close <id>
adept exchange reopen <id>
adept exchange status --json # { server, registered, dismissed } — no network call
```
## Tokens
```bash
adept exchange token rotate # issues a new token; the old one stops working immediately
```
Rotate if a token leaks. The stored creds file is updated in place.
## The setup recommendation
The `expertise-exchange` skill prompts to set up an exchange when none is
configured. To silence that prompt per-user:
```bash
adept exchange recommendation dismiss # stop prompting
adept exchange recommendation undismiss # prompt again
```
Dismissal is stored at `~/.adeptability/exchange/recommendation-dismissed` and
applies across every project on this machine.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |