agentleFS
TheGoat395TheGoat395/Codex-Skills/skills/image-video-loading-qa/SKILL.md

image-video-loading-qa

Skill136 starsChanged 5 months agoMITView on GitHub

Verify media loading and failure states.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to make media-rich sites look intentional instead of broken, cropped, or slow.

    line 8
  2. Distinctive:

    Read Image Video Loading QA Guide before claiming the site is ready.

    line 13
  3. Distinctive:

    Check critical media discovery/loading, reserved dimensions, responsive source selection, posters, slow/failed requests and rejected …

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Image Video Loading QA

Use this skill to make media-rich sites look intentional instead of broken, cropped, or slow.

Workflow

  1. Inspect the affected surface, relevant project scripts, target URL and available inspection tooling; reuse existing context.
  2. Read Image Video Loading QA Guide before claiming the site is ready.
  3. Check critical media discovery/loading, reserved dimensions, responsive source selection, posters, slow/failed requests and rejected autoplay. Preserve meaningful content when media cannot load.
  4. Fix issues when they are in scope; otherwise record exact evidence and remaining risk.
  5. Summarize commands, URLs, screenshots/checks, changed files, and what was not tested.

Scoped execution

Apply the shared web contract once when execution crosses phases; reuse it if already read. Load only the specialist guidance relevant to the requested surface and deliverable.

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.