SKILLEMALL.ai
GitHub ↗ RU Sign in

AC solo-you2idea-extract

Extract startup ideas from YouTube videos via solograph MCP — index, search, and analyze video transcripts for business ideas. Multi-MCP coordination pattern (YouTube source → analysis → storage). Use when user says "extract ideas from YouTube", "index YouTube video", "find startup ideas in video", "analyze YouTube for ideas", or "what ideas are in this video". Do NOT use for general YouTube watching (no skill needed) or content creation (use /content-gen).

modbender/skill-library-mcp Claude Code author: modbender MIT 2 files body ≈ 1 127 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Extract startup ideas from YouTube videos via solograph MCP — index, search, and analyze video transcripts for business ideas.

As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

AnalyzerYouTubeMedia and videoAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
95
Quality 40%
90
Run on models
none yet
Process rating
C
57/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

    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 · 1

    ✓ No critical or high findings

    Medium and low: 1
    • medium Broad scope meta-broad-allowed-tools SKILL.md:1
      Broad tool permissions pre-approved: Bash
      allowed-tools: Read Grep Bash Glob Write Edit AskUserQuestion mcp__solograph__source_search mcp__solograph__source_list mcp__solograph__source_tags mcp__solograph__source_related mcp__solograph__kb_se

    Files scanned: 2. 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 57/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 50When it triggers. No condition that starts the skill
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 33 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1127 tokens
    • 100Running it twice. No mutating operations

    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

    • +3Output format is not stated: the model decides each time
    • -41 reference files, but SKILL.md never points to them: the model will not open them
    • +2Single-language instructions
    • +5Description quotes 5 example trigger phrases
    • +4Description says when NOT to use the skill
    • +3Description length 461: enough signal without eating the budget
    • +4Structure: 11 headings
    • +3Step-by-step instructions: 33 items
    • +4Has examples (4 code blocks)
    • +1License stated

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