by jaredrhod
Move things on your screen with your bare hands. A webcam-powered, hand-tracked interface for your AI. No headset. No controllers.
# Add to your Claude Code skills
git clone https://github.com/jaredrhod/barehandsGuides for using api integration skills like barehands.
Last scanned: 8/17/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-08-17T04:42:36.693Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}barehands is an open-source api integration skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by jaredrhod. Move things on your screen with your bare hands. A webcam-powered, hand-tracked interface for your AI. No headset. No controllers. It has 925 GitHub stars.
Yes. barehands passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/jaredrhod/barehands" and add it to your Claude Code skills directory (see the Installation section above).
barehands is primarily written in HTML. It is open-source under jaredrhod on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other API Integration skills you can browse and compare side by side. Open the API Integration category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh barehands against similar tools.
No comments yet. Be the first to share your thoughts!
Top skills in this category by stars
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Never used Claude Code? Start at jaredrhod.com: pick your situation and it routes you to the right path.
Runs on: a webcam and Chrome; works with any AI. Any program that writes a file or curls localhost can be its brain.
Move things on your screen with your bare hands. barehands turns your webcam into a hand-tracked interface: notes, images, and 3D models float over your camera as glass cards. You pinch them, throw them, stretch them, force-pull them across the room, and blow an engine apart into its exploded view with a drag of two fingers. No headset. No controllers. No gloves. Bare hands.
And it's a body waiting for a brain: wire in your AI and the on-screen ring becomes its face, while two small scripts give it hands and eyes on your board. Free to use, change, and build on, including commercially inside your own business, and if you pass your version on it stays open under the same license (see LICENSE).
Watch it in action:
git clone https://github.com/jaredrhod/barehands
cd barehands
python3 server.py
On Windows run run.bat instead: a clean Windows 11 has no Python but leaves a Microsoft Store stub on the PATH that looks like one, and run.bat finds an interpreter that actually works. Open http://127.0.0.1:8794/stage.html in Chrome, allow the camera, and wave. That's the whole install: the server is stdlib Python, and the page loads its hand tracking (Google MediaPipe) and 3D (three.js) from CDNs on first run.
Already in a Claude Code session with your agent? One sentence does it all: "clone https://github.com/jaredrhod/barehands.git, then read barehands/barehands.md and set me up." Your agent installs it, configures it, and wires itself in.
Tap the ring → orbs bloom → tap an orb → your files unfold on glass. The sample notes teach the gestures from inside the board itself.
The "vault" on the board is just a folder of markdown, which means an Obsidian vault works as-is, and so does any folder of .md files. Point an orb at it in barehands.json:
{
"name": "Assistant",
"orbs": [
{ "title": "Notes", "path": "~/MyVault", "kind": "notes" },
{ "title": "Props", "path": "media", "kind": "media" }
]
}
One line per orb. Add more folders, rename them, point them anywhere. The media orb is the props airlock: drop images in media/misc/, transparent props in media/fx/, 3D models in media/models/, or in media/holo/, where the same model renders as a blue hologram wireframe. Only files inside media/ can ever appear on the board; that jail is a safety feature.
The easy way: open the repo in Claude Code and say "read barehands.md and set me up." The setup wizard interviews you, writes the config, and wires your assistant in end to end.
The manual way: barehands speaks two dead-simple protocols:
state/: write thinking (or idle / listening / speaking) to state/state and the ring reacts. No files, no problem: it idles beautifully. Claude Code users: two hooks in settings.json make the ring mirror your real sessions (the wizard pastes them for you).bin/board.sh '{"a":"present","title":"THE PLAN","body":"..."}' and the thing flies center stage, enlarged and spotlit, everything else dimmed: that's the show-me verb, for when you ask your AI to put something up. add_card, add_img, hand, explode, yank, hover stage the ensemble pieces; the server enforces an action allowlist and the media jail, so it's safe to hand to an assistant. bin/board-state.sh is the reverse: it prints what's on the board, so your AI can look before it talks. The wizard teaches your assistant to reach for the glass whenever you ask to SEE something instead of answering in text.Anything that can write a file or curl localhost can be the brain: Claude, a local LLM, a cron job, a Stream Deck button.
If your assistant doesn't have a memory yet, pair this with ai-memory-vault; the vault it builds becomes a notes orb on this board.
Tap (quick pinch) opens and closes. Pinch-drag moves. Hold still while carrying to rotate in 3D. Two hands scale. Flick to throw. Clap (palms together, fingers up) sweeps the board clean. The claw: flash your hand open, claw, aim at something across the screen, let it strain and shake for two seconds, then snap the claw shut, and it rips through the air into your hand. An empty pinch dragged sideways scrubs a 3D model's exploded view apart and back together.
Every threshold was tuned on a real hand across weeks of live use, and because the gates measure hand shape as ratios, not size, they hold at any camera distance. The full cheat sheet is on the board: Getting Started → The Gestures. If a gesture ever misfires for your hand or setup, TROUBLESHOOTING.md ships the tuning clinic: the built-in debug overlay and pose sampler, plus the exact method for your AI to fit the gates to your hand.
Two pages, one scene: the tracker page owns your camera; stage.html?role=render is a truly transparent mirror of it, built for an OBS browser source: the glass composites over your camera feed with real alpha. &cursors=0 hides the finger rings (bare-hands sorcery), &ss=2 renders at 2× for razor-sharp cards, and ?portrait=1 on the tracker flips the whole rig to vertical 9:16 for Shorts and TikTok. ?res=3840x2160 bumps the tracker's capture for a 4K self-view (1280x720 rescues slow machines); in an OBS rig your broadcast camera is OBS's own source, so tracking happily stays at the default. Details in the sample notes' Field Guide.
Hand tracking by Google MediaPipe (Apache 2.0). 3D rendering by three.js (MIT). Both load from public CDNs; this repo redistributes neither.
barehands improves continuously, and gesture fixes ship often. To update on macOS, double-click the Update icon setup left on your Desktop, or run ./update.sh in this folder. On Windows, or any time, say "pull the latest barehands and tell me what changed" to your agent — it does the same job. Your config, your notes, and your media stay untouched: they live outside the tracked files. Installed through fullstack-agent? ./fullstack-agent/update.sh (macOS) updates every piece at once and prints what changed.
A board is better with an agent behind it. Give it a voice and you can talk while you move things around, and a memory vault turns the notes orb into your agent's actual brain instead of a folder of files.
Free to use, and always will be. If this helped you out, you can buy me a coffee:
Copyright (c) 2026 Jared Rhodenizer.
Licensed under the GNU Affero General Public License, version 3 or later (AGPL-3.0-or-later). Use it in your business, commercially, for free. Run it, change it, build your workflow on top of it, and charge for the work you do with it. The one rule is that it stays open: if you hand it to someone else, or run a modified version as a service other people use, your version ships under this same license with its source available. Credit me when you build on it. Want it inside a closed-source commercial product? Email license@jaredrhod.com. Full terms are in the LICENSE file and at https://www.gnu.org/licenses/agpl-3.0.html