AC gingiris-blog-writer
🇺🇸 SEO Blog Writer — Write blog posts that rank on Google AND get cited by AI search. E-E-A-T content system for SaaS & startups. QAE writing pattern (Question→Answer→Evidence), founder voice injection, Key Stats tables, FAQ Schema generation, comparison article framework, and cross-posting with canonical URLs. 🇨🇳 SEO 博客写手 — 写出同时在 Google 排名和被 AI 搜索引用的文章。E-E-A-T 内容系统：QAE 写作模式（问题→回答→证据）、创始人声音注入、关键数据表格、FAQ Schema 生成、竞品对比文章框架。 🇯🇵 SEOブログライター — GoogleランキングとAI検索引用の両方に最適化されたブログ記事を作成。E-E-A-Tコンテンツシステム：QAEライティングパターン、ファウンダーボイス、キーデータテーブル、FAQスキーマ生成。 🇰🇷 SEO 블로그 라이터 — 구글 랭킹과 AI 검색 인용 모두에 최적화된 블로그 글 작성. E-E-A-T 콘텐츠 시스템: QAE 글쓰기 패턴, 창업자 목소리, 핵심 데이터 테이블, FAQ 스키마 생성. Triggers: "write blog post" | "SEO article" | "content writing" | "blog SEO" | "E-E-A-T content" | "SEO copywriting" | "SaaS blog" | "content marketing" | "write article" | "blog optimization" | "写博客" | "SEO 文章" | "内容写作"
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 51/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 31 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1198 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 888: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 11 example trigger phrases
- +4Structure: 12 headings
- +3Step-by-step instructions: 31 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.