From replit-pack
Install and configure Replit SDK/CLI authentication. Use when setting up a new Replit integration, configuring API keys, or initializing Replit in your project. Trigger with phrases like "install replit", "setup replit", "replit auth", "configure replit API key".
How this skill is triggered — by the user, by Claude, or both
Slash command
/replit-pack:replit-install-authThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Set up Replit SDK/CLI and configure authentication credentials.
Set up Replit SDK/CLI and configure authentication credentials.
set -euo pipefail
# Node.js
npm install @replit/sdk
# Python
pip install replit
# Set environment variable
export REPLIT_API_KEY="your-api-key"
# Or create .env file
echo 'REPLIT_API_KEY=your-api-key' >> .env
// Test connection code here
| Error | Cause | Solution |
|---|---|---|
| Invalid API Key | Incorrect or expired key | Verify key in Replit dashboard |
| Rate Limited | Exceeded quota | Check quota at https://docs.replit.com |
| Network Error | Firewall blocking | Ensure outbound HTTPS allowed |
| Module Not Found | Installation failed | Run npm install or pip install again |
import { ReplitClient } from '@replit/sdk';
const client = new ReplitClient({
apiKey: process.env.REPLIT_API_KEY,
});
from replit import ReplitClient
client = ReplitClient(
api_key=os.environ.get('REPLIT_API_KEY')
)
After successful auth, proceed to replit-hello-world for your first API call.
npx claudepluginhub aiminnovations/claude-code-plugins-plus --plugin replit-packGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026