Projects

Agentic OS — Force-Directed Map of a 387-Skill Claude Code Setup

Active
Next.js 16React 19TypeScriptreact-force-graph-2dframer-motionTailwind CSS 4
Product demo

Problem

An agent setup grows one plugin at a time until it has hundreds of skills, and nobody can see what it actually contains. There is no view of which skills overlap, which clusters are overweight, or which ones were hand-written versus pulled in by a marketplace plugin.

Business Impact

Teams adopting agent tooling install skills and plugins faster than they can audit them, then wonder why the agent picks the wrong one. Agentic OS turns an invisible capability surface into a picture you can point at in a review — what exists, what clusters together, and what nobody wrote on purpose.

System Approach

  • Next.js 16 App Router client shell with search, cluster filters, detail panel, and colour map
  • Canvas force simulation via react-force-graph-2d handling physics, render, and camera
  • generate-skills.mjs walks personal and plugin skills, parses SKILL.md front-matter, writes data/skills.json
  • api/graph route reshapes the snapshot into nodes plus links at build time
  • framer-motion for panel and overlay motion

Key Decisions & Trade-offs

  • Commit the snapshot rather than scan at runtime — a deployed build cannot read a local skills directory
  • Canvas over SVG — 387 nodes with live physics would stall a DOM-based renderer
  • White ring for hand-made skills — the authored-versus-installed split is the one distinction worth encoding visually
  • Cluster colours over per-skill colours so 34 categories stay readable at a glance

Current Status

Public and open source at github.com/rohitguta2432/agentic-os. Full galaxy renders from a committed 387-skill snapshot with search, cluster filtering, and a per-skill detail panel; npm run skills rebuilds the snapshot from any machine.

Roadmap

  • Diff mode to compare two skill snapshots over time
  • Overlap detection to flag skills with near-identical trigger descriptions
  • Usage weighting so frequently-invoked skills render larger

What I'd Improve Next

  • A hosted demo seeded with a public sample snapshot so visitors need no local setup
  • Export the current view as a shareable static image for reviews and posts

Explore More