Skip to content
Skills Library
AI & agents · Automation

install

/install

Run automated TeaRAGs install wizard from scratch — detects environment, installs deps (Node.js, tea-rags, Ollama/ONNX/llama-server, Qdrant), tunes performance, configures MCP server. Progress saves to ~/.tea-rags/setup-progress.json for resumable install. Triggers on "install tea-rags", "set up TeaRAGs MCP", "configure tea-rags from scratch", "поставить tea-rags в проект". NOT for tuning an existing install — use tune for that.

Repository
tearags-mcp ↗
Licence
MIT
Last repository change
18.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
15
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 18.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Run automated TeaRAGs install wizard from scratch — detects environment, installs deps (Node.js, tea-rags, Ollama/ONNX/llama-server, Qdrant), tunes performance, configures MCP server. Progress saves to ~/.tea-rags/setup-progress.json for resumable install. Triggers on "install tea-rags", "set up TeaRAGs MCP", "configure tea-rags from scratch", "поставить tea-rags в проект". NOT for tuning an existing install — use tune for that.

Triggers from the description

install tea-ragsset up TeaRAGs MCPconfigure tea-rags from scratchпоставить tea-rags в проект

Arguments

/install [project path]
Original author description

Run automated TeaRAGs install wizard from scratch — detects environment, installs deps (Node.js, tea-rags, Ollama/ONNX/llama-server, Qdrant), tunes performance, configures MCP server. Progress saves to ~/.tea-rags/setup-progress.json for resumable install. Triggers on "install tea-rags", "set up TeaRAGs MCP", "configure tea-rags from scratch", "поставить tea-rags в проект". NOT for tuning an existing install — use tune for that.

How it works

  1. How to use this skill
  2. Script Location
  3. Steps
  4. Error Recovery
  5. Do NOT
Original SKILL.md headings · 81 lines, 453 words
SKILL.md preview
---
name: install
description:
  Run automated TeaRAGs install wizard from scratch — detects environment,
  installs deps (Node.js, tea-rags, Ollama/ONNX/llama-server, Qdrant), tunes
  performance, configures MCP server. Progress saves to
  ~/.tea-rags/setup-progress.json for resumable install. Triggers on "install
  tea-rags", "set up TeaRAGs MCP", "configure tea-rags from scratch", "поставить
  tea-rags в проект". NOT for tuning an existing install — use tune for that.
argument-hint: [project path]
---

# TeaRAGs Setup Wizard

Automated install + config of TeaRAGs MCP server.

## How to use this skill

1. Read step file for current step from `steps/`
2. Read `reference.md` for lookup tables (recommendations, version managers, env
   vars, defaults)
3. Execute step
4. Next step

## Script Location

All scripts in `${CLAUDE_PLUGIN_ROOT}/scripts/setup/`.

**First: determine OS to select script set.**

Run `uname -s` (or via Bash tool)

- Output contains "Darwin" or "Linux" → use `unix/` scripts (`.sh`)
- Output contains "MINGW", "MSYS", "CYGWIN" → use `unix/` scripts (Git Bash)
- If PowerShell detected (Windows native) → use `windows/` scripts (`.ps1`)

Store chosen prefix (e.g. `SCRIPTS="${CLAUDE_PLUGIN_ROOT}/scripts/setup/unix"`),
use for all subsequent script calls.

## Steps

| Step | File                           | What it does                            |
| ---- | ------------------------------ | --------------------------------------- |
| 0    | `steps/step-0-progress.md`     | Check/init progress file                |
| 1    | `steps/step-1-detect.md`       | Detect environment, save to progress    |
| 2    | `steps/step-2-node.md`         | Install Node.js 24+                     |
| 3    | `steps/step-3-tea-rags.md`     | Install tea-rags package                |
| 4    | `steps/step-4-embedding.md`    | Choose & install embedding provider     |
| 4L   | `steps/step-4-llama-server.md` | llama-server: GPU host sheet + fallback |
| 5    | `steps/step-5-qdrant.md`       | Choose & setup Qdrant                   |
| 6    | `steps/step-6-tune.md`         | Tune performance parameters             |
| 7    | `steps/step-7-git.md`          | Configure git analytics                 |
| 8    | `steps/step-8-configure.md`    | Configure MCP server                    |
| 9    | `steps/step-9-register.md`     | Register project alias (before index)   |
| 10   | `steps/step-10-verify.md`      | Verify setup                            |
| 11   | `steps/step-11-freshness.md`   | Offer auto-update + worktree mode       |

