AB memberstack-cli
Use the Memberstack CLI to manage Memberstack accounts from the terminal. Covers authentication, apps, members, plans, custom fields, data tables, and records. Trigger this skill whenever the user wants to interact with Memberstack — including managing members, plans, custom fields, data tables/records, or authenticating with Memberstack. Also trigger when the user mentions "memberstack", "memberstack-cli", membership management, or member data operations via CLI.
As a process B 65/100 · Nearly there — weak spots: result and completion, running it twice
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 65/100
- 0Result and completion. Does not say what the result is
- 30Running it twice. 17 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 31 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1819 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 468: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 31 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (9 of 9)
- +3All 2 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 97.