One-click install
npx skills add https://github.com/binary16labs/prime-silo --skill admin-users-binary16labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Admin Users
Source: https://github.com/binary16labs/prime-silo/tree/main/app/L0/_admin/mod/_core/overlay_agent/ext/skills/admin-user-management/users
Command: npx skills add https://github.com/binary16labs/prime-silo --skill admin-users-binary16labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage admin user accounts—creating users, updating profile metadata, resetting SCRAM password verifiers, and revoking sessions—without breaking the logical L2 storage structure or membership expectations.

Core Features & Use Cases

  • Create users with canonical storage layout: Writes the user logical root, user module root, user.yaml metadata, sealed SCRAM verifier, and session verifier file.
  • Update user profile metadata: Reads and updates user.yaml fields like full_name while keeping paths logical and consistent.
  • Reset passwords and revoke sessions correctly: Generates a fresh verifier via password_generate, overwrites meta/password.json, and clears logins.json with {} to revoke sessions.
  • Remove users and handle downstream memberships: Deletes the user root directory and, when needed, updates group configs so the user disappears from manager/member lists.

Quick Start

Create an admin-capable user by instructing the skill to create user account storage under L2/<username>/, initialize user.yaml with full_name, generate a sealed verifier for the chosen password, and write an empty logins.json to the user’s meta directory.

Frequently Asked Questions about Admin Users

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

FAQPage Schema
How do I reset a user password using SCRAM verifiers without breaking the storage structure?

To reset a user password using SCRAM verifiers, you must generate a fresh sealed verifier via password_generate, overwrite the existing meta/password.json file, and clear meta/logins.json with {} to revoke active sessions. This ensures the logical L2 storage structure remains intact.

What is the canonical storage layout for creating admin user accounts?

The canonical storage layout for admin user accounts requires writing the user logical root at L2/<username>/, initializing user.yaml metadata with fields like full_name, generating a sealed SCRAM verifier, and writing an empty logins.json to the user's meta directory.

How do I revoke user sessions and update group memberships when removing an admin account?

To revoke sessions and remove an admin account, delete the user root directory under L2/<username>/ and update group configurations so the user disappears from manager and member lists. Session revocation also requires clearing the meta/logins.json file.

How do I update user profile metadata like full_name in YAML format?

Updating user profile metadata involves reading and updating user.yaml fields such as full_name. You must ensure all paths remain logical and consistent within the L2/<username>/ storage tree to maintain canonical path rules.

Why should I use password_generate instead of hand-crafting SCRAM verifiers for user management?

Using password_generate instead of hand-crafting SCRAM verifiers ensures correct structured JSON payloads and prevents corruption of meta/password.json. Hand-crafting verifiers or session entries risks breaking the logical L2 storage structure and membership expectations.

Can I manage admin user accounts without dependencies or external components?

Yes, you can manage admin user accounts without dependencies or external components. The workflow operates entirely on the logical L2/<username>/ storage tree using file system APIs to manage meta/password.json and meta/logins.json files.