user-identification

Derive a deterministic machine ID and hardware fingerprint for Electron app licensing.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/0xHarbs/agent-setup --skill user-identification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-identification
Source: https://github.com/0xHarbs/agent-setup/tree/main/claude/skills/domain/user-identification
Command: npx skills add https://github.com/0xHarbs/agent-setup --skill user-identification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Desktop applications often struggle with licensing, device fraud, and offline usage enforcement. This Skill provides deterministic device identity, machine-level license binding, and a scalable lifecycle to manage trials, tiers, and paywalls for Electron apps.

Core Features & Use Cases

  • Hardware UUID retrieval and deterministic machine ID generation to bind licenses to a device.
  • Server-backed license lifecycle including trials, tiered plans, and offline grace support with secure storage and auditing.
  • Client-side credential storage, usage events, and paywall gating to manage access and monetization.

Quick Start

Initialize the device license flow on first run to request a 30-day trial for your Electron app.

Frequently Asked Questions about user-identification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement device-based licensing in an Electron app?

To implement device licensing, you derive a deterministic machine ID using hardware fingerprinting, then manage trials, tiered plans, and offline grace periods through server-backed checks and client-side state.

What is hardware fingerprinting and how does it work for desktop paywalls?

Hardware fingerprinting generates a deterministic machine ID by retrieving hardware UUIDs, binding desktop licenses to specific devices to enforce paywalls and prevent device fraud.

Can I enforce offline license grace periods for Electron applications?

Yes, offline grace periods are supported by caching machine IDs and managing client-side state, allowing Electron apps to function temporarily without continuous server-backed license validation.

How do I manage tiered licensing and trial periods for desktop software?

Tiered licensing and trials are managed through a server-backed store that handles usage events and auditable license lifecycles, gating client-side access via paywalls based on the device fingerprint.

Does this device licensing approach store credentials locally on the client machine?

Yes, the device licensing approach includes client-side credential storage and machine ID caching to maintain secure access and manage usage events between server-backed validations.