New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Lathe Verify

by devenjarvis in devenjarvis/lathe

Verify that a stored Lathe tutorial actually works by following it end to end in a fresh scratch dir, in session.

MITAuto-check passed

Install Lathe Verify

skills CLI
$ npx skills add devenjarvis/lathe --skill lathe-verify -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install devenjarvis/lathe lathe-verify --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/devenjarvis/lathe.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/lathe-verify .claude/skills/lathe-verify && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
lathe-verify
GitHub stars
1.7k
Token cost
~844 tokens
SKILL.md length
412 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Verify that a stored Lathe tutorial actually works by following it end to end in a fresh scratch dir, in session.

  • Works in 5 steps: Mark it in-flight first → Make a fresh scratch dir and work there → Follow each part in order. Read… → …
  • SKILL.md covers Protocol and Boundaries
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Lathe Verify is an agent skill from devenjarvis/lathe. Verify that a stored Lathe tutorial actually works by following it end to end in a fresh scratch dir, in session. Use when the user invokes /lathe-verify with a slug like "/lathe-verify digital-synth-zig" (the "Verify this tutorial" button in lathe serve hands you that command).

Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Generate hands-on, multi-part technical tutorials on demand, with LLM skills tuned to make content approachable. Then you work through them yourself, by hand ✋. The licence is MIT.

Example prompts

  • “/lathe-verify digital-synth-zig”
  • “Verify this tutorial”
  • “/lathe-verify”

Requirements

  • Docker

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Mark it in-flight first
  2. Make a fresh scratch dir and work there
  3. Follow each part in order. Read ~/.lathe/tutorials//part-NN.md from part-01 up. Install the prerequisites, create the files and paste the…
  4. Record the terminal result with the matching command
  5. Report to the user what happened — verified clean, skipped (and which tool was missing), or where exactly it failed.

What it can do on your machine

Read from SKILL.md and the folder at commit 1e7c9f6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Lathe Verify loads about 844 tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 412 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~74
When it runs · the whole SKILL.md, loaded when a task matches
~844

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from devenjarvis/lathe at commit 1e7c9f6, republished under its MIT licence (© devenjarvis). 412 words, ~844 tokens.

