setup
Use when the user wants qsm on a machine or wants to change what is installed or asks what to add: set up qsm, install the plugins, which plugins do I have, reconfigure qsm, doctor says, fix my Claude Code install, which qsm tools are new on main, the bin farm is stale, add a plugin to this machine, nastav qsm, nainstaluj pluginy.
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- setup
- description
- Use when the user wants qsm on a machine or wants to change what is installed or asks what to add: set up qsm, install the plugins, which plugins do I have, reconfigure qsm, doctor says, fix my Claude Code install, which qsm tools are new on main, the bin farm is stale, add a plugin to this machine, nastav qsm, nainstaluj pluginy.
03 SKILL.md 正文
Setup
qsm-setup is the marketplace's proactive installer. A user who knows what they want names the verb; one who does not gets a guided run that picks the arguments, asks for the go before anything is written, and ends by offering the usage review (the qsm-usage skills do the judging). Install changes no file the user owns; only an activation writes into the Claude home, so each one waits for its own answer.
Direct
Run the verb the user named, read the per-plugin lines, report them.
qsm-setup install --all,qsm-setup install <plugin...>, orqsm-setup install --profile general: exactly one of the three; dependency order is the tool's job.qsm-setup doctor [<plugin>] [--verbose]: one line per installed plugin, orphans as warnings, the built-binaries check, the activation state of each plugin, then theclaude ...lines for the Claude Code installation.qsm-setup activate <plugin> -- <options>: the activation step of one plugin, see Guided.qsm-setup relink [--check]: completions regenerated, undeclared binaries and completions pruned;--checkwrites nothing and exits 1 when stale.qsm-setup build-bins: every plugin's own build step, then the record doctor compares against.qsm-setup tools [--fetch]: the qsm binaries onorigin/mainagainst this machine, verbs added and removed. Without--fetchit says how old main is and stays offline.
Guided
- Ask which plugins, with the general profile as the recommended answer: general, everything, or
a named list.
qsm-setup install --all --dry-runlists every plugin and what its installer would do. qsm-builder is not in the general profile and installs at project scope inside the marketplace checkout only, so offer it only there. - Get the go, then run one install call and read every status line.
suggestedmeans the installer left a command for the user;blockedmeans a requirement failed first;missing-prereqnames a tool to install by hand. - Then the activations, one question each,
--dry-runfirst, then the user's choice, because an activation writes into the Claude home. Doctor shows which plugins are activated.- qsm-setup:
qsm-setup activate qsm-setup -- --instructions <replace|overwrite|skip>. Replace is the default: the plugin is the source of the instructions, and the activation rewrites only its own marked area in every file it writes (CLAUDE.md, the rules, the output style), keeping everything outside the markers, where text specific to this device lives. Overwrite rewrites the whole file and runs only when the person asks for it. - qsm-memory, when installed: "Use the qsm session archive as the one memory? Claude Code's own
memory is then turned off (
autoMemoryEnabled: false) and its transcripts are kept for good (cleanupPeriodDays: 36500; the default deletes them after 30 days); the MCP is already connected by the plugin." Yes:qsm-setup activate qsm-memory -- --memory qsm. No:--memory claude, which records the choice and leaves Claude Code's own retention in force: it deletes transcripts after 30 days and qsm-memory packs nothing.
- qsm-setup:
- Run doctor and report PASS / FAIL / SKIP per plugin, the
claude ...lines and the summary line. A FAIL is a finding for the user, not something to retry. - End with the usage review offer, the one walkthrough setup hands off to.
- doctor shows qsm-usage is not installed: say that a review session needs qsm-usage and give
qsm-setup install qsm-usage. - it is installed: ask through the ask tool whether to start the usage review now. On yes load
the qsm-usage
usageskill and the rest is its work. On no say the phrase that starts it later: "review my Claude Code usage".
- doctor shows qsm-usage is not installed: say that a review session needs qsm-usage and give
Write nothing and start nothing until the person says yes to that one.
Claude Code health
Doctor's claude ... lines only report. Each FAIL names its fix; show the line and the exact fix,
ask once per fix, apply it after the yes, never a batch "fix all". Then run doctor again.
- Removals (
claude installs): run the command the line names. - PATH (
claude path): add the line to the shell profile the user names. - A file that does not parse (
claude config): read only the lines around the named line and column and fix the JSON there. - One key (
installMethod): read and write that key alone,jq '.installMethod' ~/.claude.json. Settings files and.claude.jsonhold tokens and paths, so nevercatone or print its content in the reply; name the file, the key and the position. - Agents and skills: add the missing
description:line, rename one of the sharedname:values, or fix the frontmatter YAML at the named lines, showing the user the change. - Version (
claude version):claude update.
Red flags
- When the run is about to end after doctor with no usage review offer made, make it, because the person otherwise never learns the review exists.
- When it is a first setup, show a dry run before the install, because the user has not seen what gets written.
- When you want
--alland plugin names in one call, pick one, because the tool refuses both. - When you are about to choose overwrite, ask first and name the text outside the markers it would delete, because that text is specific to this device and lives nowhere else.
- When a status is
suggested, report it as not installed, because the user still has a command to run.
Say it in the reply
After install, one line per plugin, name: status: detail, nothing summarised away. After doctor,
the summary line plus every FAIL with its exit code and remedy.
04 同仓库更多 Skills
worktrunk
Use when working with git worktrees or wt (worktrunk): creating, switching, merging or removing a branch workspace, configuring wt (project or personal config, workflow hooks around switch, commit and merge, commit-message generation, hook approvals), or a wt command that failed. Triggers: make a worktree for this branch, wt merge, wt remove, configure wt, .config/wt.toml, run tests before merge, install deps when a worktree is created, wt hook, wt switch does not cd, nastav wt, wt nefunguje.
web-ladder
Use when a task needs something the internet holds: look something up, search the web, find which page answers a question, read a page, check a library's current docs, a page that needs a browser or shows a captcha. Runs one research loop: searxng search, keywords, cases, search again up to three times, Context7 for a library, Tavily when the keywords will not come, one page in a browser, the person on a wall. Triggers: look this up, search the web, find out online, read this page, check the docs, the page is blocked, captcha, najdi na webu, otevri tu stranku. A multi-round question goes to the qsm-web:web-research agent; one tool's commands are its own skill (searxng, browserbox, opensrc).
searxng
Use when running a web search through the person's own SearXNG instance with qsm-web searxng: choosing a search profile or engines, the instance, time range or language, reading its JSON, a suspended engine. Triggers: search with searxng, qsm-web searxng, search profile, niche search, academic search, IT search, vyhledavaci profil, searxng is down, which engines. The research loop around it is the web-ladder skill.
opensrc
Use when the source code of an open-source library or repository is needed on disk to read: the docs are silent, the behaviour must be checked in code, the version the project pins. Runs qsm-web opensrc get with a package spec or a repository address. Triggers: get the source of this package, clone this library, read the library's code, qsm-web opensrc, stahni zdrojak knihovny. Library docs are the Context7 skill; the research loop is the web-ladder skill.
browserbox
Use when one page needs a real browser through qsm-web browserbox: content built by script, a page that blocks plain fetching, a captcha to solve or hand to the person, a scripted sequence of clicks, a login the person is present for. Triggers: open it in a browser, the page is empty without JavaScript, captcha, take over the browser, run these steps on the page, log in to this site, browserbox. When to reach for a browser at all is the web-ladder skill.
usage
Use when the user wants a review of how they use Claude Code, or setup hands over after a first install: review my Claude Code usage, audit my setup, what does my setup cost, where did my tokens go, clean up my Claude Code, usage report, zkontroluj moje pouzivani. One walkthrough of four stages (machine, work, habits, extensions), questions after each, then one plan. A question about one topic (which hooks are slow) goes to that topic's skill; this session's tokens alone is `/qsm-usage`.