SKILLEMALL.ai
GitHub ↗ RU Sign in

CA spec

Turn vague intent into a precise, executable spec in five phases. (gstack)

The skillemall take

Promises to transform vague intent into a five-phase executable spec. Three files in the archive describe the process, but lack examples or templates to work with. Quality score of 55 signals half-baked content: the instruction exists, but practical material falls short.

Audits found no critical errors, but flagged one medium-level issue—likely inconsistency in descriptions or phase transitions. The skill wasn't tested on models. Runs on all major platforms, including Claude and Cursor.

Install if you need a structure for talking through task clarification with an AI. Skip it if you're looking for ready-made examples or automation.

garrytan/gstack Agent Skills author: garrytan MIT 3 files body ≈ 14 084 tokens Open the sourcegithub.com↗ analyzed 27 h ago

Turn vague intent into a precise, executable spec in five phases.

As a process A 80/100 · Runs to the end — weak spots: inputs and preconditions, execution cost, running it twice

ProcedureAI and agentsSoftware developmentOperations and projectstype 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
C
79/100
safety, quality, tests
Safety 60%
95
Quality 40%
55
Run on models
none yet
Process rating
A
80/100
Runs to the end
Inputs and preconditions w 11
30
Running it twice w 4
30
Execution cost w 6
40
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 · 1

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Bash Read Grep Glob AskUserQuestion

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 14084 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "preamble-tier"
  • note frontmatter-key unknown frontmatter key "triggers"

Process rating: all ten parameters 80/100

  • 30Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 10 mutating operations with no state check
  • 40Execution cost. Instruction body is 14084 tokens: crowds the task out of the window
  • 50When it triggers. No condition that starts the skill
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 116 steps
  • 100Result and completion. Output format and completion criterion are stated
  • 100Failures and branches. 10 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 32 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (10 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 74: 120–800 characters recommended
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +4Structure: 60 headings
  • +3Step-by-step instructions: 116 items
  • +3Output format is stated explicitly
  • +4Has examples (17 code blocks)

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