agentleFS
Sign inStart free
TIKAZITIKAZI/TIKAZ-Codex-Visual-Content/SKILL.md

visual-content

Skill0 starsChanged 3 months agoMITView on GitHub

Orchestrate article illustration, logistics explainers, writing cleanup, and lawful music discovery with explicit style routing, asset provenance, accessibility text, and visual QA. Use for content packages that need coherent visuals without generic image generation.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. kostja94/marketing-skills★ 1.1ksame name
    2. dalroot/agentic-seo★ 23same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Use concise-writing-editor only when the source is padded or generic.

    line 17
  2. Distinctive:

    Create a shot card: message, scene/mechanism, composition, labels, character role, palette, forbidden elements, source assets, and license …

    line 19
  3. Very specific:

    Use legal-free-music only when music is requested.

    line 21
  4. Distinctive:

    Read references/routing.md and references/output-contract.md.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Visual Content

Designed, integrated, refactored, and continuously maintained by TIKAZ.

Inputs and routing

Accept the content or thesis, audience, publishing surface, required asset, factual sources, accessibility needs, and license boundary. Use one child Skill directly when writing cleanup, one illustration identity, or lawful music discovery is the whole task.

TIKAZ method

  1. Extract the content thesis, audience, publishing surface, visual jobs, claims, and accessibility needs.
  2. Use concise-writing-editor only when the source is padded or generic; preserve facts and author voice.
  3. Route to exactly one illustrator: xiaohei-article-illustrator or zhuge-logistics-illustrator.
  4. Create a shot card: message, scene/mechanism, composition, labels, character role, palette, forbidden elements, source assets, and license status.
  5. Review at publishing size for message clarity, text accuracy, character consistency, cropping, hierarchy, and alt text.
  6. Use legal-free-music only when music is requested; retain license and attribution evidence with the selected file.

Boundary

This suite intentionally excludes 生图-Image2. It defines content and QA workflows without requiring a specific image-generation provider.

Output, fallback, and limits

Return the selected route, shot or editing contract, source and license ledger, accessible text, publishing-size QA, and final asset or explicit creation handoff. If no drawing or generation tool is available, deliver an editable SVG/HTML specification or shot card rather than pretending an image was produced. Never turn uncertain labels or claims into definitive visuals.

Example

Use visual-content to clean this article, choose one illustration route, create a sourced shot card, and verify labels, licenses, alt text, and publishing-size clarity.

Read references/routing.md and references/output-contract.md.

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.

Check your setup, free