Iván
作者:Iván更新日 2026-05-11全 5 バージョン · 最新版の公開日 2026-03-11image@clawhub_ivangdavila/image
画像生成画像編集ビジュアル素材

AlphaMoatによると、2026-10時点でImageのダウンロード数は60,396、スター数は40で、累計ダウンロード数で今回のランキング対象AIスキル10,914件中397位、デザイン・メディアでは1,116件中46位です。

一覧の初期表示は累計ダウンロード数順で、スター数順にも並べ替えできます。詳細ページの順位は累計ダウンロード数で計算しています。

ダウンロード数
6万
スター数
40
累計ダウンロード順位
#397
全体の上位 4% · デザイン・メディアの上位 5%
プラットフォームダウンロード数スター数コメント
ClawHub ↗2.3万30-
SkillHub ↗6万40—

プラットフォームごとに集計方法と集計時点が異なります。

このスキルでできること

リサイズ、切り抜き、圧縮、メタデータ、透明度、カラープロファイルの確認と処理を扱い、用途ごとの説明へ振り分けます。レスポンシブなウェブ、SNS の寸法、EC の商品画像が対象です。素材を早い段階で平坦化せず、ベクターやレイヤー、RAW のまま残すべきかを先に判断するよう促します。

資料公開日 2026-10-27

できること

  • ウェブや SNS の要件に合う寸法と形式で書き出す
  • 圧縮の前にカラープロファイルと透明部分を確認する

使う場面

  • 主な成果物が画像やビジュアル素材のとき
  • 複数プラットフォームの書き出し仕様を満たす必要があるとき

プロンプト例

スキルのドキュメントをもとに生成した例であり、実際の実行結果ではありません。

この画像をウェブ向けの形式で、容量を抑えて書き出してください
この商品画像の白背景と寸法がプラットフォームの要件を満たすか確認してください

月次の推移

ダウンロード数6万
1.6万4万6.4万2026-03 · ダウンロード数 1.9万2026-05 · ダウンロード数 2.6万2026-06 · ダウンロード数 2.8万2026-07 · ダウンロード数 2.9万2026-08 · ダウンロード数 3万2026-09 · ダウンロード数 3.4万2026-10 · ダウンロード数 6万26-0326-0926-10
スター数40
2433412026-03 · スター数 252026-05 · スター数 362026-06 · スター数 392026-07 · スター数 402026-08 · スター数 402026-09 · スター数 402026-10 · スター数 4026-0326-0926-10

2026-09 から集計方法を変更し、同名スキルを作者ごとに分けて集計し、全スキルを対象にしました。破線は変更前の月で、変更後のデータとは直接比較せず、変更をまたぐ増減も計算していません。 同名の別スキルがあるため、変更前のデータは現在ダウンロード数が最も多いこのスキルに帰属させています。

月ダウンロード数前月比スター数
2026-106万—40
2026-093.4万—40
2026-083万+3.4%40
2026-072.9万+4.8%40
2026-062.8万+7.3%39
2026-052.6万—36
2026-031.9万—25

SKILL.md 原文

作者が公開した元のファイルをテキストのまま表示しています。AlphaMoat による編集や審査はしていません。リンクはクリックできません。コマンドは内容を確認してから実行してください。取得日 2026-10-23。

14 KB・ClawHub v1.0.4
---
name: Image
slug: image
version: 1.0.4
homepage: https://clawic.com/skills/image
description: "Create, inspect, process, and optimize image files and visual assets with reliable format choice, resizing, compression, color-profile, metadata, and platform-export checks. Use when (1) the task is about images, screenshots, logos, product photos, or graphics; (2) resizing, converting, compressing, cropping, metadata, or export specs matter; (3) the asset must survive web, social, ecommerce, or print delivery without quality or format mistakes."
changelog: "Expanded the skill with branding, screenshot, accessibility, and richer platform-specific workflows while preserving stronger image-processing guidance."
metadata: {"clawdbot":{"emoji":"🖼️","os":["linux","darwin","win32"]}}
---
すべて表示(全 181 行)
## When to Use

Use when the main artifact is an image file or visual asset, especially when format choice, resizing, cropping, compression, metadata, transparency, color profile, responsive delivery, social specs, marketplace requirements, or print readiness matter.

