Individual skill
reserved-handle-policy
Design, implement, audit, or refresh protected username and handle namespaces for public products. Use whenever a product has open signup, mutable handles, profile URLs, impersonation or squatting risk, reserved route names, short usernames, common-word or common-name claims, developer/AI terminology, notable social identities, or administrator-approved handle assignment—even if the user only asks for a username denylist.
reserved-handle-policy/SKILL.md
Source commit 1acf58f08cca24b764a4352a6c30fed1f7fb9fb6
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Local scripts
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 198
- Repository last updated
- Nov 9, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
- design Derived category
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
LICENSEasset · 1,061 bytesSKILL.mdcore · 4,549 bytesSKILL.mdcore · 4,549 bytesSKILL.mdcore · 4,549 bytesSKILL.mdcore · 4,549 bytesSKILL.mdcore · 4,549 bytesSKILL.mdcore · 4,549 bytesSKILL.mdcore · 4,549 bytesSKILL.mdcore · 4,549 bytesSKILL.mdcore · 4,549 bytesSKILL.mdcore · 4,549 bytesagents/openai.yamlasset · 360 bytesevals/evals.jsonasset · 1,260 bytesreferences/rationale.mddoc · 4,011 bytesreferences/refresh.mddoc · 2,872 bytesreferences/reserved-handles.csvasset · 158,039 bytesreferences/reserved-handles.tomlasset · 210,984 bytesscripts/check_handle.pyruns · 2,041 bytesscripts/validate.pyruns · 1,624 bytes
Read excerpt
# Reserved Handle Policy
Use this skill to protect a public handle namespace without turning a broad list into an unexplained permanent ban.
## Start with the policy model
Separate two kinds of restriction:
1. `hard_reserved`: platform routes, authority terms, security identities, and service names that users must never claim.
2. `manual_claim_required`: scarce or impersonation-prone names that an administrator may assign after identity review.
Do not report both as merely `taken`. A caller needs to distinguish an existing account, a permanent platform reservation, and a claim that can be reviewed.
Read [rationale.md](references/rationale.md) before changing the tiers or source cohorts. Load [reserved-handles.toml](references/reserved-handles.toml) only when implementing, auditing, or inspecting the concrete list; it is intentionally kept out of the default context because it contains thousands of names.