replit-install-auth
Configures .replit files, secrets management, and user authentication for Replit applications.
Install
mkdir -p .claude/skills/replit-install-auth && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9436" && unzip -o skill.zip -d .claude/skills/replit-install-auth && rm skill.zipInstalls to .claude/skills/replit-install-auth
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Set up a Replit project with .replit + replit.nix configuration, Secrets,Key capabilities
- →Configure .replit and replit.nix files
- →Manage AES-256 encrypted environment secrets
- →Integrate user authentication via Google, GitHub, Apple, X, or Email
- →Set up project entrypoints and run commands
How it works
It automates the creation of environment configuration files and provides middleware code snippets to parse Replit-injected authentication headers.
Inputs & outputs
When to use replit-install-auth
- →Initialize a new Replit project with Nix packages
- →Securely add environment variables using Replit Secrets
- →Integrate user authentication flows
- →Configure project run behavior and entrypoints
About this skill
Replit Install & Auth
Overview
Set up a Replit App from scratch: configure .replit and replit.nix, manage Secrets (AES-256 encrypted environment variables), and integrate Replit Auth for zero-setup user authentication with Google, GitHub, Apple, X, and Email login.
Prerequisites
- Replit account (Free, Core, or Teams plan)
- Replit App created from template, GitHub import, or blank
- For Auth: deployed app on
.replit.appor custom domain
Instructions
Step 1: Configure .replit File
# .replit — controls run behavior, deployment, and environment
entrypoint = "index.ts"
run = "npm start"
# Nix modules provide language runtimes
modules = ["nodejs-20:v8-20230920-bd784b9"]
[nix]
channel = "stable-24_05"
[env]
NODE_ENV = "development"
PORT = "3000"
[deployment]
run = ["sh", "-c", "npm start"]
deploymentTarget = "autoscale"
build = ["sh", "-c", "npm run build"]
ignorePorts = [3001]
[unitTest]
language = "nodejs"
[packager]
language = "nodejs"
[packager.features]
packageSearch = true
guessImports = true
[gitHubImport]
requiredFiles = [".replit", "replit.nix"]
Step 2: Configure replit.nix
# replit.nix — system-level dependencies via Nix
{ pkgs }: {
deps = [
pkgs.nodejs-20_x
pkgs.nodePackages.typescript-language-server
pkgs.nodePackages.pnpm
pkgs.postgresql
pkgs.python311
pkgs.python311Packages.pip
];
}
After editing replit.nix, reload the shell for changes to take effect.
Step 3: Configure Secrets
Secrets are encrypted with AES-256 at rest and TLS in transit. Two scopes:
- App-level: specific to one Replit App
- Account-level: shared across all your Apps
Via UI:
1. Click the lock icon (Secrets) in the left sidebar
2. Add key-value pairs:
- DATABASE_URL = postgresql://...
- API_KEY = sk-...
- JWT_SECRET = your-jwt-secret
Via code — validate at startup:
// src/config.ts
function requireSecrets(keys: string[]): Record<string, string> {
const missing = keys.filter(k => !process.env[k]);
if (missing.length > 0) {
console.error(`Missing secrets: ${missing.join(', ')}`);
console.error('Add them in the Secrets tab (lock icon in sidebar)');
process.exit(1);
}
return Object.fromEntries(keys.map(k => [k, process.env[k]!]));
}
const config = requireSecrets(['DATABASE_URL', 'JWT_SECRET']);
Secrets sync automatically between Workspace and Deployments. Replit's Secret Scanner warns if you paste API keys directly into code files.
Step 4: Add Replit Auth
Replit Auth provides zero-setup authentication. Users log in with Google, GitHub, Apple, X, or Email. Replit handles sessions via cookies, password resets, and user management.
Express.js integration:
// src/auth.ts
import express from 'express';
const app = express();
// Replit Auth injects these headers on authenticated requests
interface ReplitUser {
id: string; // X-Replit-User-Id
name: string; // X-Replit-User-Name
bio: string; // X-Replit-User-Bio
url: string; // X-Replit-User-Url
image: string; // X-Replit-User-Profile-Image
roles: string; // X-Replit-User-Roles
teams: string; // X-Replit-User-Teams
}
function getReplitUser(req: express.Request): ReplitUser | null {
const id = req.headers['x-replit-user-id'] as string;
if (!id) return null;
return {
id,
name: req.headers['x-replit-user-name'] as string,
bio: req.headers['x-replit-user-bio'] as string,
url: req.headers['x-replit-user-url'] as string,
image: req.headers['x-replit-user-profile-image'] as string,
roles: req.headers['x-replit-user-roles'] as string,
teams: req.headers['x-replit-user-teams'] as string,
};
}
// Auth middleware
function requireAuth(req: express.Request, res: express.Response, next: express.NextFunction) {
const user = getReplitUser(req);
if (!user) return res.status(401).json({ error: 'Not authenticated' });
(req as any).user = user;
next();
}
// Client-side: GET /__replauthuser returns current user info
// Login: direct user to Replit's login page for your app
Flask integration:
from flask import Flask, request, jsonify
app = Flask(__name__)
def get_replit_user():
user_id = request.headers.get('X-Replit-User-Id')
if not user_id:
return None
return {
'id': user_id,
'name': request.headers.get('X-Replit-User-Name', ''),
'roles': request.headers.get('X-Replit-User-Roles', ''),
'teams': request.headers.get('X-Replit-User-Teams', ''),
'image': request.headers.get('X-Replit-User-Profile-Image', ''),
}
@app.route('/api/profile')
def profile():
user = get_replit_user()
if not user:
return jsonify({'error': 'Not authenticated'}), 401
return jsonify(user)
Step 5: Verify Setup
// test-setup.ts — run to verify everything works
const checks = {
nix: process.version, // should show Node version
secrets: !!process.env.DATABASE_URL,
replSlug: process.env.REPL_SLUG,
replOwner: process.env.REPL_OWNER,
replId: process.env.REPL_ID,
};
console.log('Replit Setup Verification:', checks);
Built-in environment variables available in every Repl:
| Variable | Description |
|---|---|
REPL_SLUG | Your Repl's name/slug |
REPL_OWNER | Owner username |
REPL_ID | Unique Repl identifier |
REPL_IDENTITY | PASETO token signed by Replit infra |
REPLIT_DB_URL | Key-value database endpoint |
Error Handling
| Error | Cause | Solution |
|---|---|---|
Module not found | Nix package missing | Add to replit.nix deps, reload shell |
EACCES permission | Wrong file permissions | Check .replit run command syntax |
Secret undefined | Not set in Secrets tab | Add via sidebar lock icon |
| Auth headers empty | Not deployed / local dev | Auth only works on deployed .replit.app URLs |
channel not found | Invalid Nix channel | Use stable-24_05 or check Nix channels list |
Resources
Next Steps
Proceed to replit-hello-world for a working starter app, or replit-deploy-integration to deploy.
When not to use it
- →When attempting to use authentication headers in a local development environment
Prerequisites
Limitations
- →Auth headers only function on deployed .replit.app URLs
How it compares
This automates the boilerplate configuration for Nix dependencies and auth headers that would otherwise require manual file editing and header parsing.
Compared to similar skills
replit-install-auth side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| replit-install-auth (this skill) | 0 | 27d | Review | Beginner |
| supabase-developer | 95 | 7mo | Review | Intermediate |
| supabase-mcp-integration | 13 | 8mo | Review | Advanced |
| better-auth-best-practices | 18 | 6mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
supabase-developer
daffy0208
Build full-stack applications with Supabase (PostgreSQL, Auth, Storage, Real-time, Edge Functions). Use when implementing authentication, database design with RLS, file storage, real-time features, or serverless functions.
supabase-mcp-integration
manutej
Comprehensive Supabase integration covering authentication, database operations, realtime subscriptions, storage, and MCP server patterns for building production-ready backends with PostgreSQL, Auth, and real-time capabilities
better-auth-best-practices
novuhq
Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.
nextjs-supabase-auth
davila7
Expert integration of Supabase Auth with Next.js App Router Use when: supabase auth next, authentication next.js, login supabase, auth middleware, protected route.
better-auth
mrgoonie
Implement authentication and authorization with Better Auth - a framework-agnostic TypeScript authentication framework. Features include email/password authentication with verification, OAuth providers (Google, GitHub, Discord, etc.), two-factor authentication (TOTP, SMS), passkeys/WebAuthn support, session management, role-based access control (RBAC), rate limiting, and database adapters. Use when adding authentication to applications, implementing OAuth flows, setting up 2FA/MFA, managing user sessions, configuring authorization rules, or building secure authentication systems for web applications.
auth-patterns
davepoon
This skill should be used when the user asks about "authentication in Next.js", "NextAuth", "Auth.js", "middleware auth", "protected routes", "session management", "JWT", "login flow", or needs guidance on implementing authentication and authorization in Next.js applications.