AC ai_stack_builder
Build a personalized AI tool stack based on role, goals, and budget. Recommends specific tools for each category (writing, meetings, coding, research, productivity, etc.) with free/paid tiers, pricing, and why each tool fits the user's situation. Pairs with ai-productivity-audit: audit cuts the bad tools, stack builder recommends the replacements. Use when a user asks what AI tools they should use, wants to build a productivity stack, is switching roles, or wants to set up AI tools from scratch. Premium version available: https://buy.stripe.com/4gMeVd7ld8Pk7U371P1Jm0M
As a process C 61/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (ai_stack_builder) differs from the folder (ai-stack-builder)
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 77 steps
- 100Execution cost. Instruction body is 1909 tokens
- 100Running it twice. Mutating operations check current state
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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 574: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 77 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.