SKILLEMALL.ai

BD idea2mvp

Discover product ideas, validate them, and build MVPs. Search trending tools across Product Hunt, GitHub, Indie Hackers, XiaoHongShu, V2EX, SSPAI, etc. Validate feasibility via market research and competitive analysis. Build MVPs. Send reports via email. Triggers: 'find ideas', 'search products', 'trending tools', 'product ideas', 'validate my idea', 'build MVP', 'market research', 'competitive analysis', 'indie hacker', 'send email', '找想法', '搜产品', '找灵感', '产品调研', '验证想法', '构建MVP', '发邮件', '发送报告'.

ClawHub Agent Skills author: Morvan v1.0.18 MIT-0 20 files body ≈ 1 970 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerGitHubData and analyticsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
73
Run on models
none yet
Process rating
D
48/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • 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: 20. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 48/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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Steps. 76 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1970 tokens

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
  • -31 of 10 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 499: enough signal without eating the budget
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 76 items
  • +4Has examples (2 code blocks)
  • +4Reference files are cited in the instructions (7 of 7)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.

External checks

ClawHub: suspicious
This skill mostly does what it advertises, but it silently stores user profile details and uses risky authenticated web automation that deserves review before installation.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026