agentleFS
clairelily2020clairelily2020/creator-workflows/skills/comic-preflight/SKILL.md

comic-preflight

Skill0 starsChanged 21 days agoMITView on GitHub

Run a final publishing checklist for comics, carousels, short videos, storyboards, covers, and visual storytelling assets. Use before publishing or handing off final files.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    No accidental private notes, prompt fragments, or draft comments.

    line 20
  2. Distinctive:

    No obvious generation artifacts in important areas.

    line 28
  3. Distinctive:

    Do not pretend to verify files you cannot inspect.

    line 87
  4. Distinctive:

    If only a description is provided, clearly mark checks that need the actual file.

    line 88
  5. Distinctive:

    If the platform is unknown, check common formats and ask where it will publish.

    line 89

≈ “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

Comic Preflight

Catch avoidable publishing problems before the asset goes out.

This is a final check. If the story or storyboard itself is weak, route back to comic-review.

Checks

Content

  • First panel or first seconds create a reason to continue.
  • Story setup is understandable without extra explanation.
  • Ending beat is clear.
  • Captions or subtitles have no placeholders.
  • No accidental private notes, prompt fragments, or draft comments.

Visual

  • Character design stays consistent.
  • Important text is readable on mobile.
  • Cover or first frame is legible at small size.
  • Color and lighting are consistent enough for the format.
  • No obvious generation artifacts in important areas.

Format

  • Aspect ratio matches the target platform.
  • Resolution is high enough.
  • File type is accepted by the platform.
  • Duration fits the intended channel.
  • Safe area is respected for captions and UI overlays.

Audio And Captions

  • Audio is present if expected.
  • Loudness is reasonable.
  • Captions are synced.
  • Captions do not cover key faces or action.
  • Licensed music or audio rights are clear.

Publishing

  • Title supports the hook.
  • Description does not over-explain.
  • Hashtags or tags are limited and relevant.
  • CTA is clear if needed.
  • Final files are archived.

Output Format

## Preflight: {asset}

Target platform:
{platform or format}

Status:
{clear to publish / publish after fixes / blocked}

Blockers:
- {issue and fix}

Fix before publishing:
- {issue and fix}

Passed checks:
- {selected checks}

Final export notes:
- aspect ratio: {value}
- resolution: {value}
- duration: {value}
- file type: {value}

Next step:
{publish / fix and rerun preflight / return to review}

Rules

  • Be strict about unreadable text, wrong aspect ratio, and broken captions.
  • Do not pretend to verify files you cannot inspect.
  • If only a description is provided, clearly mark checks that need the actual file.
  • If the platform is unknown, check common formats and ask where it will publish.

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.