Download SKILL.mdSave it as .claude/skills/lathe-verify/SKILL.md (or your agent's skills folder).
name
lathe-verify
description
Verify that a stored Lathe tutorial actually works by following it end to end in a fresh scratch dir, in session. Use when the user invokes /lathe-verify with a slug like "/lathe-verify digital-synth-zig" (the "Verify this tutorial" button in `lathe serve` hands you that command).

Lathe — Verify a Tutorial

Follow a stored tutorial exactly as a reader would, in a throwaway directory, and record whether it actually works. Triggered by /lathe-verify <slug>. Isolation is by instruction — a fresh mktemp -d, under the user's normal interactive permissions. No sandbox-exec, no Docker.

This skill is read-only with respect to the tutorial: never edit the parts or the metadata. The only writes are status updates through lathe verify-result.

Protocol

  1. Mark it in-flight first:

    bash
    lathe verify-result <slug> --status verifying

    This sets the spinner badge in the web UI. If it errors with "cannot verify while it is extending", stop — a part is mid-flight; don't verify on top of it.

  2. Make a fresh scratch dir and work there:

    bash
    cd "$(mktemp -d)"

    Everything the tutorial tells the reader to create happens here, not in the user's project. (Status is set by this skill, never by the web/CLI button — so an unclicked button can never strand a tutorial at verifying.)

  3. Follow each part in order. Read ~/.lathe/tutorials/<slug>/part-NN.md from part-01 up. Install the prerequisites, create the files and paste the code blocks exactly as written, in order, then run the ## Checkpoint command and compare against the stated expected output.

    • Skip the pedagogical and provenance callouts — > [!PREDICT], > [!RECALL], and > [!UNVERIFIED] are not verifiable steps. They prompt the reader or flag uncertainty; there's nothing to execute.
    • Treat the Checkpoint commands and code blocks as the executable surface.

  4. Record the terminal result with the matching command:

    • Everything works → lathe verify-result <slug> --status verified
    • A required tool isn't installed → lathe verify-result <slug> --status skipped This is not a failure — it's the ⚠️ Skipped badge, meaning "couldn't run it here," not "the tutorial is wrong." Use it whenever the toolchain the tutorial needs (compiler, runtime, SDK) is missing locally.
    • Something genuinely breaks (wrong output, code doesn't compile, a step contradicts itself) →
      bash
      lathe verify-result <slug> --status failed \
  --part <part-NN.md> \
  --failed-step <1-indexed step number within that part> \
  --error "<the error message or mismatched output>"

  5. Report to the user what happened — verified clean, skipped (and which tool was missing), or where exactly it failed.

Show full SKILL.md (72 more words)Show less

Boundaries

  • Read-only on the tutorial. Never edit a part-NN.md, metadata.json, or verify-result.json directly — the only state writes are via lathe verify-result.
  • No OS sandboxing. Isolation is the mktemp -d scratch dir plus instruction, under the user's normal permission model. Don't reach for sandbox-exec or Docker.
  • Skipped ≠ failed. A missing toolchain is skipped. Reserve failed for the tutorial being genuinely broken.
  • Status is always set by this skill, never by the handoff button.

© devenjarvis, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/lathe-verify of devenjarvis/lathe.

Open the folder on GitHubat commit 1e7c9f6

Compare with similar skills

Lathe Verify next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Lathe Verify compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lathe Verify this skilldevenjarvis/lathe1.7k—~844Automated safety check: PassMIT
Agent App Storeruvnet/ruflo74k2 repos~1kAutomated safety check: PassMIT
App Store Optimizationalirezarezvani/claude-skills28k1 repos~4.2kAutomated safety check: PassMIT
Eas App Storessickn33/agentic-awesome-skills47k1 repos~1.9kAutomated safety check: PassMIT
App Store Changelogsickn33/agentic-awesome-skills47k2 repos~831Automated safety check: PassMIT
Microsoft Store Publishergithub/awesome-copilot40k—~3.8kAutomated safety check: PassMIT

Similar skills

  • Agent App Store

    ruvnet/ruflo

    Agent skill for app-store - invoke with $agent-app-store. An agent skill from ruvnet/ruflo.

    74k GitHub starsUsed in 2 repos~1k tokens
    MobileAuto-check passed

  • App Store Optimization

    alirezarezvani/claude-skills

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.

    28k GitHub starsUsed in 1 repo~4.2k tokens
    Marketing & SEOAuto-check passed

  • Eas App Stores

    sickn33/agentic-awesome-skills

    Curated upstream guidance for Eas App Stores; use when the workflow matches the user goal.

    47k GitHub starsUsed in 1 repo~1.9k tokens
    MobileAuto-check passed

  • App Store Changelog

    sickn33/agentic-awesome-skills

    Generate user-facing App Store release notes from git history since the last tag.

    47k GitHub starsUsed in 2 repos~831 tokens
    DevelopmentAuto-check passed

  • Microsoft Store Publisher

    github/awesome-copilot

    Official

    Takes a Windows desktop app through MSIX packaging, WACK validation and a Partner Center submission with the Microsoft Store, with strict confirmation safeguards for risky steps.

    40k GitHub stars~3.8k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

  • Tutorial

    Q00/ouroboros

    Interactive tutorial teaching Ouroboros hands-on. An agent skill from Q00/ouroboros.

    6.2k GitHub stars~1.6k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed

More from devenjarvis/lathe

  • Lathe Ask

    devenjarvis/lathe

    Answer a reader's question about a specific part of a Lathe tutorial, in session.

    1.7k GitHub stars~532 tokensUpdated 2 mo ago
    Auto-check passed

  • Lathe Extend

    devenjarvis/lathe

    Write the next part of an existing Lathe tutorial, in session.

    1.7k GitHub stars~1.4k tokensUpdated 2 mo ago
    Auto-check passed

  • Lathe Tag

    devenjarvis/lathe

    Pick or backfill the search tags on a stored Lathe tutorial, in session.

    1.7k GitHub stars~466 tokensUpdated 2 mo ago
    Auto-check passed

  • Lathe Voice

    devenjarvis/lathe

    Author a custom writing voice for Lathe tutorials, in session, then persist it via the CLI.

    1.7k GitHub stars~1.3k tokensUpdated 2 mo ago
    Auto-check passed

  • Lathe Work

    devenjarvis/lathe

    Run the Lathe worker loop so the web UI's Ask / Verify / Add-a-part buttons drive work directly in this session instead of handing back a command to paste.

    1.7k GitHub stars~1.7k tokensUpdated 2 mo ago
    Auto-check passed

  • Lathe

    devenjarvis/lathe

    Generate hands-on technical tutorials for any topic on demand.

    1.7k GitHub stars~7.2k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Lathe Verify

What does Lathe Verify do?

Verify that a stored Lathe tutorial actually works by following it end to end in a fresh scratch dir, in session. Lathe Verify is an agent skill from devenjarvis/lathe. Verify that a stored Lathe tutorial actually works by following it end to end in a fresh scratch dir, in session.

How do I install Lathe Verify in Claude Code?

Run `npx skills add devenjarvis/lathe --skill lathe-verify -a claude-code`. Or copy the skill folder (.claude/skills/lathe-verify in devenjarvis/lathe) into .claude/skills/lathe-verify in your project. Claude Code loads it when a task matches its description.

How do I install Lathe Verify in Codex?

Run `npx skills add devenjarvis/lathe --skill lathe-verify -a codex`. Or copy the skill folder (.claude/skills/lathe-verify in devenjarvis/lathe) into .agents/skills/lathe-verify in your project. Codex loads it when a task matches its description.

Can I use Lathe Verify in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add devenjarvis/lathe --skill lathe-verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lathe-verify, .gemini/skills/lathe-verify, .github/skills/lathe-verify and .opencode/skills/lathe-verify in your project.

What does Lathe Verify need to run?

SKILL.md names no scripts, command-line tools or credentials: Lathe Verify is instructions for the agent only. Our summary lists: Docker.

Does Lathe Verify access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Lathe Verify safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Lathe Verify use?

Lathe Verify is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lathe Verify use?

About 844 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Lathe Verify?

Skills that share tags, products or a category with Lathe Verify: Agent App Store (ruvnet/ruflo, 74k stars), App Store Optimization (alirezarezvani/claude-skills, 28k stars), Eas App Stores (sickn33/agentic-awesome-skills, 47k stars) and App Store Changelog (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lathe Verify?

devenjarvis (a GitHub user) maintains it in devenjarvis/lathe, which has 1,686 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on August 3, 2026.

Source: devenjarvis/lathe on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.