aios-titles-meta

Generates and repairs SERP title tags and meta descriptions for client pages via the AIOS content job pipeline.

1|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/codesofadan/danyals-aios --skill aios-titles-meta-codesofadan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aios-titles-meta
Source: https://github.com/codesofadan/danyals-aios/tree/main/.claude/skills/aios-titles-meta
Command: npx skills add https://github.com/codesofadan/danyals-aios --skill aios-titles-meta-codesofadan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing SEO title tags and meta descriptions that meet length limits, front-load the primary keyword, and stay grounded in real client facts is slow and error-prone when done by hand. This Skill runs the full generation-and-QA pipeline and returns a review-ready snippet with character counts and QA signals for human approval. ## Core Features & Use Cases - Spec-compliant generation: Creates titles under ~60 characters and meta descriptions under ~155 characters using the 4 U's framework (Useful, Urgent, Unique, Ultra-specific), grounded in the client's real context. - Repair mode: Fixes thin, too-long, or keyword-missing titles and descriptions on existing content jobs by routing brief edits through a LEAD-approved PATCH instead of spinning up duplicate jobs. - QA-gated output: Returns character counts, primary-keyword placement checks, and QA dimensions (keyword_handling, snippet_extractability, fact_grounding) so a human can approve or route to edit. - Use Case: An operator asks for "titles and meta for AC repair San Jose" for a client; the Skill resolves the client, creates the content job, waits for review status, and presents the title, meta, and QA verdict at the approval gate. ## Quick Start Ask the assistant to generate titles and meta for a client and topic, for example: "Generate titles and meta for client Acme Plumbing on the topic water heater repair Denver."

Frequently Asked Questions about aios-titles-meta

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate SEO title tags and meta descriptions for a client page?▼

Provide the client name and target topic, and the Skill resolves the client, creates a content job with the 4 U's framework, waits for the draft, then returns the title, meta description, character counts, and QA signals for human approval.

How to fix a title tag or meta description that is too long?▼

The Skill flags any title over ~60 characters or meta over ~155 characters and routes the job to an edit action rather than truncating the copy. A LEAD can PATCH the brief and re-run the pipeline to regenerate grounded, in-spec copy.

What are the length limits for title tags and meta descriptions?▼

Titles must stay under roughly 60 characters and meta descriptions under roughly 155 characters, per the content doctrine spec. The Skill measures the returned strings and reports OK or OVER for each.

Can the meta description include pricing or guarantee claims?▼

Only if the claim exists in the client's source material. The fact_grounding QA dimension hard-blocks any invented number, price, or guarantee, and the Skill stops and routes the fact to a human instead of fabricating it.

Why does the title generation report a degraded status?▼

Degraded status means the SERPER or ANTHROPIC API keys are not configured server-side, so generation and QA ran on a deterministic fake. The output is labeled degraded and must not be presented or published as live copy.

Who can approve the generated title and meta for publishing?▼

Only a LEAD role (owner, admin, or manager) can approve at the review gate. Staff users with publish_content permission create and edit jobs, but final approval re-checks the QA gate in the database.