← ClaudeAtlas

qalamlist-ops-companionlisted

Use when working in the QalamList repo and the user asks to deploy, install prerequisites, check setup, run locally, configure Cloudflare, D1, Turnstile, secrets, Wrangler, diagnose deploy errors, or get QalamList running. Use for phrases like "deploy this", "doctor", "prerequisites", "publish", "setup", or "run locally".
qalamio/qalamlist-skills · ★ 0 · AI & Automation · score 68
Install: claude install-skill qalamio/qalamlist-skills
# QalamList Ops Companion ## Core Principle Help QalamList customers get running without surprising them. Read-only checks are fine; installs, file edits, Cloudflare mutations, remote D1 commands, secrets, and deploys need explicit approval. This is a customer-facing skill. Explain required tools and Cloudflare resources in one clear sentence or short paragraph before asking to act. ## First Move 1. Confirm the current directory is the QalamList repo by checking for `package.json`, `wrangler.jsonc.example`, `deploy.sh`, and `src/index.ts`. 2. Route the request to one workflow: `prerequisites`, `doctor`, `local`, or `deploy`. 3. If the request is ambiguous, choose the safest workflow: - "check", "why failing", "doctor", "validate" -> `doctor` - "install", "requirements", "setup tools" -> `prerequisites` - "run locally", "dev server", "test locally" -> `local` - "deploy", "publish", "production", "Cloudflare" -> `deploy` ## Approval Gate Before running any command that installs software, edits files, writes secrets, creates Cloudflare resources, applies any remote migration, or deploys, state: - What is missing or changing. - Why QalamList needs it. - The exact command. - Whether it affects only the local machine or Cloudflare/production. Then ask for approval and wait. If the tool environment has an approval mechanism, use it. If not, ask in chat. Read-only diagnostics do not need approval unless they may expose secrets. Never print secret values. ## Tro