setup
/setup
Guided SiftStack setup. Walks a person from a fresh install to working skills - picks the keys worth adding for the work they actually do, creates a .env from the bundled template, explains what each key costs and the free route without it, turns on plugin auto-update, and confirms with the doctor. Use when someone says "set up SiftStack", "help me configure the skills", "add my API keys", "get me started", "I just installed siftstack", or when the doctor shows blocked skills they want unblocked.
- Author
- datasift-ty-personal ↗
- Repository
- siftstack ↗
- Licence
- MIT
- Last repository change
- 21.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 21.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Guided SiftStack setup. Walks a person from a fresh install to working skills - picks the keys worth adding for the work they actually do, creates a .env from the bundled template, explains what each key costs and the free route without it, turns on plugin auto-update, and confirms with the doctor. Use when someone says "set up SiftStack", "help me configure the skills", "add my API keys", "get me started", "I just installed siftstack", or when the doctor shows blocked skills they want unblocked.
Triggers from the description
Original author description
Guided SiftStack setup. Walks a person from a fresh install to working skills - picks the keys worth adding for the work they actually do, creates a .env from the bundled template, explains what each key costs and the free route without it, turns on plugin auto-update, and confirms with the doctor. Use when someone says "set up SiftStack", "help me configure the skills", "add my API keys", "get me started", "I just installed siftstack", or when the doctor shows blocked skills they want unblocked.
How it works
- 1. See where they stand
- 2. Ask what they do, then pick keys for that
- 3. Create the .env
- 4. Turn on updates (Claude Code, one time)
- 5. Confirm
SKILL.md preview
---
name: setup
description: Guided SiftStack setup. Walks a person from a fresh install to working skills - picks the keys worth adding for the work they actually do, creates a .env from the bundled template, explains what each key costs and the free route without it, turns on plugin auto-update, and confirms with the doctor. Use when someone says "set up SiftStack", "help me configure the skills", "add my API keys", "get me started", "I just installed siftstack", or when the doctor shows blocked skills they want unblocked.
---
# SiftStack setup
Get someone from "installed" to "working" without making them buy anything they do not need.
## 1. See where they stand
Run the doctor first (`python "${CLAUDE_PLUGIN_ROOT}/scripts/doctor.py" --json`). Never start by listing keys.
## 2. Ask what they do, then pick keys for that
Ask what they want to get done this week. Map the answer to skills, and only then to keys. About half the library needs nothing at all, so many people are already done.
Every key is optional and every skill degrades instead of failing. Say the cost and the free route for each key before they decide:
- The cost and fallback for every package are in `${CLAUDE_PLUGIN_ROOT}/data/requires.json`.
- Where to get each key, in one line each, is in the comments of `${CLAUDE_PLUGIN_ROOT}/data/env.skills.example`.
## 3. Create the .env
Skills read environment variables, plus a `.env` in the folder Claude is working in.
- If there is no `.env` in the working folder, copy `${CLAUDE_PLUGIN_ROOT}/data/env.skills.example` to `.env` there.
- You MUST NOT overwrite an existing `.env`, because it may hold keys that exist nowhere else. Append only the missing variable names, empty.
- You MUST NOT ask the person to paste a key into the chat, and MUST NOT write a key value yourself, because anything typed here stays in the conversation history. Tell them which line to fill in and let them edit the file in their own editor.
- If the folder is a git repository, check that `.env` is ignored before they fill it in. If it is not, add it to `.gitignore` first.
People who use many folders can set the variables at the user level in their OS instead. Both work.
## 4. Turn on updates (Claude Code, one time)
Third-party marketplaces do not auto-update by default. Have them run `/plugin`, open **Marketplaces**, select **siftstack**, and choose **Enable auto-update**. Without it they stay on the version they installed until they run `/plugin marketplace update siftstack` by hand.
In Cowork, the Plugins page has an **Update** button on the marketplace.
If installing a bundle failed with `Unrecognized key: "dependencies"`, their Claude Code is too old for bundles. `claude update` fixes it.
## 5. Confirm
Run the doctor again and show what moved from blocked to working. Then suggest one concrete first task using a skill that is ready.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · datasift-ty-personal/siftstack | 100 | MIT |
| HwangSlater/harness-fit | 100 | MIT |
| nesquikm/dev-process-toolkit | 100 | MIT |
| userKael/rastro | 100 | MIT |
| als-apg/osprey | 100 | BSD-3-Clause |
| dedujeong/gemba | 100 | Apache-2.0 |
| eigenwise/eigenwise-toolshed | 100 | MIT |
| awrshift/agent-memory-kit | 100 | MIT |
| lifecycle-innovations-limited/claude-ops | 100 | MIT |
Database snapshot: 13.11.2026 · package version bfa34c1df7bd (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100doctor
SiftStack readiness check. Reports which installed SiftStack skills work right now, which need a login, which need an API key, what each key costs, and the no-API route to use instead. Use when someone asks "what can I run", "what do I need to set up", "why did that skill skip a… - 100env-vars
Manage environment variables and API keys in the sandbox. Use when the user asks to set, update, or manage environment variables, API keys, secrets, or credentials, or when you need to configure API keys or secrets for tools, scripts, or services you are running. - 100troubleshooting
Ralphy CLI operations and repair — environment setup, API keys and connectors, `ralphy doctor`, reading logs, diagnosing a failed generation or render, and the CLI cookbook for verbs other roles call. USE WHEN the user says "set this up", "set up my keys", "run ralphy doctor",… - 100sarmalink-setup
Use when setting up SarmaLink-AI for the first time, deploying to Vercel, configuring Supabase, adding API keys, or troubleshooting a fresh installation. Also use when someone says 'help me set up', 'deploy this', 'configure environment', or 'I just cloned this repo'. - 100doctor
Use when GodMode skills do not seem to trigger, when the user asks whether GodMode is installed or working, or after installing or updating the plugin on any harness - 90workflow-setup
Use when the user runs /workflow-setup or asks to set up, install or configure sams-agentic-workflow globally or for a project. "/workflow-setup" is the guided standard setup; "/workflow-setup full" lists every setting at the global and project layers to turn on or off. Also…