personal/skills/auth/SKILL.md
Implements authentication, OAuth, sessions, payments, and billing. Use when adding auth flows, route protection, RBAC, or payment webhooks.
npx skillsauth add tim-hub/powerball authInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A collection of skills responsible for implementing authentication and payment features.
| Feature | Details | |---------|--------| | Authentication | See references/authentication.md | | Payments | See references/payments.md |
Authentication and payment features always carry high security risk. Always display the following before starting work:
🔐 Security Checklist
This work is security-critical. Please verify the following:
### Authentication
- [ ] Passwords are hashed (bcrypt/argon2)
- [ ] Session management is secure (HTTPOnly Cookie)
- [ ] CSRF protection is implemented
- [ ] Rate limiting (brute-force protection)
### Payments
- [ ] Sensitive information (card numbers, etc.) is not stored on the server
- [ ] Stripe/payment provider SDK is used correctly
- [ ] Webhook signature verification
- [ ] Amount tampering prevention (amounts finalized server-side)
### Common
- [ ] Error messages are not too detailed (prevent information leakage)
- [ ] Sensitive information is not logged
⚠️ Severity Level: 🔴 High
This feature carries the following risks:
- Credential leakage
- Unauthorized access
- Fraudulent payment operations
Expert review is recommended.
🔐 Building Login & Payment Features Safely
1. **Hash passwords**
- Store passwords in an irreversible form
- Data remains safe even if it leaks
2. **Do not store card information on your server**
- Delegate to dedicated services like Stripe
- Store nothing on your own server
3. **Keep error messages vague**
- Use "Authentication failed" instead of "Wrong password"
- Do not give hints to malicious actors
testing
Picks the right Kubernetes Deployment update strategy (RollingUpdate / Recreate / Blue-Green / Canary) for the situation. Use when configuring a new Deployment, changing rollout config, or deciding how to ship a risky change.
tools
Translates a markdown file to a target language, preserving structure. Use when the user needs a markdown file translated.
development
Translates text between any two languages while preserving source format. Use when the user needs to translate plain text, code, or markdown content.
testing
Generates written content — blog posts, social posts, emails, and marketing copy — matched to the project's existing voice. Use when the user needs written material.