AD problem-solver
When user asks to solve a problem, fix an issue, troubleshoot, debug, find solution, brainstorm, help me decide, should I, pros and cons, root cause, what should I do, stuck on, confused about, overwhelmed, prioritize tasks, compare options, think through, figure out, decision making, or any problem-solving task. 20-feature AI problem solver with 10+ frameworks including 5 Whys, decision matrix, SWOT, Eisenhower matrix, brainstorming, step-by-step solutions, and progress tracking. All data stays local — NO external API calls, NO network requests, NO data sent to any server.
When user asks to solve a problem, fix an issue, troubleshoot, debug, find solution, brainstorm, help me decide, should I, pros and cons, root cause, what…
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5333 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (problem-solver) differs from the folder (problem-solver-ai)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Execution cost. Instruction body is 5333 tokens
- 100Steps. 38 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 29 top-level sections: this looks like several domains in one skill
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 580: enough signal without eating the budget
- +4Structure: 31 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (46 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.