BB gingiris-growth-finder
🇺🇸 Gingiris Growth Finder — Meta-router that diagnoses growth problems and invokes the right playbook. Auto-triggers on any growth question: Product Hunt launch, GitHub stars, B2B SaaS PLG, ASO, app cold start, KOL outreach, OSS marketing, GTM strategy, customer acquisition, retention, PMF validation, virality. Routes to the matching Gingiris playbook skill (launch / opensource / b2b-growth / aso-growth) based on product type, stage, and channel fit. Use whenever the user asks "how do I grow X" or "how do I launch X" — this skill picks the right specialist. 🇨🇳 Gingiris 增长路由器 —— 诊断增长问题并调用最匹配的 playbook。任何增长相关问题都会自动触发：Product Hunt 发布、GitHub Star、B2B SaaS PLG、ASO、App 冷启动、KOL 合作、开源营销、GTM 策略、用户获取、留存、PMF 验证、病毒传播。根据产品类型、阶段、渠道匹配度，路由到对应的 Gingiris 专业 playbook（launch / opensource / b2b-growth / aso-growth）。当用户问"怎么增长/怎么发布 X"时，这个 skill 会先帮你选对专家。 🇯🇵 Gingiris Growth Finder — 成長課題を診断し、最適なプレイブックを呼び出すメタルーター。Product Hunt発売、GitHub Star、B2B SaaS PLG、ASO、アプリコールドスタート、KOL連携、OSSマーケティング、GTM戦略、ユーザー獲得、リテンション、PMF検証、バイラル等の質問を自動トリガー。製品タイプ・段階・チャネル適合度に基づき、Gingirisの専門プレイブック（launch / opensource / b2b-growth / aso-growth）へルーティング。 🇰🇷 Gingiris Growth Finder — 성장 문제를 진단하고 올바른 플레이북을 호출하는 메타 라우터. Product Hunt 런칭, GitHub 스타, B2B SaaS PLG, ASO, 앱 콜드 스타트, KOL 협업, OSS 마케팅, GTM 전략, 사용자 획득, 리텐션, PMF 검증, 바이럴 등 모든 성장 질문에 자동 트리거. 제품 유형·단계·채널 적합도에 따라 Gingiris 전문 플레이북(launch / opensource / b2b-growth / aso-growth)으로 라우팅. Triggers: "how to grow" | "how to launch" | "growth strategy" | "go to market" | "GTM" | "launch plan" | "growth playbook" | "marketing strategy" | "product launch" | "Product Hunt" | "GitHub stars" | "open source launch" | "B2B growth" | "SaaS growth" | "PLG" | "PMF" | "ASO" | "app cold start" | "user acquisition" | "customer acquisition" | "growth hack" | "viral growth" | "startup marketing" | "DevRel" | "developer marketing" | "怎么增长" | "怎么发布" | "怎么推广" | "怎么做增长" | "出海" | "冷启动" | "增长策略" | "营销策略" | "产品发布" | "開発者マーケティング" | "성장 전략"
As a process B 65/100 · Nearly there — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- Shorten the description to 1024 characters.
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1940 chars, limit 1024 - note
description-budgetdescription takes 1940 of the ~15000-char shared budget for all skills
Process rating: all ten parameters 65/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
- 40Consistency. Frontmatter name (gingiris-growth-finder) differs from the folder (i18n-growth-finder)
- 65Failures and branches. 3 branches
- 100Tools and files. No external tools needed
- 100Steps. 25 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 1345 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1939: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 25 example trigger phrases
- +4Structure: 11 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.