agentleFS
gokulsvisiongokulsvision/Crewm8-Social-Media-Manager-Skill-Graph/skills/visual/asset-format/SKILL.md

asset-format

Skill17 starsChanged 7 months agoMITView on GitHub

Enforce platform-specific image and video dimensions — X 16:9, Instagram 4:5 or 1:1, LinkedIn 4:5, TikTok 9:16 — plus safe zones, resolution targets, and file format guidance.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Every platform displays images differently.

    line 25
  2. Distinctive:

    Before exporting any image or video for social

    line 29
  3. Distinctive:

    All platforms: avoid bottom 10-15% for key content

    line 75
  4. Distinctive:

    All 6 slides must share the same 4:5 ratio

    line 148

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

Asset Format

Enforce correct dimensions, aspect ratios, and safe zones for every visual asset on every platform. Wrong dimensions mean cropped images, blurry posts, and a brand that looks amateur. This skill is the single source of truth for visual specs.

Purpose

Every platform displays images differently. The same image that looks perfect on X gets cropped badly on LinkedIn. This skill eliminates guesswork by providing exact specs per platform, content type, and asset format — so every visual lands correctly.

When to Use

  • Before exporting any image or video for social
  • Visual plan, meme, or image prompt needs dimension guidance
  • Founder sends a raw image: "Format this for X"
  • Auditing existing posts for formatting issues

Inputs Required

  • Target platform
  • Content type (feed post, story, banner, carousel, video, link preview)
  • Source asset dimensions (if resizing an existing image)

Quick Reference

Image Dimensions

PlatformAspect RatioResolutionBest For
X (feed)16:91200x675 or 1600x900General posts, quote cards
X (link preview)1.91:11200x628Link preview cards
IG Feed (portrait)4:51080x1350Carousels, primary posts
IG Feed (square)1:11080x1080General feed posts
IG Stories / Reels9:161080x1920Stories, Reels
LinkedIn Feed4:5 or 1.91:11200x1500 (4:5)Carousels, single images
LinkedIn Banner~3.33:11584x396Profile header
TikTok9:161080x1920All videos

Video Specifications

PlatformAspect RatioMax DurationMax SizeCodec
X video16:9 or 1:12:20 (premium longer)512MBH.264
IG Reels9:1690 sec4GBH.264
LinkedIn video16:9 or 1:110 min5GBH.264
TikTok9:1610 minVariesH.264

Procedure

  1. Identify the platform and content type. Feed post? Story? Banner? Carousel? Video? Thumbnail?
  2. Select dimensions from the Quick Reference table.
  3. Check safe zones:
    • X feed: rounded corners — keep critical content away from edges
    • IG feed: profile icon + UI elements overlay bottom-left — avoid text there
    • LinkedIn: "see more" cut — first 2 caption lines matter most
    • TikTok: UI (likes, comments) overlays right and bottom edges — keep content in center 80%
    • All platforms: avoid bottom 10-15% for key content
  4. Specify export settings:
    • Image: PNG for graphics with text (lossless), JPG for photos (quality 85-95%)
    • Video: MP4, H.264, 30fps, captions embedded
  5. If source asset is wrong aspect ratio:
    • Recommend cropping (specify what to crop)
    • Or extending with blurred background fill
  6. Provide the format checklist for the exact asset type.

Output Format

# Asset Format: [Asset Name]

## Platform: [X / LinkedIn / IG / TikTok]
## Content Type: [Feed / Story / Banner / Carousel / Video]

### Specifications
- **Aspect ratio:** [e.g., 4:5]
- **Resolution:** [e.g., 1080x1350 px]
- **File format:** [PNG / JPG / MP4]
- **File size limit:** [Platform max]

### Safe Zones
- **Top:** [N]px margin
- **Bottom:** [N]px margin (UI overlay risk)
- **Left:** [N]px margin
- **Right:** [N]px margin
- **Center safe area:** [Effective usable area]

### Source Asset Adjustment
[Cropping/extension notes if source is different ratio]

### Export Settings
- **Format:** [PNG/JPG/MP4 settings]
- **Color space:** sRGB
- **Compression:** [Level or bitrate]

Done Criteria

The skill is complete when:

  1. Dimensions match the target platform and content type
  2. Safe zones are documented (including platform UI overlays)
  3. File format and export settings are specified
  4. Any source asset adjustments are stated (crop, extension, fill)

Pitfalls

  • Designing at the wrong aspect ratio and cropping critical content
  • Forgetting platform UI overlays cover part of the image
  • Exporting at too-low resolution (blurry on high-DPI screens)
  • Exporting at too-high file size (platform compression destroys quality)
  • Carousels where slide 1 has a different ratio than slides 2-5 (platform rejects it)

Verification

Preview at platform display size (30-50% of screen width to simulate feed view). Is text readable? Are key elements in the safe zone? Export a test post in draft mode and review on mobile.

Example

Input: LinkedIn carousel. 6 slides. Source text: "3 signs your pricing is wrong."

Output:

  • Aspect ratio: 4:5
  • Resolution: 1200x1500 px per slide
  • Format: PNG (graphics with text)
  • Safe zones: top 10% + bottom 15% clear (LinkedIn UI + action buttons overlay the bottom)
  • Center safe area: 75% of image height — put all text here
  • Export: sRGB, PNG-24
  • All 6 slides must share the same 4:5 ratio

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.