Blog post writer for AEO-optimized, data-driven sites. Writes posts based on BLS/ONET data or equivalent authoritative sources, following the site's tone guide and content structure. Career/product pages generated by data pipelines are out of scope — use this skill for editorial blog posts only.
Analyze webpages for content quality, schema markup completeness, and AEO (Answer Engine Optimization). Designed to complement Ahrefs Site Audit findings.
Research AEO (Answer Engine Optimization) opportunities by discovering what questions AI engines are actually answering in your niche, which domains and pages they're citing, and what content formats are winning citations.
Backlink and citation outreach for a newly published post. Finds Substack writers, journalists, and bloggers likely to reference the post's key claim, generates personalized pitches, and maintains a running outreach contacts file. Use after a post is published and socially distributed.
Social distribution for a newly published post. Drafts Reddit comments/posts and a LinkedIn post in one run. Invokes reddit-content and linkedin-content as sub-skills. Use when a post is published and ready to distribute to social channels.
Central coordinator for the content pipeline. Maintains a prioritized task board across 4 workstreams, routes work to the right skill, tracks citation performance, and learns from GSC data and human feedback to improve future routing and flag skill updates.
Pre-publish checklist for blog posts, career pages, industry pages, and /now articles. Run before publishing or updating to validate SEO, dates, sitemap, formatting, and build.
Analyze competitor websites to identify their SEO strategies, content gaps, and generate prioritized target keywords with ranking potential. Use when users want to understand competitor SEO tactics, find keyword opportunities, identify content gaps, or build a keyword strategy based on competitive intelligence.
★not rated 16 4mo agoA55 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: