10x Cli Setup
Install or fix @przeprogramowani/10x-cli and align it with your AI editor after 10xDevs enrollment without guessing outdated install steps.
Overview
10x-cli-setup is an agent skill for the Build phase that installs and configures @przeprogramowani/10x-cli by following the live GitHub README.
Install
npx skills add https://github.com/przeprogramowani/10x-cli --skill 10x-cli-setupWhat is this skill?
- Treats the live GitHub README as the single source of truth instead of hardcoded install steps
- Runs `10x --version` first to skip redundant installs when only reconfigure or troubleshoot is needed
- Covers install, update, re-auth, npm/permission errors, and per-tool configuration
- Explicitly excludes developing or contributing to 10x-cli source
Adoption & trust: 1.6k installs on skills.sh; 31 GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You enrolled in 10xDevs or switched AI tools but do not trust static chat advice for installing and authenticating 10x-cli.
Who is it for?
New or returning 10xDevs students who need 10x-cli on macOS/Linux/Windows with Cursor, Copilot, or Claude Code.
Skip if: Contributing to 10x-cli itself, cloning the repo to extend it, or unrelated project bootstrap without the 10xDevs CLI.
When should I use this skill?
User mentions 10x-cli, @przeprogramowani/10x-cli, 10xDevs CLI, or course environment setup (install, update, reconfigure, auth, npm errors)—not 10x-cli development.
What do I get? / Deliverables
10x-cli is installed or updated, configured for your AI client, and auth or npm issues are resolved using current upstream instructions.
- Working `10x --version` output
- AI-tool configuration per README
- Resolved auth or install errors
Recommended Skills
Journey fit
Canonical shelf is Build because the skill’s job is standing up course tooling and agent-facing CLI configuration before day-to-day coding work. Agent-tooling fits best: it wires 10x-cli into Cursor, Copilot, and Claude Code rather than shipping product features.
How it compares
Use for course CLI onboarding; use generic dev environment skills when you are not on the 10xDevs toolchain.
Common Questions / FAQ
Who is 10x-cli-setup for?
Solo and indie builders in the 10xDevs ecosystem who need the official CLI installed and pointed at their AI coding tool.
When should I use 10x-cli-setup?
At Build/agent-tooling when you first install 10x-cli, after an update, when reconfiguring for Cursor or Claude Code, or when npm permissions or authentication fail.
Is 10x-cli-setup safe to install?
Review the Security Audits panel on this Prism page and verify you are fetching README and packages from the official @przeprogramowani sources before running shell commands.
SKILL.md
READMESKILL.md - 10x Cli Setup
# 10x-cli Setup This skill sets up the `@przeprogramowani/10x-cli` on the user's machine. The core principle is simple: **the README is the single source of truth**. The CLI evolves — version requirements change, new install methods appear, commands get updated. Rather than hardcoding any of that here, this skill tells you *how to work*, and the README tells you *what to do*. ## Step 1: Check if the CLI is already installed Before anything else, check the current state: ```bash 10x --version 2>/dev/null || echo "NOT_INSTALLED" ``` - If a version is printed, the CLI is already installed. Tell the user and ask if they want to update, reconfigure, or troubleshoot. - If not installed, proceed to Step 2. This avoids wasting time on prerequisites when the user might just need a config change or re-auth. ## Step 2: Fetch the latest README Retrieve the current README from GitHub — this is the authoritative source for all install steps, prerequisites, commands, and tool configurations: ``` URL: https://raw.githubusercontent.com/przeprogramowani/10x-cli/refs/heads/master/README.md ``` Use WebFetch or `curl -sL` to get it. If the fetch fails, tell the user and stop — don't guess at install steps from memory, because they may be outdated. ## Step 3: Build a plan from the README and execute it Read the fetched README and construct a step-by-step setup plan from it. The README contains everything needed: prerequisites, install commands, auth flow, available commands, and tool-specific configuration. Your job is to translate the README into actionable steps for the user's specific situation. The general flow from the README is: 1. **Prerequisites** — whatever the README says is required (runtime version, package manager, etc.). Check each one and stop if something is missing. 2. **Install** — use the install method described in the README. Verify it worked. 3. **Authenticate** — the README describes the auth command and flow. Note: auth is interactive (magic-link email), so the user may need to run it themselves via `! 10x auth` if the shell doesn't support input. 4. **Verify** — the README lists a diagnostic command. Run it and review the output with the user. 5. **Explore** — show the user how to browse and fetch content using the commands from the README. 6. **Tool configuration** — if the user mentioned a specific AI tool (Claude Code, Cursor, etc.), use the README's multi-tool support section to configure it. If not, explain the options and let them choose. Do not hardcode specific version numbers, command flags, or directory paths — read them from the README. This way the skill stays correct even when the CLI changes. ## Important principles - **README over memory.** If you think you know a command or requirement, but the fetched README says something different, follow the README. Always. - **Check before installing.** Step 1 exists for a reason — don't reinstall what's already there. - **Be interactive.** Confirm with the user before installing global packages or modifying their system. Ask before running `sudo`. - **Diagnose before fixing.** If something fails, read the error and the README's guidance before suggesting a fix. Don't just retry blindly. - **Stay focused on end-user setup.** This skill is about installing and configuring the published CLI package, not about development/contributing workflows.