open source is social v-it.org
docs: add skills-only path to getting started tutorial
Restructures the getting started page so users who only want skills
can follow steps 1-3, hit a path fork, and jump straight to a
self-contained skills section — no git repo or beacon needed.
Three edits:
- Prerequisites now note git is only needed for caps
- Path fork after step 3 routes skills-only users to #skills
- Skills section rewritten as standalone entry point (browse → vet → learn)
Note: run `make deploy-site` to publish these changes.
+18
-5
+18
-5
docs/start/index.html
+18
-5
docs/start/index.html
···
290
290
291
291
<h2>what you need</h2>
292
292
<ul>
293
-
<li><strong><a href="https://nodejs.org">Node.js</a> 20.10+</strong> and <strong>git</strong></li>
293
+
<li><strong><a href="https://nodejs.org">Node.js</a> 20+</strong></li>
294
+
<li><strong>git</strong> — only needed if you plan to ship caps (skills work without it)</li>
294
295
<li><strong>a <a href="https://bsky.app">Bluesky</a> account</strong> — vit publishes to your identity on the <a href="https://atproto.com">AT Protocol</a></li>
295
296
<li><strong>a coding agent</strong> — <a href="https://claude.ai/code">Claude Code</a>, <a href="https://github.com/openai/codex">Codex CLI</a>, or <a href="https://github.com/google-gemini/gemini-cli">Gemini CLI</a></li>
296
297
</ul>
···
315
316
<li><code>jeremie.com</code> — vit's creator, ships capabilities and skills regularly</li>
316
317
</ul>
317
318
<p>use <code>vit scan</code> to discover more publishers — it replays recent network activity and shows who's shipping.</p>
319
+
320
+
<p><strong>where to next?</strong></p>
321
+
<ul>
322
+
<li><strong>skills only</strong> — no git repo needed. run <code>vit skim --skills</code> and <a href="#skills">skip to the skills section</a>.</li>
323
+
<li><strong>caps</strong> — continue to step 4. you'll need a git repo with a beacon.</li>
324
+
</ul>
318
325
319
326
<hr>
320
327
···
357
364
358
365
<hr>
359
366
360
-
<h2>skills</h2>
361
-
<p>capabilities are project-scoped improvements. <strong>skills</strong> are different — they're reusable agent abilities that work across any project. think npm for AI agent skills.</p>
367
+
<h2 id="skills">skills</h2>
368
+
<p>skills are reusable agent abilities that work anywhere — no git repo, no beacon, no project setup needed. if you completed steps 1–3 above, you're ready to go.</p>
362
369
370
+
<h3>browse skills</h3>
363
371
<span class="cmd-label">your agent runs this</span>
364
372
<pre><code>vit skim --skills</code></pre>
365
-
<p>browse skills on the network. when you find one you want:</p>
373
+
<p>browse skills from publishers you follow.</p>
374
+
375
+
<h3>vet before you trust</h3>
366
376
<span class="cmd-label">you run this (terminal)</span>
367
377
<pre><code>vit vet skill-agent-test-patterns</code></pre>
378
+
<p>evaluate a skill in a sandbox before learning it. vetting is always your call.</p>
379
+
380
+
<h3>learn a skill</h3>
368
381
<span class="cmd-label">your agent runs this</span>
369
382
<pre><code>vit learn skill-agent-test-patterns</code></pre>
370
-
<p>skills install to <code>.claude/skills/</code> in your project, or <code>~/.claude/skills/</code> with <code>--user</code> for global use. they follow the <a href="https://agentskills.io">Agent Skills</a> open standard.</p>
383
+
<p><code>vit learn</code> saves the skill to <code>.claude/skills/</code> in your current project, or use <code>--user</code> for global access across all projects. skills follow the <a href="https://agentskills.io">Agent Skills</a> open standard.</p>
371
384
372
385
<hr>
373
386