AC nobodybuilt
Use this skill when the user wants to find unexplored tool, app, or project ideas that nobody has built yet. Triggers: 'nobodybuilt', 'find me an idea', 'what should I build', 'viral tool idea', 'unexplored niche', 'blue ocean', 'surprise me with an idea', 'what hasn't been built yet', or when the user sends a screenshot/photo asking for tool ideas. Accepts text or images as input — analyzes screenshots of apps, photos of real-world problems, or Reddit/Twitter posts to identify gaps. Searches GitHub, Reddit, Product Hunt, npm, and AI directories for real gaps, scores ideas on 9 viral factors, then generates complete publish-ready code + README + launch strategy. Do NOT use for: building a specific tool the user already has in mind, code review, debugging, or general brainstorming unrelated to tool/product discovery.
As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, 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: 7. 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 59/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 14 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 65Failures and branches. 3 branches
- 85Steps. 53 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2757 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
- +5Description has no quoted example phrases that should trigger the skill
- +3Description length 827: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 22 headings
- +3Step-by-step instructions: 53 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.