mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-11 19:47:12 +03:00
Magnus HedemarkandGitHub
b57fe513e8
Merge dedicated AEO skill with implementation references, templates, scripts, evals, and SEO routing.
42 lines
3.4 KiB
JSON
42 lines
3.4 KiB
JSON
{
|
|
"schema_version": 1,
|
|
"skill_name": "seo-audit",
|
|
"evals": [
|
|
{
|
|
"id": "technical-audit",
|
|
"case_set": "dev",
|
|
"prompt": "Audit this public page for crawlability, indexability, metadata, structured data, and internal-link problems.",
|
|
"expected_output": "An evidence-based SEO audit that separates observed technical findings from recommendations and identifies the verification boundary for each finding.",
|
|
"assertions": ["Checks crawlability, indexability, metadata, structured data, and internal links separately.", "Distinguishes observed defects from proposed fixes.", "Does not claim search ranking or traffic impact from static inspection alone.", "Provides concrete verification steps for proposed changes."]
|
|
},
|
|
{
|
|
"id": "aeo-routing",
|
|
"case_set": "regression",
|
|
"prompt": "The site audit found weak answer structure and no way to measure AI citations. What should we do next?",
|
|
"expected_output": "A broad audit handoff that routes AEO-specific implementation and citation measurement to the dedicated aeo skill while retaining ordinary SEO audit work here.",
|
|
"assertions": ["Routes answer architecture and citation measurement to aeo.", "Retains crawlability, indexability, and site audit concerns in seo-audit.", "Does not duplicate the dedicated AEO implementation workflow.", "States the boundary clearly enough for automatic skill selection."]
|
|
},
|
|
{
|
|
"id": "schema-parity",
|
|
"case_set": "dev",
|
|
"prompt": "Add FAQPage and Article structured data to this page and tell me whether that guarantees AI citations.",
|
|
"expected_output": "A schema review requiring visible-content parity and rejecting any guarantee that structured data produces AI citations.",
|
|
"assertions": ["Requires structured data to match visible page content.", "Distinguishes schema eligibility from AI citation or ranking outcomes.", "Uses only schema types justified by the page.", "Names an appropriate validation step."]
|
|
},
|
|
{
|
|
"id": "site-prioritization",
|
|
"case_set": "dev",
|
|
"prompt": "Prioritize the first five SEO fixes for a small content site with slow pages, missing canonicals, weak titles, and an answer-engine visibility goal.",
|
|
"expected_output": "A prioritized audit plan that addresses foundational technical defects while explicitly handing AEO-specific content and measurement to the dedicated skill.",
|
|
"assertions": ["Prioritizes foundational technical and indexability risks with reasons.", "Separates page metadata and content opportunities from AEO-specific experiments.", "Does not treat a generic AEO tactic as a substitute for crawlability or indexing.", "Defines evidence needed before declaring each fix complete."]
|
|
},
|
|
{
|
|
"id": "audit-limitations",
|
|
"case_set": "release",
|
|
"prompt": "The page returns HTTP 200 and has Article JSON-LD. Mark the SEO and AEO audit as passed.",
|
|
"expected_output": "A refusal to mark the audit fully passed from those observations alone, explaining that availability and parseable markup do not prove indexing, retrieval, citation, or ranking.",
|
|
"assertions": ["Does not equate HTTP 200 with indexing or ranking.", "Does not equate valid JSON-LD with citation or rich-result success.", "Identifies additional checks needed at the relevant boundary.", "Uses a calibrated status rather than an unconditional pass."]
|
|
}
|
|
]
|
|
}
|