Production readiness agent auth
Skill scalekit-inc/skills/skills/production-readiness-agent-auth
35 skills that teach AI coding agents to integrate Scalekit auth — agent auth, full-stack login, MCP OAuth 2.1, enterprise SSO, and SCIM. Works with Claude Code, Cursor, Windsurf, and 35+ other agents.
npx -y skills add scalekit-inc/skills --skill production-readiness-agent-authAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Walks through a structured production readiness checklist for Scalekit agent authentication implementations. Use when the user says they are going live, launching to production, doing a pre-launch review, or wants to verify their agent OAuth implementation is production-ready.
SKILL.md
2.6 KB, as published. Nobody here has run it
Scalekit Agent Auth Production Readiness
Work through each section in order — earlier sections are blockers for later ones.
Quick checks (run first)
- Production environment URL, client ID, and client secret are set (not dev/staging values)
- HTTPS enforced on all auth endpoints
- API credentials stored in environment variables — never committed to code
- Redirect URIs registered in dashboard match exactly what the app sends
OAuth token flows
- Test authorization URL generation with correct scopes
- Validate
stateparameter in callbacks (CSRF protection) - Test authorization code exchange for access + refresh tokens
- Verify access tokens are stored securely (not in localStorage or logs)
- Test automatic token refresh before expiry
- Verify token refresh handles concurrent requests correctly (no race conditions)
- Test behavior when refresh token expires — user prompted to re-authorize
- Verify revocation on logout clears stored tokens
Per connected service:
- Test OAuth flow end-to-end for each service (Gmail, Slack, Notion, etc.)
- Verify correct scopes requested — request minimum required
- Test API calls with valid access token succeed
- Test API calls with expired token trigger refresh correctly
- Test behavior on permission denied (user revoked access in the third-party app)
Security
- Access tokens never logged or exposed in error messages
- Refresh tokens stored encrypted at rest
- Token storage scoped per user — no cross-user token access possible
- Webhook/callback endpoint validates signatures (if applicable)
Monitoring and incident readiness
- Auth logs monitoring configured in Dashboard > Auth Logs
- Error tracking configured for OAuth failures and token refresh errors
- Alerts configured for repeated authorization failures
- Log retention policies configured
- Incident response runbook written (who to contact, how to revoke compromised tokens)
Key metrics:
- Token refresh success/failure rate
- OAuth authorization completion rate (initiated vs completed)
- Per-service API error rates (distinguish auth errors from service errors)
- Token expiry distribution (are tokens being refreshed proactively?)
Gives 0 of the 12 instructions most context ai engineering skills give
Counted across 1,193 of the 1,976 authors here whose files we hold, read 2026-08-06
- dispatch a fresh implementer subagent per taskin 48 of 1193, across 19 files
- dispatch final reviewer after all tasksin 37 of 1193, across 11 files
- provide full task text to the subagentin 31 of 1193, across 10 files
- review spec compliance before code qualityin 27 of 1193, across 10 files
- make the hook script executablein 26 of 1193, across 8 files
- re-snapshot after navigation or DOM changesin 25 of 1193, across 17 files
- answer subagent questions before proceedingin 22 of 1193, across 7 files
- mark task complete in TodoWrite after approvalin 22 of 1193, across 6 files
- merge hook into existing settingsin 21 of 1193, across 3 files
- read files before editing themin 21 of 1193, across 9 files
- ask if installation is global or projectin 20 of 1193, across 2 files
- copy the hook script to target locationin 20 of 1193, across 2 files
Said here and by no other author read
- store api credentials in environment variables
- enforce https on all auth endpoints
- validate state parameter in callbacks
- request minimum required scopes per service
- encrypt refresh tokens at rest
- scope token storage per user
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.