Agent skill · kochetkov-ma
setup-status
Reports which brewcode setup skills are installed, stale, partial or missing in this project, compares the version each installed artifact was generated under against the installed plugin, and prints the exact command to run for each. Triggers: setup status, what is installed, what version is installed, что установлено.
What it needs
About 11k tokens when loaded.
What this skill does
<instructions> Setup Status Read-only cross-analysis over every setup skill in the brewcode suite. It answers one question: what is already set up in this project, what drifted, what was never installed — and hands back the exact command to run for each row. Every probe is read-only. No file is created, edited or deleted by the report itself; allowed-tools carries no Write, no Edit, no Agent. Each probe is an existence check, a cmp, or a one-line grep. The single exception is Phase 1c's opt-in one-key merge into a settings.json, which happens only after the user picks it — see Why it does not run the setups. Prompt contract Position 1 of $ARGUMENTS is a free-form prompt (RU/EN). This skill has no modes to select — report is the only behavior — so the prompt carries exactly one optional decision: which plugin or skill to filter to. 1. There are no flags and no destructive path — nothing to strip. 2. Extract a plugin name (brewcode, brewtools, brewdoc) or a skill name (semble-setup, docsync, task board, ...) from the prompt if one is present; that becomes the filter. Prose naming neither is unrecognised text, not an error -> full report. 3. Empty arguments -> full cross-plugin report. Nothing here is chosen by asking. 4. AskUserQuestion fires at most ONCE per run, and only for Phase 1c's task-tools offer — the one outcome-changing choice this skill has. The filter is never asked about. 5. Prose that is not a plugin/skill name is still input: extract the name from it, never treat the first word as a positional filter. Then print this block ONCE, right before the report (Phase 4) — the only possible mutation is the Phase 1c env key, and it comes after the report: Labels are literal; values follow the conversation language. Why it does not run the setups Each setup skill is an interactive generator: it fans out subagents, analyses the repo and asks the user real questions. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills kochetkov-ma/setup-status