AB side-hustle-analyst
Runs structured day-by-day execution for AI agent side hustles. Use when: executing the Agent Side Hustle School workflow, tracking experiment progress, or maintaining persistent state across a 28-day hustle cycle. NOT for: generic productivity advice, long-term business strategy, or non-AI/agent business ideas.
As a process B 73/100 · Nearly there — weak spots: inputs and preconditions, failures and branches
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
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Runs structured day-by-day execution for AI agent side hustles. Us… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 73/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 23 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 389 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 313: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 23 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.