AC gingiris-competitor-analysis
🇺🇸 Competitor Analysis — SEO/GEO Intelligence & Market Positioning. Analyze competitor SEO rankings, AI search citations, content strategy, and market positioning. Build comparison pages that rank for "[competitor] vs [you]" keywords. Competitive keyword gap analysis, SERP feature mapping, AI citation frequency audit, and positioning framework. 🇨🇳 竞品分析 — SEO/GEO 竞争情报与市场定位。分析竞品 SEO 排名、AI 搜索引用、内容策略和市场定位。构建竞品对比页面，抢占"[竞品] vs [你]"关键词。竞争关键词差距分析、SERP 特征映射、AI 引用频率审计。 🇯🇵 競合分析 — SEO/GEOインテリジェンスと市場ポジショニング。競合のSEOランキング、AI検索引用、コンテンツ戦略を分析。比較ページ構築、キーワードギャップ分析、SERP機能マッピング。 🇰🇷 경쟁사 분석 — SEO/GEO 인텔리전스 및 시장 포지셔닝. 경쟁사 SEO 순위, AI 검색 인용, 콘텐츠 전략 분석. 비교 페이지 구축, 키워드 갭 분석, SERP 기능 매핑. Triggers: "competitor analysis" | "competitive analysis" | "competitor SEO" | "vs page" | "comparison page" | "market positioning" | "keyword gap" | "SERP analysis" | "competitor research" | "竞品分析" | "竞争对手" | "对比页"
As a process C 59/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 59/100
- 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 21 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1096 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 892: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +5Description quotes 11 example trigger phrases
- +4Structure: 11 headings
- +3Step-by-step instructions: 21 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.