keyco
by @husamabdel
Manage Keyco assets, DUBs (QR/NFC/BLE/Virtual beacons), workflows, lifecycle events, users, and analytics. Use when the user asks about Keyco, asset manageme...
User: "What assets does alice@company.com have?"
β keyco user list --output json to find her user ID, then
β keyco user assigned-dubs --user-id
β Summarize: "Alice has N assets assigned: [list]"
User: "Create a maintenance event for DUB ee6f2f42-31b1-4f90-9440-e91fb02ac7c4 due next Friday"
β Compute the absolute date from "next Friday"
β keyco lifecycles create --event-type MAINTENANCE --name "Maintenance" --assigned-dub ee6f2f42-31b1-4f90-9440-e91fb02ac7c4 --due-date 2026-04-24
β Confirm creation to the user with the returned event ID
User: "Show me this week's analytics"
β keyco analytics weekly-digest --output json
β Summarize top-line metrics (total assets, active workflows, open lifecycle events, utilization %)
User: "Find any stale assets"
β keyco analytics stale-assets --output json
β Report the count and list the first few, offering to create maintenance events or reassign them
User: "Import 50 assets from this CSV"
β Explain that bulk CSV import goes through POST /api/imports/upload (not yet in CLI) β suggest they use the dashboard at https://dashboard.qrdub.com or loop over keyco lifecycles create / asset endpoints individually
Before running any command, verify the CLI is installed and configured:
1. Check if keyco is on PATH: which keyco
2. Check configuration: keyco status
3. If either check fails, run the setup script β it handles install + configure in one shot:
bash scripts/setup-keyco.sh
@keyco/cli globally via npm if missing (falling back to sudo npm if needed)
- Skip install if already present
- Walk the user through keyco configure if no valid API key is set
- Verify connectivity at the endAlways offer to run this script before failing β don't ask the user to manually install or configure.
clawhub install keyco