launch-blog-post
Write technical launch blog posts optimized for both traditional SEO and AI engine citation (AEO). Use this skill whenever someone asks to write a launch announcement blog post, a technical blog post for a product release, a changelog-style post, or any written content tied to a product launch that lives on a blog or docs site. Also trigger for "write the blog post for this launch," "draft the announcement," "I need a technical write-up for this feature," or any request to create long-form launch content. Covers post structure, technical writing, benchmarks, tutorials, SEO, and answer engine optimization (AEO/GEO).
79
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./launch-skills/skills/launch-blog-post/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its scope (technical launch blog posts with SEO/AEO), provides explicit trigger guidance with natural user phrases, and occupies a distinct niche. It covers both 'what' and 'when' comprehensively, includes quoted example trigger phrases that match how users naturally speak, and lists specific capabilities like benchmarks, tutorials, and answer engine optimization that differentiate it from generic writing skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: writing launch blog posts, post structure, technical writing, benchmarks, tutorials, SEO optimization, and AEO/GEO optimization. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (write technical launch blog posts with SEO/AEO optimization, covering structure, benchmarks, tutorials) and 'when' (explicit 'Use this skill whenever...' clause with detailed trigger scenarios and quoted example phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases users would actually say: 'write the blog post for this launch,' 'draft the announcement,' 'technical write-up for this feature,' 'launch announcement blog post,' 'changelog-style post,' 'product release.' These are highly natural and varied. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: technical launch blog posts with SEO+AEO optimization. The combination of 'launch,' 'blog post,' 'product release,' and 'AEO' creates a clear, specific domain that is unlikely to conflict with general writing skills or general SEO skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive and well-structured guide for writing launch blog posts with good coverage of post types, writing principles, SEO, and AEO. Its main weaknesses are verbosity (particularly the AEO section which over-explains concepts), lack of truly executable/template artifacts (no schema markup code, no post template), and missing explicit validation steps in the writing workflow. It reads more like a thorough reference document than a lean, actionable skill.
Suggestions
Add a concrete blog post template (markdown skeleton) that Claude can fill in, and include actual schema markup JSON-LD snippets for Article, FAQPage, etc. — these would make the skill significantly more actionable.
Trim the AEO explanatory content (e.g., 'AI search engines are becoming a primary way people discover products' and 'AEO is the practice of...') — Claude knows this. Focus only on the specific techniques.
Add an explicit writing workflow with validation checkpoints, e.g.: 1. Confirm messaging brief exists → 2. Choose post type → 3. Draft → 4. Check against SEO checklist → 5. Check AEO citable passages → 6. Publish → 7. Post-publication checklist.
Consider splitting SEO and AEO sections into separate reference files to reduce the main skill's length, keeping only the most critical points inline with links to detailed guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally well-written but includes some unnecessary explanatory content that Claude already knows (e.g., explaining what AEO is, why AI engines matter, what schema markup does). The AEO section in particular could be significantly tightened. However, most sections earn their place with actionable guidance. | 2 / 3 |
Actionability | The skill provides concrete structural templates, good/bad opener examples, and specific guidelines (word counts, character limits, checklist items). However, it lacks executable artifacts — no actual schema markup code snippets, no template markdown for a blog post, no example of a complete post section. Guidance is specific but not copy-paste ready. | 2 / 3 |
Workflow Clarity | The post-publication checklist provides a clear sequence, and the overall flow (choose type → use brief → write → optimize → publish → follow up) is implicit but not explicitly sequenced as a workflow. There are no validation checkpoints — e.g., no step to review against the messaging brief before publishing, no review gate for SEO/AEO compliance. | 2 / 3 |
Progressive Disclosure | The companion skills section at the end provides good cross-references to related skills. However, the skill itself is quite long (~300+ lines) with the AEO and SEO sections containing substantial inline detail that could be split into reference files. With no bundle files provided, all content is monolithic in a single file. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- amplitude/builder-skills
- Commit
221ffaa
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.