If the task is destination-specific, load the matching file before deciding:
- `web.md` for responsive delivery, LCP/CLS, `srcset`, lazy loading, SVG, and modern web formats.
- `social.md` for platform dimensions, safe zones, and feed/story/banner exports.
- `ecommerce.md` for marketplace product-image rules, white backgrounds, zoom, and catalog consistency.
- `photography.md` for RAW, ICC profiles, print export, EXIF, and non-destructive editing.
- `branding.md` for logos, icons, favicons, app icons, SVG consistency, and small-size legibility.
- `screenshots.md` for UI captures, documentation images, annotations, redaction, and marketing/device frames.
- `accessibility.md` for alt text, decorative vs informative images, text in images, charts, and contrast-aware image delivery.
- `commands.md` when the user needs concrete ImageMagick or Pillow examples.

Keep the main workflow in this file, then pull in the specialized file for the exact delivery context instead of guessing from generic image advice.

## Quick Reference

| Situation | Load | Why |
|-----------|------|-----|
| Web optimization, responsive images, lazy loading, SVG | `web.md` | Avoid CLS/LCP mistakes, oversized assets, and wrong web formats |
| Color profiles, metadata, RAW, print, non-destructive workflows | `photography.md` | Protect color intent, print readiness, and master-file quality |
| Social platform dimensions, safe zones, banners, previews | `social.md` | Prevent unsafe crops, unreadable text, and uploader recompression surprises |
| Product photos, marketplace standards, catalog consistency | `ecommerce.md` | Preserve zoom detail, white-background compliance, and catalog consistency |
| Logos, favicons, SVGs, app icons, icon sets | `branding.md` | Protect small-size legibility, SVG consistency, and multi-format icon delivery |
| UI screenshots, docs captures, redaction, annotations | `screenshots.md` | Avoid blurry captures, privacy leaks, and misleading before/after comparisons |
| Alt text, text-in-image risk, charts, decorative vs informative images | `accessibility.md` | Keep image work usable and compliant, not only visually correct |
| ImageMagick and Pillow commands | `commands.md` | Use concrete commands once the export decision is already clear |

## Fast Workflow

1. Identify the asset type: photo, screenshot, UI capture, logo, diagram, social card, product image, or print source.
2. Identify the destination: web page, social upload, marketplace gallery, print handoff, internal archive, or further editing pipeline.
3. Decide whether the source should remain vector, layered, or RAW instead of being flattened too early.
4. Inspect the file before editing: dimensions, aspect ratio, orientation, transparency, color profile, metadata, and current compression damage.
5. Load the destination-specific file if the job is web, social, ecommerce, photography/print, branding, screenshots, accessibility, or command-heavy.
6. Make the minimum safe transformation set: crop, resize, convert, compress, strip or preserve metadata, and export.
7. Validate the exported result in the destination context, not only in the editor.

## Asset-Type Defaults

| Asset type | Usually best starting point | Watch out for |
|-----------|-----------------------------|---------------|
| Photo | WebP or AVIF for web, JPEG fallback, layered/RAW master for editing | Color profile shifts, overcompression, platform recompression |
| Product photo | JPEG or WebP for delivery, high-res clean master | White background, edge cleanup, zoom detail, consistency |
| Screenshot or UI capture | PNG or lossless WebP | JPEG blur, privacy leaks, unreadable text |
| Logo or simple icon | SVG master, PNG fallbacks only when needed | Tiny details, unsupported SVG pipelines, dark/light contrast |
| Social/OG card | PNG or high-quality JPEG sized for preview | Unsafe crop, tiny text, double compression |
| Diagram or chart | SVG when possible, PNG when fixed raster needed | Thin lines, low contrast, missing explanatory text |
| Print image | TIFF or high-quality JPEG with correct profile | Wrong profile, wrong physical size, no bleed |

## Core Rules

### 1. Choose the workflow by destination, not by habit

- Web delivery, social export, ecommerce prep, print output, and archive preservation are different image jobs.
- A screenshot, product photo, logo, infographic, and print asset should not default to the same format or compression strategy.
- Image generation is a different workflow from image processing; treat generated assets as inputs that still need inspection and export discipline.
- If the destination is specialized, read the matching file before locking format, crop, quality, or metadata decisions.
- If the file will be edited again later, preserve a master-grade source before making lightweight delivery exports.

