agentleFS
oegeyilmaz9oegeyilmaz9/seo-aeo-geo-ultimate/skills/seo-images/SKILL.md

seo-images

Skill6 starsChanged 3 months agoApache-2.0View on GitHub

Use when reviewing image accessibility, discoverability, metadata, responsive delivery, image sitemaps, or visual performance from a page/media inventory; provide evidence-linked improvements without keyword, format, or ranking guarantees.

32 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-maps, seo-sxo and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • timruebenachSkill

    seo-maps

    Maps intelligence for local SEO — geo-grid rank tracking, GBP profile auditing via API, review intelligence across Google/Tripadvisor/Trustpilot, cross-platform NAP verification (Google/Bing/Apple/OSM), competitor radius mapping, and LocalBusiness schema generation from API data. Three-tier capability: free (Overpass + Geoapify), DataForSEO (full intelligence), DataForSEO + Google (maximum coverage). Use when user says "maps", "geo-grid", "rank tracking", "GBP audit", "review velocity", "competitor radius", "maps analysis", "local rank tracking", "Share of Local Voice", or "SoLV".

    Also in 18 projects that use this

  • timruebenachSkill

    seo-sxo

    Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says "SXO", "search experience", "page type mismatch", "SERP analysis", "user story", "persona scoring", "why isn't my page ranking", "intent mismatch", or "wireframe".

    Also in 18 projects that use this

  • indranilbanerjeeSkill

    seo-drift

    Compare two SEO exports (Search Console, two dates): gainers, losers, drift classes. \"what moved after the core update\"

    Also in 20 projects that use this

  • mangollcSkill

    seo-backlinks

    Backlink analysis and link building strategy: competitor backlink profiling, outreach plan generation, monthly SEO reporting framework, toxic link identification, link opportunity scoring, and unlinked mention discovery.

    Also in 18 projects that use this

  • +6 more from timruebenach

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read markdown-delivery-contract.md for every task.

    line 10
  2. Very specific:

    Read references/image-review-protocol.md before preparing a formal media recommendation.

    line 19
  3. Distinctive:

    Do not infer file format, dimensions, loading behavior, or user impact from a filename.

    line 25
  4. Distinctive:

    Review accessibility: Check meaningful alternative text, captions/nearby explanation, controls, contrast/legibility where text is embedded, …

    line 30
  5. Distinctive:

    Review discovery/metadata: Check whether significant images are reachable in rendered content and whether page context, canonical URLs, …

    line 32
  6. Distinctive:

    Do not use keyword-stuffed alt text, duplicate captions, decorative image descriptions, fake EXIF metadata, or image sitemap stuffing.

    line 37
  7. Distinctive:

    Do not promise image search visibility, page ranking, Core Web Vitals, or conversion improvement.

    line 38
  8. Distinctive:

    Keep image discovery, user accessibility, and rendering performance as separate verifications.

    line 40

“Common” is measured: kept by at least 6 in 10 of the 31 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SEO Images

Markdown delivery contract

Read markdown-delivery-contract.md for every task. Write a substantive .md document for every material work step and register its direct destination in the work index.md. For public-site work, apply the owner-required Markdown discovery profile across the full eligible inventory; preserve native standards and immutable evidence formats.

Lane outputs: image-review.md; media-map.md (combine small related steps with stable section links). Preserve relevant captions, alt meaning, source/licensing facts and media destinations in Markdown. Keep actual image files and responsive delivery contracts; do not pretend a text export reproduces visual evidence.

Purpose

Improve the way meaningful visual assets are understood and delivered to people and crawlers. This skill separates accessibility, rendering/performance, asset rights, and image-search discoverability instead of treating them as one score.

Read references/image-review-protocol.md before preparing a formal media recommendation.

Input gate

Require the rendered page or asset inventory, image purpose/context, source URL, intrinsic dimensions/format/size, delivery behavior, locale, accessibility context, and any available field/lab evidence. Ask who owns the image/license and whether an image is content, UI decoration, hero/LCP candidate, product/media asset, or purely decorative.

Do not infer file format, dimensions, loading behavior, or user impact from a filename. Do not recommend an image or alt text without seeing its page context.

Workflow

  1. Inventory by purpose. Map each material image to the visible topic, page region, adjacent text/caption, owner/license, and delivery URL. Mark decorative images as decorative rather than inventing alt text.
  2. Review accessibility. Check meaningful alternative text, captions/nearby explanation, controls, contrast/legibility where text is embedded, and responsive mobile rendering. Alt text explains the image’s purpose in context; it is not a keyword field.
  3. Review delivery. Inspect dimensions, responsive candidates, intrinsic width/height or aspect-ratio reservation, loading priority, lazy loading behavior, cache/CDN policy, and actual LCP/CLS/interaction evidence when available. A newer format is not automatically an improvement; evaluate support, source quality, byte savings, and visual fidelity.
  4. Review discovery/metadata. Check whether significant images are reachable in rendered content and whether page context, canonical URLs, structured data, and image sitemap use are truthful and relevant. Route structured data to seo-schema and sitemap changes to seo-sitemap.
  5. Plan safe changes. For each action name the asset/template scope, owner, accessibility/content review, visual QA, performance test, approval, and rollback. Send systemic delivery changes through seo-action-plan.

Guardrails

  • Do not use keyword-stuffed alt text, duplicate captions, decorative image descriptions, fake EXIF metadata, or image sitemap stuffing.
  • Do not promise image search visibility, page ranking, Core Web Vitals, or conversion improvement.
  • Respect licenses, consent, privacy, and brand requirements. Do not expose internal image URLs or generate derivative assets without authorization.
  • Keep image discovery, user accessibility, and rendering performance as separate verifications.

Formal evidence handoff

When this work needs a cross-team, approval-ready plan, package evidence-bound findings as an immutable seo-findings.json bundle using the checked-out suite contract. Let <suite-root> mean ${CLAUDE_PLUGIN_ROOT} in Claude Code. In Codex, read .seo-suite-runtime.json beside this SKILL.md when present and use its suite_root value; otherwise use the absolute repository checkout. Keep every referenced capture/source below raw/, retain declined claims and limitations, and run python "<suite-root>/scripts/validate_seo_findings.py" validate-findings <bundle>/seo-findings.json --bundle <bundle>. Send only a passing bundle to seo-action-plan; otherwise label the handoff provisional.

Output

Return a media inventory with observations, accessibility/performance/discovery recommendations, source-aware implementation notes, test path, and rollback. Provide alt-text or caption options only with visible context and label them as reviewable suggestions.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.