gts-auth

Manage T3K passwordless OAuth and API-key JWT authentication for the Guitar Tone Shootout platform.

Updated Feb 2, 2026

Search Tags:#security #authentication #api #oauth #jwt #session management

Ready to run

npx skills add https://github.com/krazyuniks/guitar-tone-shootout --skill gts-auth

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gts-auth
Source: https://github.com/krazyuniks/guitar-tone-shootout/tree/main/.claude/skills/gts-auth
Command: npx skills add https://github.com/krazyuniks/guitar-tone-shootout --skill gts-auth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines and secures the authentication process for the Guitar Tone Shootout platform, ensuring robust user login, session management, and API security.

Core Features & Use Cases

Passwordless OAuth: Enables secure webapp login via T3K's OAuth flow.
API Key Authentication: Manages JWT authentication for source synchronization.
Session Management: Handles session cookies, CSRF protection, and security headers.
Shared Auth: Allows authentication credentials to be shared across worktrees via a secure file.
API Separation: Differentiates between User and Admin API access controls.
Use Case: When a new user signs up or logs in, this skill handles the T3K OAuth redirect, token exchange, and secure storage, making their session persistent across different work sessions.

Quick Start

Use the gts-auth skill to log in to the T3K OAuth provider.

Frequently Asked Questions about gts-auth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I implement passwordless OAuth for webapp login?▼

Passwordless OAuth for webapp login is implemented via the T3K OAuth provider flow, handling the secure redirect, token exchange, and persistent session storage without requiring user passwords.

How does JWT API key authentication work for source synchronization?▼

JWT API key authentication secures source synchronization by issuing tokens that validate API access requests, ensuring only authorized sources can sync data with the platform.

What is the best way to manage session cookies and CSRF protection?▼

Session cookies and CSRF protection are managed by enforcing secure cookie attributes and validating anti-forgery tokens, ensuring persistent and secure user sessions across different work sessions.

Can I share authentication credentials across multiple worktrees?▼

Yes, authentication credentials can be shared across worktrees via a secure cross-worktree auth file, allowing consistent authenticated access without requiring separate logins for each worktree.

How do I separate User and Admin API access controls?▼

User and Admin API access controls are separated by defining distinct authentication and authorization rules for each API tier, ensuring administrative endpoints require elevated privileges compared to standard user APIs.