### 2. Pick formats by content, not by trend

- Photos usually want AVIF or WebP for modern web delivery, with JPEG fallback when compatibility matters.
- Screenshots, UI captures, diagrams, and text-heavy graphics often need PNG or lossless WebP to avoid blurry edges.
- Logos, icons, and simple illustrations should stay vector (`.svg`) when the target supports it.
- Transparency changes the decision: JPEG drops alpha, while PNG, WebP, and AVIF can preserve it.
- Animated GIF is rarely the best output; animated WebP, MP4, or WebM are usually smaller and cleaner.
- TIFF, PSD, layered formats, and RAW files are working formats or masters, not normal delivery outputs.
- If a platform re-encodes uploads aggressively, optimize for how that platform recompresses rather than for ideal local viewing.
- Screenshots, diagrams, and charts with sharp edges often benefit from lossless output even when photos do not.

### 3. Preserve color, transparency, and detail deliberately

- Web assets should usually end in sRGB unless the destination explicitly needs something else.
- Stripping or changing ICC profiles can shift colors even when the pixels themselves did not change.
- Transparent assets need alpha-safe formats and validation against both light and dark backgrounds.
- Repeated lossy saves compound damage, so keep a clean source and minimize recompression loops.
- Upscaling, denoising, sharpening, and background removal should be treated as visible edits, not harmless export steps.

### 4. Resize, crop, and compress in the right order

- Decide aspect ratio first, crop second, resize third, and compress last.
- Do not upscale by default; extra pixels do not create missing detail.
- Retina or HiDPI exports should be intentional, not automatic overkill.
- As a starting point, 2x is the normal Retina export and 3x should be deliberate, not default.
- Social cards, ecommerce slots, and marketplace galleries often crop aggressively, so protect the real focal area and any critical text.
- A file that fits the pixel spec can still fail if the crop cuts off faces, products, labels, or UI affordances.
- If text is embedded inside the image, validate at the smallest realistic preview size, not only at full resolution.

### 5. Treat metadata and orientation as real delivery concerns

- EXIF orientation can make an image look upright in one viewer and rotated in another after export.
- Public web assets usually should strip GPS and unnecessary camera metadata.
- Copyright, author, or provenance metadata may need to be preserved for editorial, legal, or archive use.
- Metadata decisions are part of the workflow, not an afterthought.
- Preserve filenames and output naming conventions when downstream systems map assets by exact names or SKU patterns.
- Do not strip metadata blindly if the workflow depends on authoring info, rights data, timestamps, or orientation.

### 6. Use practical budgets and delivery defaults

- For web work, use budgets as a forcing function, not as decoration.
- A useful default starting point is: hero image under 200 KB, content image under 100 KB, thumbnail under 30 KB, raster icon under 5 KB.
- Reserve layout space with explicit dimensions or aspect ratio when the image ships on the web.
- Do not lazy-load the primary hero or likely LCP image.
- A file that "looks fine locally" is not finished if it breaks CLS, LCP, or responsive delivery in the real page.
- A small file is not automatically good if detail, text legibility, product edges, or gradients collapse.
- If a platform will recompress the image anyway, leave enough headroom that the second compression does not destroy the result.

### 7. Validate against the actual destination

- Platform specs are not interchangeable: web hero, social preview, app store art, marketplace gallery, and print ad all have different constraints.
- Ecommerce images may need background consistency, edge cleanliness, square-safe crops, and zoom-friendly detail.
- Social images need safe composition because feeds crop previews differently across platforms.
- Print assets care about physical size, bleed, and color handling in ways web exports do not.
- If the asset ships on the web, remember the surrounding delivery too: width, height, alt text, and whether the image should carry text at all.
- If the asset will be uploaded to a third-party platform, check the post-upload result because many pipelines resize, strip profiles, flatten metadata, or recompress again.
- If the image carries meaning, validate its accessibility too: alt text strategy, text legibility, decorative vs informative role, and whether the meaning should have stayed in HTML or surrounding copy.

### 8. Batch safely and keep the original reversible

- Work from originals or clean masters, not from already-optimized outputs.
- Batch processing should apply consistent rules, but still spot-check representative files before touching the whole set.
- One wrong crop preset, color conversion, or lossy export can damage an entire batch quickly.
- Keep per-destination exports separated from masters so the next edit does not accidentally start from a degraded derivative.

## Specialized Cases Worth Loading

- Load `branding.md` when the asset is a logo, app icon, favicon, social avatar, badge, or reusable icon set.
- Load `screenshots.md` when the asset is a UI capture, bug report image, tutorial screenshot, release-note image, or device-framed marketing visual.
- Load `accessibility.md` when the image needs alt text, contains embedded text, carries chart/diagram meaning, or may be decorative instead of informative.

## What Good Looks Like

- The chosen format matches the content and the destination, not a blanket preference.
- The exported file keeps the right focal area, text legibility, transparency, and color intent.
- Metadata is preserved or stripped deliberately.
- The file size is efficient without obvious visual damage.
- The asset still works after the actual upload, embed, or platform preview step.
- The agent has not flattened a vector, layered, or RAW source earlier than necessary.
- The asset is still understandable in its real use context, not just visually attractive in isolation.

## Common Traps

- Saving transparent images as JPEG and silently losing the alpha channel.
- Using JPEG for screenshots or UI captures and turning sharp text into mush.
- Shipping a file that matches the requested dimensions but has the wrong aspect ratio or unsafe crop.
- Recompressing the same JPEG multiple times and blaming the tool instead of the workflow.
- Stripping metadata and accidentally breaking orientation, licensing context, or provenance needs.
- Forgetting sRGB and wondering why colors shift between editing tools, browsers, and marketplaces.
- Using SVG where the target platform strips it, rasterizes it badly, or blocks it entirely.
- Assuming AVIF or WebP is safe everywhere when some platforms, email clients, or upload pipelines still normalize back to JPEG or PNG.
- Embedding critical text into images where HTML or native UI text should have carried the meaning.
- Hitting the file-size budget but missing visual quality because the image was resized, cropped, or sharpened badly.
- Rasterizing a logo too early and then fighting blurry exports forever.
- Shipping a screenshot with secrets, personal data, or unstable timestamps still visible.
- Treating alt text, captions, or chart summaries as someone else's problem after the pixels look good.

## Related Skills
Install with `clawhub install <slug>` if user confirms:
- `image-edit` — Masking, cleanup, inpainting, and targeted visual edits.
- `image-generation` — AI image generation and editing across current model providers.
- `photography` — Capture, color, and print-oriented photo workflows.
- `svg` — Vector graphics workflows when raster files are the wrong output.
- `ecommerce` — Marketplace and product-listing requirements that often constrain image delivery.

## Feedback

- If useful: `clawhub star image`
- Stay updated: `clawhub sync`

デザイン・メディアの人気スキル

视频短视频图片音乐音频配音口播数字人全能创作デザイン・メディア

通过同一个AI创作工具完成AI图片、视频、音乐与语音创作,查找公开社交数据,编辑视觉成果,并集中查看和管理生成资产。Beatra 全能创作支持AI图片生成(文生图)、AI视频生成(图生视频)和AI视频编辑,通过AI音乐生成把想法做成歌曲或纯音乐,也可用AI语音生成(文字转语音)、多语言旁白和AI语音克隆完成跨媒介内容;还能查找抖音数据、小红书数据,以及 YouTube、TikTok、Instagram 与 X 上的公开帖子、笔记、评论、账号和趋势,把社交媒体数据用于竞品调研和创作。它是一款面向AI内容创作与多模态内容创作的AI创作套件,用起来就是一个把图片、视频、音乐与语音收在同一处的AI创作助手,适用于社交内容、产品展示、营销素材、课程、播客、短片和跨媒介项目;还能在不同媒介间复用原始素材、已有成果和查到的公开资料,查看制作进度、返回文件、实际用量和积分记录。

↓ 147.6万★ 113u_319b171b
AI数字人口播与虚拟主播视频デザイン・メディア

