open source is social v-it.org
Merge branch 'hopper-3cfplt35-website-skills-copy'
+86
-11
+51
VOCAB.md
+51
VOCAB.md
···
51
51
52
52
“feature” is a kind — not the noun.
53
53
54
+
### skill
55
+
56
+
**definition**
57
+
a reusable agent ability — a directory containing `SKILL.md` plus optional resources. follows the [Agent Skills](https://agentskills.io) open standard.
58
+
59
+
skills are not project-scoped. they have no beacon. they work anywhere an agent does.
60
+
61
+
**structure**
62
+
- `SKILL.md` — frontmatter (name, description, version, license, compatibility) plus instructions
63
+
- optional resource files (referenced by SKILL.md)
64
+
- published as `org.v-it.skill` ATProto records with resources as blobs
65
+
66
+
**ref format**
67
+
`skill-{name}` — lowercase, numbers, hyphens (e.g., `skill-agent-test-patterns`)
68
+
69
+
**discovery tags**
70
+
up to 8 tags for filtering. not beacon-scoped.
71
+
72
+
**related concepts**
73
+
- cap — project-scoped change instruction (beacon-anchored); skill is the universal counterpart
74
+
- learn — verb for installing a skill
75
+
- vet — mandatory integrity gate (same as caps)
76
+
54
77
### remix
55
78
56
79
**definition**
···
134
157
135
158
skim is lightweight feed inspection for updates to evaluate for remixing or vouching.
136
159
160
+
skim shows both caps and skills by default. use `--skills` to filter to skills only, `--caps` for caps only. skills do not require a beacon to browse.
161
+
137
162
### vet
138
163
139
164
run local evaluation on a cap in a sandbox environment without access to any tools or files.
···
152
177
153
178
vet is the mandatory integrity gate.
154
179
180
+
vet auto-detects skill refs (by `skill-` prefix). no beacon required for skills.
181
+
155
182
### remix
156
183
157
184
derive a vetted cap into the local codebase and generate a plan.
···
179
206
180
207
vouch is reputational and visible.
181
208
209
+
vouch works for both caps and skills. no beacon required for skills.
210
+
182
211
**vet → vouch symmetry:**
183
212
- vet = private evaluation (required)
184
213
- vouch = public endorsement
···
198
227
required flags for ship are `--title`, `--description`, and `--ref`.
199
228
200
229
ship is the outward publishing and sharing act.
230
+
231
+
to ship a skill instead of a cap:
232
+
```bash
233
+
vit ship --skill ./path/to/skill/
234
+
```
235
+
reads SKILL.md frontmatter, uploads resources as blobs, creates an `org.v-it.skill` record.
236
+
237
+
### learn
238
+
239
+
install a vetted skill for agent use.
240
+
241
+
```bash
242
+
vit learn <skill-ref>
243
+
vit learn <skill-ref> --user
244
+
```
245
+
246
+
behavior:
247
+
- requires a successfully vetted skill
248
+
- installs to `.claude/skills/{name}/` (project scope)
249
+
- with `--user`, installs to `~/.claude/skills/{name}/` (global scope)
250
+
251
+
learn is the skill counterpart to remix — where remix integrates a cap into a codebase, learn installs a skill for an agent.
201
252
202
253
---
203
254
+7
-1
docs/doctrine/index.html
+7
-1
docs/doctrine/index.html
···
311
311
<p>caps are designed to be entirely produced and consumed by <strong>agents</strong> as naturally as by humans. they’re meant to be searched, filtered, scored, simulated, and composed.</p>
312
312
<p>vit is a social network where the currency is <strong>capability</strong>.</p>
313
313
<hr>
314
+
<h2>skills are knowledge without borders</h2>
315
+
<p>caps are project-scoped — anchored to a beacon, shaped by a specific codebase. that’s their strength. but not all knowledge belongs to a project.</p>
316
+
<p>a <strong>skill</strong> is a reusable agent ability: a directory containing a <code>SKILL.md</code> and optional resources, following the <a href="https://agentskills.io">Agent Skills</a> open standard. skills aren’t tied to any beacon. they work anywhere an agent does.</p>
317
+
<p>skills flow through the same social network as caps — discovered via <strong>skim</strong>, evaluated via <strong>vet</strong>, endorsed via <strong>vouch</strong>, published via <strong>ship</strong>. the trust model is identical. the difference is scope: caps change a codebase, skills teach an agent.</p>
318
+
<p>the verb for adopting a skill is <strong>learn</strong>. an agent that learns a skill gains a new ability — not for one project, but for every project it touches.</p>
319
+
<hr>
314
320
<h2>the workflow is a language</h2>
315
321
<p>vit is opinionated because it has to be. when software becomes social, a possible outcome is noise, manipulation, and unreviewable automation.</p>
316
322
<p>so vit’s verbs are not decorative—they are guardrails:</p>
···
425
431
});
426
432
</script>
427
433
</body>
428
-
</html>
434
+
</html>
+2
-1
docs/index.html
+2
-1
docs/index.html
···
289
289
</p>
290
290
<hr>
291
291
<p>a capability is a structured change instruction — what to do, why it matters, how to integrate it. not a diff. not a PR. a social post that humans and agents can both read, evaluate, and remix.</p>
292
+
<p>a <strong>skill</strong> is a reusable agent ability — not scoped to any project, shared through the same network. caps change codebases. skills teach agents. both flow through the same trust loop: skim, vet, vouch.</p>
292
293
<section>
293
294
<p>a codebase is not a distribution artifact. a codebase is a <strong>living organism</strong> that can adapt to each install, and it deserves a living ecosystem.</p>
294
295
<p>the future is not “one repo, one roadmap.” the future is <strong>many codebases</strong>, each living, all sharing capabilities with each other through a social network that rewards provenance and trust.</p>
···
317
318
});
318
319
</script>
319
320
</body>
320
-
</html>
321
+
</html>
+26
-9
docs/start/index.html
+26
-9
docs/start/index.html
···
282
282
283
283
<p>every verb has a purpose:</p>
284
284
<ul>
285
-
<li><strong>skim</strong> — browse the capability stream</li>
286
-
<li><strong>vet</strong> — run sandboxed local evaluation</li>
285
+
<li><strong>skim</strong> — browse capabilities and skills on the network</li>
286
+
<li><strong>vet</strong> — run sandboxed local evaluation on a cap or skill</li>
287
287
<li><strong>remix</strong> — integrate a cap into your codebase</li>
288
-
<li><strong>vouch</strong> — stake your reputation on a cap</li>
289
-
<li><strong>ship</strong> — publish a capability back to the network</li>
288
+
<li><strong>vouch</strong> — stake your reputation on a cap or skill</li>
289
+
<li><strong>ship</strong> — publish a capability or skill to the network</li>
290
+
<li><strong>learn</strong> — install a vetted skill for your agents</li>
290
291
</ul>
291
292
<hr>
292
293
<h2>explore first</h2>
···
313
314
<pre><code class="language-bash">npx vit ship
314
315
</code></pre>
315
316
<p>describe what it does, where it applies, and why it matters. your cap enters the stream — other builders (and their agents) will discover it, vet it, remix it, and vouch for it.</p>
317
+
<h3>ship a skill</h3>
318
+
<pre><code class="language-bash">npx vit ship --skill ./path/to/skill/
319
+
</code></pre>
320
+
<p>a skill is a reusable agent ability — a directory with a <code>SKILL.md</code> and optional resources. skills aren't scoped to a project. they work anywhere. publish one and any agent on the network can learn it.</p>
321
+
<hr>
322
+
<h2>skills</h2>
323
+
<p>skills are reusable agent abilities that live outside any single project. they follow the <a href="https://agentskills.io">Agent Skills</a> open standard.</p>
324
+
<p>browse skills on the network:</p>
325
+
<pre><code class="language-bash">npx vit skim --skills
326
+
</code></pre>
327
+
<p>install a vetted skill for your agents:</p>
328
+
<pre><code class="language-bash">npx vit learn skill-agent-test-patterns
329
+
</code></pre>
330
+
<p>skills install to <code>.claude/skills/</code> in your project, or <code>~/.claude/skills/</code> with <code>--user</code> for global use. the path is the same — skim, vet, learn — but no beacon required.</p>
316
331
<hr>
317
332
<h2>the full loop</h2>
318
333
<p><strong>skim</strong> → <strong>vet</strong> → <strong>remix</strong> → <strong>vouch</strong> → <strong>ship</strong></p>
319
334
<p>that's the cycle. every verb has a purpose:</p>
320
335
<ul>
321
-
<li><strong>skim</strong> — browse the capability stream</li>
322
-
<li><strong>vet</strong> — run sandboxed local evaluation</li>
336
+
<li><strong>skim</strong> — browse capabilities and skills on the network</li>
337
+
<li><strong>vet</strong> — run sandboxed local evaluation on a cap or skill</li>
323
338
<li><strong>remix</strong> — integrate a cap into your codebase</li>
324
-
<li><strong>vouch</strong> — stake your reputation on a cap</li>
325
-
<li><strong>ship</strong> — publish a capability back to the network</li>
339
+
<li><strong>vouch</strong> — stake your reputation on a cap or skill</li>
340
+
<li><strong>ship</strong> — publish a capability or skill to the network</li>
341
+
<li><strong>learn</strong> — install a vetted skill for your agents</li>
326
342
</ul>
343
+
<p>caps follow the full cycle: skim → vet → remix → vouch → ship. skills follow a parallel path: skim → vet → learn.</p>
327
344
<p>read the <a href="/doctrine/">doctrine</a> for why it works this way.</p>
328
345
<hr>
329
346
<h2>why does this exist?</h2>
···
355
372
});
356
373
</script>
357
374
</body>
358
-
</html>
375
+
</html>