Burn After Login

Why it's ranked here

The concept targets a specific, recurring obstacle with a disciplined workflow. It validates prerequisites before editing, reuses the application’s authentication system, and requires production requests to receive a 404. The strongest value is not novel authentication code, but coordinated discovery, implementation, and documentation. Confidence is limited because the repository supplies instructions and examples rather than tests demonstrating the generated results across its many claimed stacks.

What's good

The workflow has sensible stop conditions for missing environment detection, authentication, or test users. Generated shortcuts call existing authentication machinery instead of introducing a separate identity path. Session and token flows receive distinct treatments. The skill also discovers configured browser tools and adds concrete authentication guidance for them. Self-removal requires user approval, while the generated shortcuts remain.

Tradeoffs

This is an instruction-driven skill, not a fixed implementation with predictable output across every framework. Results depend on the coding agent correctly interpreting each project’s authentication and development safeguards. Query parameters may carry credentials in login examples, despite the requirement not to log them. The supplied repository text shows no automated tests for production blocking, credential handling, generated routes, or cleanup.

How to use it well

Use it in an established application with reliable development-mode detection, working authentication, and dedicated test accounts. It fits teams whose browser agents repeatedly traverse login forms during local testing. Inspect the proposed endpoint or script and verify production returns 404 before relying on it. It does not create an authentication system or test users, and it does not replace broader browser automation setup.

Observed

License

MIT

Primary artifact

Agent Skills instruction document written in Markdown

Install surface

Installed with the skills CLI into a project’s agent skills directory

Interface

Agent Skill, including a Claude Code slash-command invocation

Supported project languages

Claims Node.js, Python, Ruby, Go, Rust, and additional languages

Authentication modes

Creates shortcuts for session-based authentication, token-based authentication, or both

Website stack

Private SvelteKit project using TypeScript, Svelte, and Vite

Tests

No test directory or automated test files appear in the supplied repository tree