**Reference**: `reference.md` — recommendation tables, version manager options,
env vars, tune defaults.

## Error Recovery

If a script fails (exit code 1):

1. Show stderr error to user
2. Progress file retains last successful state
3. Suggest re-running `/tea-rags-setup:install` — resumes from failed step

**Common issues to check:**

- **Network/proxy errors** (ECONNREFUSED, timeout, SSL): ask if behind corporate
  proxy. If yes: "Set proxy before re-running:
  `export HTTP_PROXY=http://proxy:port HTTPS_PROXY=http://proxy:port`"
- **Permission errors** (EACCES): suggest sudo or fix ownership
- **"command not found" after install**: suggest restart terminal or source
  shell profile (`source ~/.bashrc` / `source ~/.zshrc`)
- **jq/curl missing**: scripts report explicitly — follow install instructions
  in error message

## Do NOT

- Run scripts without checking progress first
- Skip AskUserQuestion for user choices (embedding, qdrant)
- Run llama-server or its printed lines yourself on GPU host — print, hand to
  user. Local fallback lines: hand to user too
- Use Ollama as llama-server fallback — `EMBEDDING_FALLBACK_URL` = local
  llama-server only
- Proceed past a checkpoint without verification
- Modify MCP config for other servers
- Run indexing — that is `/tea-rags:index` after restart. (Step 9 registers
  alias only — records path mapping, does NOT index.)
Files in this package (15)
  • SKILL.md 4 KB
  • reference.md 9 KB
  • steps/step-0-progress.md 1 KB
  • steps/step-1-detect.md 1 KB
  • steps/step-10-verify.md 1 KB
  • steps/step-11-freshness.md 2 KB
  • steps/step-2-node.md 2 KB
  • steps/step-3-tea-rags.md 1 KB
  • steps/step-4-embedding.md 4 KB
  • steps/step-4-llama-server.md 4 KB
  • steps/step-5-qdrant.md 1 KB
  • steps/step-6-tune.md 2 KB
  • steps/step-7-git.md 2 KB
  • steps/step-8-configure.md 3 KB
  • steps/step-9-register.md 2 KB

Versions

RepositoryScoreLicence
This page · artk0de/tearags-mcp90MIT
rossoctl/context-guru100Apache-2.0
jeremylongshore/tons-of-skills-marketplace100MIT
codifydoo/gatehand100MIT
terrylica/cc-skills100MIT
agile-4/opem-agent-plugin100MIT
artk0de/tearags-mcp100MIT
artk0de/tearags-mcp100MIT
brainweb/payload-mcp-oauth100MIT

Database snapshot: 13.11.2026 · package version 3ca421b0a344 (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

  • 100tune
    Benchmark this hardware and write optimal performance parameters (embedding throughput, Qdrant storage, pipeline concurrency, git trajectory) into ~/.tea-rags/setup-progress.json. Triggers on "indexing is slow", "tune performance", "benchmark my hardware", "find optimal batch…
  • 100report-issue
    Help the user file a high-quality GitHub issue for a TeaRAGs bug — gather environment + diagnostic context, CHECK FOR EXISTING/KNOWN ISSUES FIRST, then produce a pre-filled issue URL (or `gh issue create` when available). Triggers on "report a bug", "file an issue", "open a…
  • 100mcp-servers
    Install, configure, authenticate, and troubleshoot MCP (Model Context Protocol) servers for this agent. Use when the user asks to add/install/remove an MCP server, connect a tool like Linear/Sentry/Supabase/GitHub via MCP, set up mcp.json, or when MCP tools are failing or need OAuth login.
  • 100ac-tools-setup-voice-mode
    Installs and configures VoiceMode MCP for voice interactions in the target client. Triggers on keywords: setup voice, voice mode, install voicemode, configure voice
  • 100ubrowser-setup-validator
    Install, validate, or diagnose the upstream uBrowser MCP runtime and its local Playwright dependencies. Use for missing server files, MCP startup failures, tool-surface checks, or a clean uBrowser setup; do not use for ordinary browser automation.
  • 100mcporter-setup
    Install MCPorter and configure MCP servers from scratch. Use when setting up MCP integration for the first time, adding new MCP servers, or troubleshooting MCP connectivity. Handles installation, configuration, secrets management, and connection testing.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.