A GitHub Action marketplace card is a badge row, not a screencast

The marketplace SKU is a heading, uses: line, and badge row. Qwen or Ideogram owns those letters. An npm readme hero (already a post) is a package page; this is the Actions card.

A GitHub Action that converts is type a maintainer can proof at 100%: the action name as it appears on the Marketplace, uses: owner/repo@v1 as it actually pins, the license and run badges. It is not a cinematic VS Code session with invented YAML and a glowing prompt. Letter the card. Then decide whether the still even needs to move.

The marketplace card is the product

Procurement of an Action is a pause test. The heading has to be the name on the Marketplace. The uses: line has to be the pin you will stand behind. The badge row has to match the shields you already publish. A photoreal hero of “a developer’s dark IDE at night” is a different object. Nobody copies a lamp. They copy the pin.

Do not prompt a video model to “show a premium GitHub Action page with a glowing workflow.” It will invent a cousin action, a cousin org, a cousin tag. A buyer who lands on the real Marketplace card and sees a different string is not looking at creative. They are looking at a lie.

Capture the live card if the type already holds. Crop chrome that is not the SKU. Crop the star count if it will be stale tomorrow. The still is a document. If the live page is a mess of unreadable badges, typeset a mock of the card — not a host.

The uses: line is YAML you ship. Quote it character for character: org, repo, @, version. uses: actions/checkout@v4 is not uses: checkout@latest. A paraphrased pin is a different workflow. Do not let prompt rewriting “clean up” the line.

Qwen letters the uses: line; Ideogram letters the stamp

Body copy, the uses: line, a badge row that has to read as words. That is a page. Qwen Image 3 Text to Image is the stills row when the letters have to read: third-generation Qwen, complex text in Chinese and English, prompt rewriting on by default, 4 credits, 2K max. No audio. No duration. Quote every string. Rewriting is not a licence to paraphrase uses: owner/repo@v1 into uses: owner/repo@main. Scout at 1K. Keep at 2K when someone will zoom.

Eight to twelve words that must read at thumbnail size. Action name, “MIT,” a one-word stamp. That is Ideogram V4: 6 credits, posters and logos listed, accurate text rendering. Quote the string. Do not ask a photoreal workhorse to spell the scope.

Ideogram owns words in the frame is the lettering split. Ideogram is strong on short-to-medium on-image copy. Ask it for a newspaper and you have routed a page to a poster engine. Qwen holds the columns. Ideogram holds the name.

Proof at 100%. One wrong character in the org, the repo, or the tag is a regenerate. Overlay later if the pin will change; bake only when the type is the scene and you will not edit it. Do not chain a stamp on top of baked-in type or you double-print the uses: line.

Badges are the same rule. If they are in the still, they have to match what you publish today. A generated “2.4k stars” on a 90-star action is a fabricated proof. Crop the live card so the shields that will rot are gone.

The agent is a still job, not a screencast

Generate an image from text is the named agent job: describe the still, the agent asks about style, aspect, and count, then picks a fitting image model — or uses the one you name. Cost is priced per model, shown before you confirm. Name Qwen Image 3 when the uses: line is the product. Name Ideogram V4 when the heading is the product. A bare “make me a GitHub Action hero” is how you get a cinematic desk.

The agent will not publish to the Marketplace. It typesets a picture of a card. Do not ask it for a photoreal founder holding a laptop that says uses:. That is a host. The SKU is the heading, the pin, the badges.

Motion is optional and last. A push off an approved card describes only the camera. Do not re-describe the uses: line in a video paragraph. Motion will not correct a misspelled org. A Veo terminal session with invented YAML is the talking meter pointed at the wrong object.

An npm readme is already a post

An npm readme hero is Qwen type, not a screencast already owns the package page: heading, npm i, license badges. That swarm is the registry hero. This page is the Actions card. Mixing them is how a Marketplace listing becomes a package.json, and how a readme ships a cousin uses: line.

The install verbs are different objects. npm is npm i foo. Actions is uses: owner/repo@v1 inside a workflow. Do not send an Action brief to the npm post and hope the model swaps the verb. Change the pin with a new still. Keep the host off this plate. A VS Code screencast is a different product: film it, do not generate a cousin IDE.

FAQ

Can I put the uses: line in a video prompt so the terminal typesets itself?

No. A video row will invent YAML. Letter the card on Qwen Image 3 at 4 credits, 2K, or stamp the name on Ideogram V4 at 6 credits, and proof the characters. Motion, if any, is a later still-to-motion pass of an approved card.

Should the agent invent a typical Action name if I only said “GitHub Action hero”?

No. Generate an image from text will fill something that looks like a Marketplace card. That something is not your action. Write the heading, the uses: line, and the badges, then name the stills row.

When is Ideogram the better row than Qwen Image 3?

When eight to twelve words must read at thumbnail size — the action name, a license stamp. Qwen Image 3 is the page: uses: line, badge row, a short body. Do not send a newspaper to Ideogram, and do not send a three-word lockup to a layout scout unless you already know it holds.

Is the npm-readme post the same job as this Marketplace card?

No. The npm post is the package heading, install line, and badge row as a still. This page is the Actions heading, uses: pin, and badge row. A Veo terminal session is neither.