Auth

What this skill does

The Auth skill helps marketers and product teams understand and select the appropriate authentication pattern based on their application’s needs. It clarifies when to use JWT, session-based auth, OAuth 2.0, API keys, or emerging methods like passkeys. This ensures secure, scalable user access and integration flows tailored to your platform’s architecture and user experience goals.

Who it's for

This skill is designed for growth leads managing multi-channel platforms who must balance security with user convenience. It suits performance marketers overseeing web and API integrations requiring secure third-party access. Agency strategists recommending authentication approaches for client projects will also find it valuable for aligning tech choices with marketing objectives.

Key workflows

First, identify your application type—whether you’re running traditional web sessions or stateless microservices—and match that to a fitting auth pattern. Next, evaluate your integration needs: OAuth 2.0 is ideal for third-party user access, while API keys suit server-to-server communication. Then, apply best practices such as verifying JWT signatures and managing token expiry to maintain security. Finally, stay informed about emerging options like passkeys for passwordless authentication starting in 2025.

Common questions

Which auth pattern should I use for simple web applications? Session-based authentication is typically best for straightforward, traditional web apps. How do I ensure JWT tokens remain secure? Always verify the signature, check expiration, and avoid storing sensitive data inside JWTs. When is OAuth 2.0 preferable over API keys? Use OAuth 2.0 when third-party user authorization is required, and API keys when authenticating server-to-server or public API access.

How to use in Metaflow

Attach the Auth skill to any agent task where authentication design decisions are involved, such as API integration or user access flows. The skill will guide you through selecting the right pattern based on your use case and highlight important security considerations. This makes it easier to document and communicate auth choices within your team and stakeholders.

For broader context, see our roundup of marketing skills claude, and read Claude Code workflows for marketing agencies for related setup guidance.