SKILLEMALL.ai
GitHub ↗ RU Sign in

DC gstack-upgrade

Upgrade gstack to the latest version.

garrytan/gstack Agent Skills author: garrytan MIT 17 files · 16 scripts body ≈ 5 948 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Upgrade gstack to the latest version.

As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureSoftware developmentData and analyticsAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
D
76/100
safety, quality, tests
Safety 60%
94
Quality 40%
48
Run on models
none yet
Process rating
C
61/100
Has gaps
Result and completion w 14
0
When it triggers w 12
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 2

✓ No critical or high findings

Medium and low: 2
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Bash Read Write AskUserQuestion
  • low Dangerous commands cmd-pipe-to-shell-known-host SKILL.md:181
    Pipe-to-shell installer from a well-known host (still executes remote code) (quoted — discussed, not commanded)
    On `BUN_VERSION_UNREADABLE`, STOP: `bun --version` did not print a version gstack can read, so `bun upgrade` may not run either; tell the user to reinstall Bun from https://bun.sh (`curl -fsSL https:/
    quoted

Files scanned: 17. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-short description under 40 chars: too little signal for triggering
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 5948 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "triggers"
  • note edit-residue the text marks something as outdated (lines 110, 289, 362): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 61/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 70Execution cost. Instruction body is 5948 tokens
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 11 steps
  • 100Failures and branches. 3 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The response is described with custom markup (3 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 37: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -2localhost URLs: will not work for another user
  • +1No license
  • +2Single-language instructions
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 11 items
  • +4Has examples (18 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 48.

In the sandbox The scripts kept to themselves

The skill's scripts were run in a throwaway machine: no network, fake keys in the home directory, a tracer watching. We wrote down what they did. Reaching for the network or for secrets caps the technical grade at C; a quiet run adds no points.

Запущено 12 скриптов, ещё 4 не поместились в лимит; каждому дали двадцать секунд, поддельный домашний каталог с ключами и сеть, в которой ничего нет.

Из них 8 не дошли до работы, и об их поведении мы ничего не узнали.

migrations/v0.15.2.0.shничего за пределами своей папки
migrations/v0.16.2.0.shне запустился: migrations/v0.16.2.0.sh: cannot resolve the gstack state root: migrations/../../bin/gstack-state-root.sh is missing. fix: reinstall with ./s
migrations/v1.0.0.0.shне запустился: migrations/v1.0.0.0.sh: cannot resolve the gstack state root: migrations/../../bin/gstack-state-root.sh is missing. fix: reinstall with ./se
migrations/v1.1.3.0.shничего за пределами своей папки
migrations/v1.17.0.0.shничего за пределами своей папки
migrations/v1.27.0.0.shне запустился: migrations/v1.27.0.0.sh: cannot resolve the gstack state root: migrations/../../bin/gstack-state-root.sh is missing. fix: reinstall with ./s
migrations/v1.37.0.0.shне запустился: migrations/v1.37.0.0.sh: cannot resolve the gstack state root: migrations/../../bin/gstack-state-root.sh is missing. fix: reinstall with ./s
migrations/v1.38.1.0.shне запустился: migrations/v1.38.1.0.sh: cannot resolve the gstack state root: migrations/../../bin/gstack-state-root.sh is missing. fix: reinstall with ./s
migrations/v1.40.0.0.shне запустился: migrations/v1.40.0.0.sh: cannot resolve the gstack state root: migrations/../../bin/gstack-state-root.sh is missing. fix: reinstall with ./s
migrations/v1.58.0.0.shне запустился: migrations/v1.58.0.0.sh: cannot resolve the gstack state root: migrations/../../bin/gstack-state-root.sh is missing. fix: reinstall with ./s
migrations/v1.65.0.0.shне запустился: migrations/v1.65.0.0.sh: cannot resolve the gstack state root: migrations/../../bin/gstack-state-root.sh is missing. fix: reinstall with ./s
migrations/v1.67.0.0.shничего за пределами своей папки

19 Oct 2026