用一张人像和一段短脚本或语音,制作有明确讲述内容的数字人口播视频。可使用现成录音,也可以先选择音色,把脚本生成旁白,让画面中的人物随声音完成稳定、自然的口播。适合 AI 主播、虚拟主播视频、数字人讲解、让照片说话、照片说话视频、产品讲解视频、数字人培训视频、公告和社交口播,并在交付后检查人物一致性、声音清晰度、口型同步和动作稳定性。一节课的讲解也能做成课程口播。

↓ 50.8万★ 39u_319b171b
架构图一键生成デザイン・メディア

ContextWeaveアーキテクチャ図ワンショット生成

↓ 47万★ 280user_bddf3fe6
海报设计工作室デザイン・メディア

将一段活动描述、一张产品照片或品牌参考图,转化为抓人眼球的活动海报、宣传 banner 或社交媒体配图。这款 AI海报设计与制作工具生成图片丰富的海报,在海报排版上搭配清晰视觉层级、按品类匹配的风格和预留文字区域,覆盖活动、音乐节、电影、产品发布和促销场景。你可以把它当作 AI宣传单制作工具来制作促销宣传单,当作活动海报设计工具,当作电影海报生成器,当作音乐节海报设计工具,当作产品发布会海报的 banner设计 AI,或当作平面设计海报工作室。从活动主题出发,用品牌风格参考图变换产品或场景照片,或在已认可草稿上做定向精修,完成可印刷或可分享的成品。

↓ 30.5万★ 28user_87b8e34f
自动化克隆数字人口播混剪视频デザイン・メディア

抖音短视频双路径生产体系(单 Skill 版)。Path A[付费·高质量]:策略大脑→(可选:素材混剪/AI高光提取)→脚本优化→AI生图/素材准备→配音渲染(百炼/GPT-SoVITS/CosyVoice/VoxCPM2+剪映/Remotion/ffmpeg/数字人)。Path B[免费·动画风]:采集热点→脚本→edge-tts免费配音+HyperFrames开源渲染→MP4,零云费开箱快。触发词分层:①"抖音短视频/选题规划/合规闸门/运营策略" ②"口播脚本/AI生图/AI配音/视频渲染/Remotion渲染" ③"蹭热点/快速出片/免费做视频" ④"混剪/高光提取/素材粗剪/autoclip

↓ 29.7万★ 79user_3b54b400
GPT Image 2.5生图デザイン・メディア

GPT Image 2.5生图是一款 AI 工具,用 GPT-Image-2.5 和 ChatGPT Images 2.5 出一张图。GPT Image 2.5 Studio 支持 gpt-image-2.5-flare 与 gpt-image-2.5-sunburst,可文生图或参考图生图,做中文海报、商品图、信息图和社媒画面。

↓ 27.1万★ 27user_87b8e34f
MiniMax H3 AI视频创作デザイン・メディア

用 MiniMax H3 这款 AI视频生成器创作高质感 2K AI 视频。从文字创意出发完成文生视频,让静态图片自然动起来,用首尾画面做首尾帧视频的完整转场,也可以结合图片、视频和音频参考,以多模态视频生成塑造统一场景。适合 AI 广告视频、电商产品视频、品牌宣传视频、动态海报、游戏 UI、电影片头和社交短视频创作,形成电影感画面与同步的原生立体声。使用 Beatra 账号即可开始,创作进度与成片集中管理。

↓ 26.3万★ 23user_87b8e34f
AI Logo设计·品牌标识创作デザイン・メディア

输入品牌名称、行业方向或参考图,生成专业 AI Logo、品牌标识和应用图标。这款 AI logo 设计工具从你的品牌简报出发——公司名、行业气质、配色偏好——先探索多个商标设计方向,再用精确品牌色、简洁几何和可缩放构图精修最强概念。制作企业 logo、创业公司标志、字母标、徽章、组合标识和 VI设计中的主标,从网站 favicon 到门头招牌都清晰可辨。从文字描述出发,将已有草图和品牌素材转化为精致标识,或在已认可草稿上做定向精修。

↓ 26万★ 19user_87b8e34f

Ivánのその他のスキル

データ月:2026-10 · ダウンロード数とスター数は公開スキルレジストリ(ClawHub、SkillHub)から月単位で集計しています。詳しくはデータの方法論をご覧ください。