Skill Claude CodeCodex
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.
Skill Claude CodeCodex
DEPRECATED — use the replacement skills listed below.
Skill Claude CodeCodex
Analyze webpages for content quality, schema markup completeness, and AEO (Answer Engine Optimization). Designed to complement Ahrefs Site Audit findings.
Skill Claude CodeCodex
Run a complete SEO/AEO strategy audit by orchestrating all three core skills, and synthesizing findings into one unified set of recommendations.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
Pre-publish checklist for site pages (blog posts, case studies, career/industry pages, /now articles). Run before publishing or updating a page to validate SEO, dates, sitemap, links, formatting, and build. Site-specific rules live in the project, not in this skill.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
Iteratively screenshot a running dev server with Puppeteer and fix UI issues until the interface matches design guidelines. Use when asked to review, polish, or QA frontend pages.
Skill Claude CodeCodex
Scopes a product or feature into a prioritized, test-ready specification (specs/product/ .md). Inspects the existing codebase and specs first, names the core hypothesis, pushes back hard on scope by cutting or downgrading complexity multipliers, ranks every capability P0/P1/P2 by biggest unlock and riskiest…
Skill Claude CodeCodex
Guides building or improving any visual/UI design (landing pages, app screens, dashboards, marketing pages, prototypes) through a numbered process (0 Set up, 1 Explore, 2 Refine, 3 Polish & hand off) that produces several genuinely distinct directions and pushes past the generic "AI slop" look — instead of…
Skill Claude CodeCodex
Audit an app (built with or without product-engineering, including Replit/Lovable/Bolt prototypes) against five pillars before going live: infrastructure, code quality, security, observability and cost, failure and rollback. Runs a repo scan, then produces a status table per pillar and findings split into fix-now…
Skill Claude CodeCodex
Spec-driven dev loop. One-time setup (guardrails, CONFIG.md, dev/prod analytics keys), then milestone planning with every unit contract written upfront (automated T tests, manual E2E M walkthroughs, analytics events), ADRs, test-first build, an independent maker/verifier gate, and living-spec sync. Guardrails are…
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: