open source is social v-it.org
Add vit skill skeleton and skills authoring guide
Create skills/vit/SKILL.md with YAML frontmatter and skeleton body
documenting vit CLI usage, subcommands, core workflow, terminology,
and configuration. Add Skills section to CLAUDE.md with link to
Claude agent skills best practices and key authoring guidelines.
+83
+10
CLAUDE.md
+10
CLAUDE.md
···
45
45
```
46
46
47
47
Add this header to `.js` files in `bin/` and `src/`. Do not add headers to docs/, node_modules/, or non-source files.
48
+
49
+
## Skills
50
+
51
+
Agent skills for this project live in `skills/`. When authoring or updating skills, follow the [Claude agent skills best practices](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices):
52
+
53
+
- Keep SKILL.md concise — under 500 lines. Only add context Claude doesn't already have.
54
+
- Use progressive disclosure: essentials inline, details in referenced files one level deep.
55
+
- Use gerund or action-oriented naming (lowercase-hyphens only) for skill names.
56
+
- Write descriptions in third person that specify both what the skill does and when to use it.
57
+
- Test with all target models (Haiku, Sonnet, Opus) as effectiveness varies.
+73
skills/vit/SKILL.md
+73
skills/vit/SKILL.md
···
1
+
---
2
+
name: using-vit
3
+
description: Operates the vit CLI for DID:PLC identity management and ATProto social collaboration. Use when working with beacons, caps, vetting, vouching, remixing, or shipping in a vit project.
4
+
---
5
+
6
+
# vit CLI
7
+
8
+
CLI toolkit for DID:PLC operations and Bluesky OAuth.
9
+
10
+
## Quick start
11
+
12
+
```bash
13
+
bun install # install dependencies
14
+
vit init # check environment and configure vit
15
+
vit oauth --handle alice.bsky.social # authenticate with Bluesky
16
+
```
17
+
18
+
## Subcommands
19
+
20
+
| Command | Purpose |
21
+
|---------|---------|
22
+
| `vit init` | Check environment readiness, configure vit for first use |
23
+
| `vit setup` | Initialize user-level config |
24
+
| `vit doctor` | Check vit setup status (alias for init) |
25
+
| `vit oauth --handle <h>` | Browser-based ATProto OAuth, saves tokens to .env |
26
+
| `vit config [action]` | Read/write vit.json config (list, set, delete) |
27
+
| `vit plc-register` | Generate and register a DID:PLC genesis operation |
28
+
| `vit plc-verify` | Verify DID document and audit log from PLC directory |
29
+
| `vit firehose` | Listen to Bluesky Jetstream for custom record events |
30
+
| `vit pds-record` | Write/read org.v-it records on authenticated PDS |
31
+
32
+
For full option details, see [README.md](../../README.md).
33
+
34
+
## Core workflow
35
+
36
+
Setup (one-time):
37
+
38
+
```bash
39
+
vit init
40
+
vit adopt <beacon>
41
+
```
42
+
43
+
Typical flow:
44
+
45
+
```bash
46
+
vit skim # read caps from followed agents and beacon
47
+
vit vet <cap> # run local evaluation, generate evidence
48
+
vit remix <cap> # derive vetted cap into local codebase, create plan
49
+
vit ship # publish new cap to beacon
50
+
```
51
+
52
+
Endorsement path:
53
+
54
+
```bash
55
+
vit vet <cap>
56
+
vit vouch <cap> # publicly endorse a vetted cap
57
+
```
58
+
59
+
A cap must be vetted before it can be remixed or vouched.
60
+
61
+
## Terminology
62
+
63
+
Key terms: **beacon** (canonical project identity), **cap** (structured change record), **remix** (local derivative of a cap), **evidence** (proof artifacts from vetting), **provenance** (lineage chain).
64
+
65
+
Key verbs: **init**, **adopt**, **follow**, **skim**, **vet**, **vouch**, **remix**, **ship**.
66
+
67
+
For complete definitions, see [VOCAB.md](../../VOCAB.md).
68
+
69
+
## Configuration
70
+
71
+
- **`.vit/`** — local project directory, stores beacon and follows
72
+
- **`.env`** — credentials (`BSKY_DID`, `BSKY_ACCESS_TOKEN`, etc.), written by `vit oauth`
73
+
- **`vit config`** — read/write `vit.json` user-level config