kai-test-account-reset
Skill40 starsChanged 4 days agoApache-2.0View on GitHub
Use when resetting a Kai/UAT test account by email for end-to-end onboarding, vault, RIA, consent, or profile retesting.
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hushh-webapp/AGENTS.mdAGENTS.md
- impeccableSkill
- agent-orchestration-governanceSkill
- analytics-observability-governanceSkill
- animateSkill
- animation-vocabularySkill
- apple-designSkill
- autonomous-rca-governanceSkill
- backend-agents-operonsSkill
- backend-api-contractsSkill
- backend-runtime-governanceSkill
- backendSkill
- brandkitSkill
- client-env-paritySkill
- codex-skill-authoringSkill
- comms-communitySkill
- context-refreshSkill
- contributor-onboardingSkill
- docs-governanceSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- founder-brief-curationSkill
- frontend-architectureSkill
- frontend-cache-coherenceSkill
- frontend-design-systemSkill
- frontend-native-surface-mapperSkill
- frontendSkill
- frontend-surface-placementSkill
- future-plannerSkill
- github-contribution-governanceSkill
- hushh-consent-mcpSkill
- hushh-icon-themeSkill
- iam-consent-governanceSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- improve-animationsSkill
- industrial-brutalist-uiSkill
- less-text-karma-jiSkill
- mcp-developer-surfaceSkill
- mobile-nativeSkill
- mobile-parity-auditSkill
- mobile-plugin-contractsSkill
- morphy-axSkill
- one-voice-governanceSkill
- oss-license-governanceSkill
- pdf-artifact-generationSkill
- pick-ui-librarySkill
- pkm-upgrade-rehearsalSkill
- planning-boardSkill
- pr-governance-reviewSkill
- profile-uiSkill
- prototypeSkill
- puppy-one-harnessSkill
- quality-contractsSkill
- release-ios-appstoreSkill
- repo-contextSkill
- repo-operationsSkill
- review-animationsSkill
- reviewer-app-testingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Avoid overlap with security-audit, iam-consent-governance, and repo-operations.
- Distinctive: line 52
Run a dry run first:
- Very specific: line 57
Add --include-counts only when row counts are needed.
- Distinctive: line 58
Ask for action-time confirmation before deletion, naming the email, environment, and data classes.
- Distinctive: line 63
Verify canonical erasure and remaining UID/email-linked rows.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Kai Test Account Reset Skill
Purpose and Trigger
- Primary scope:
kai-test-account-reset - Trigger on requests to delete or reset a Kai test user, especially when the user provides an email and wants to retest onboarding end to end.
- Avoid overlap with
security-audit,iam-consent-governance, andrepo-operations.
Coverage and Ownership
- Role:
spoke - Owner family:
security-audit
Owned repo surfaces:
.agents/skills/kai-test-account-reset
Non-owned surfaces:
security-auditsecurity-auditiam-consent-governancerepo-operationsbackend
Do Use
- UAT-backed test-account erasure where the email is explicitly supplied by the user; this is not same-UID delete/recreate repair.
- Dry-run discovery of Firebase UID shadows, actor profile rows, vault/PKM/RIA/consent rows, and email-linked developer/invite rows.
- Operator-side cleanup that must remain separate from the user-facing account deletion UI.
Do Not Use
- Production account deletion.
- Deleting accounts without an explicit user-authored email and action-time confirmation.
- Bypassing the in-app
profile.delete_accountvault-owner flow for normal user-initiated deletion. - Firebase Auth account deletion or browser-local storage deletion unless explicitly scoped and confirmed.
Read First
consent-protocol/api/routes/account.pyconsent-protocol/hushh_mcp/services/account_service.pydocs/architecture/finance/kai-action-gateway-vnext.md
Workflow
- Run a dry run first:
python3 .agents/skills/kai-test-account-reset/scripts/reset_kai_test_account.py --email <email> - Report the matched UID preview and planned cleanup scope without printing secrets.
Add
--include-countsonly when row counts are needed; it can be slow on large UAT tables. - Ask for action-time confirmation before deletion, naming the email, environment, and data classes.
- Execute only after confirmation:
python3 .agents/skills/kai-test-account-reset/scripts/reset_kai_test_account.py --email <email> --execute --confirm-email <email> - Verify canonical erasure and remaining UID/email-linked rows. Never bulk-delete discovered rows outside the owning retention policy or continue cleanup after a failed transaction.
- The helper attests the connected UAT database and exact Firebase-bound owner; it preserves Firebase, external provider grants, and a minimal resurrection-suppression hash. Existing external-cleanup intents fail closed. An erased UID cannot recreate its UAT account; use a different authorized test account. Firebase/browser erasure requires a separately scoped workflow.
Handoff Rules
- Route schema or account-deletion-service gaps to
iam-consent-governanceorsecurity-audit. - Route backend runtime/proxy failures to
repo-operations. - Route user-facing One Voice/search action changes to
one-voice-governance.
Required Checks
python3 .agents/skills/kai-test-account-reset/scripts/reset_kai_test_account.py --help
python3 -m py_compile .agents/skills/kai-test-account-reset/scripts/reset_kai_test_account.py
python3 .agents/skills/codex-skill-authoring/scripts/skill_lint.pyDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

