mikhailbahdashych

Hardware Assets Inventory Tool — Development skill for Claude Code

Development community

Self-hosted hardware asset inventory for IT teams — track devices, who holds them, and the full ownership history.

How to install Hardware Assets Inventory Tool

This entry records only its repository, not the path inside it, so there is no exact command to give. Open mikhailbahdashych/hardware-assets-inventory-tool and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Hardware Assets Inventory Tool does

Self-hosted hardware asset inventory for IT teams — track devices, who holds them, and the full ownership history. TypeScript monorepo: React + Vite, Fastify + SQLite. Every area ships a CLAUDE.md so you customize it by asking Claude Code.

Alternatives in Development

  • Epic Claim — Claim an epic issue, stamp coordination state, and sync local ownership 243.5k ★
  • Happy Coder — by GrocerPublishAgent - Spawn and control multiple Claude Codes in parallel from your phone or desktop 15.7k ★
  • Microsandbox — Open-source self-hosted MicroVM sandboxes with sub-200ms startup, hardware-level isolation via libkrun 5k ★

README

Inventory — hardware asset tracking for IT teams

Self-hosted, MIT licensed, and small enough that the whole install is one container over one directory: track devices, who holds them, and the full ownership history of every one. Every setting has a default, so an instance with no configuration at all runs and its first screen creates your organization — and when one machine stops being enough, `DATABASE_URL` moves the rows to PostgreSQL and `S3_BUCKET` moves the attachments to a bucket, without changing anything else about the app.

Table of contents

What it is

  • Assets — tag, name, category, serial, status, purchase, warranty, supplier, notes, attachments and any custom fields you define. Filters live in the URL, so a filtered view is a link you can send someone.
  • Employees — the people who hold devices. Separate from the accounts that sign in, optionally linked to them, because most staff never need a login.
  • Ownership history — who had what, when, and how it came back. Held in one table that is the only truth about it; an asset's status and its open ownership record cannot disagree.
  • Custom statuses and workflow — the statuses an asset can be in are yours, not ours: an admin adds, renames, recolours and reorders them, and draws the moves between them as a checkbox matrix with a live diagram beside it. The API enforces the graph, so taking an edge off it stops that move being offered and stops it being accepted.
  • **Custom roles an