據 AlphaMoat 統計,截至 2026-10,Image 累計下載 60,396 次、獲 40 個星標,按累計下載量在本次參與排名的 10,914 個 AI 技能中排名第 397 位,在「設計創意」分類(1,116 個)中排名第 46 位。
列表預設按累計下載量排序,也可按星標排序;詳情頁排名按累計下載量計算。
| 平台 | 累計下載 | 星標 | 評論 |
|---|---|---|---|
| ClawHub ↗ | 2.3萬 | 30 | - |
| SkillHub ↗ | 6萬 | 40 | — |
各平台的計數口徑不同,統計時間不一致。
覆蓋縮放、裁剪、壓縮、後設資料、透明與色彩配置的檢查與處理,並按交付場景查閱對應說明:響應式網頁、社媒尺寸、電商商品圖。它建議先判斷素材是否該保留為向量、分層或 RAW,而不是過早壓平。
資料釋出於 2026-10-27
以下是根據技能文件生成的示例,不代表實際執行結果。
2026-09 起統計方法調整:同名技能按作者分別統計,並覆蓋全部技能。圖中虛線為調整前的月份,與之後的資料不直接比較,也不計算跨越調整的增長。 該技能有同名的其他版本,調整前的資料歸屬當前下載量最大的這一個。
| 月份 | 累計下載 | 環比 | 星標 |
|---|---|---|---|
| 2026-10 | 6萬 | — | 40 |
| 2026-09 | 3.4萬 | — | 40 |
| 2026-08 | 3萬 | +3.4% | 40 |
| 2026-07 | 2.9萬 | +4.8% | 40 |
| 2026-06 | 2.8萬 | +7.3% | 39 |
| 2026-05 | 2.6萬 | — | 36 |
| 2026-03 | 1.9萬 | — | 25 |
以下是作者釋出的原始檔案,按純文字顯示,本站未做修改或稽核;其中的連結不可點選,命令請核實後再執行。抓取於 2026-10-23。
---
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"]}}
---
## 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創作助手,適用於社交內容、產品展示、行銷素材、課程、播客、短片和跨媒介專案;還能在不同媒介間複用原始素材、已有成果和查到的公開資料,檢視製作進度、返回檔案、實際用量和積分記錄。
用一張人像和一段短指令碼或語音,製作有明確講述內容的數位人口播影片。可使用現成錄音,也可以先選擇音色,把指令碼生成旁白,讓畫面中的人物隨聲音完成穩定、自然的口播。適合 AI 主播、虛擬主播影片、數位人講解、讓照片說話、照片說話影片、產品講解影片、數位人培訓影片、公告和社交口播,並在交付後檢查人物一致性、聲音清晰度、口型同步和動作穩定性。一節課的講解也能做成課程口播。
ContextWeave 架構圖一鍵生成
將一段活動描述、一張產品照片或品牌參考圖,轉化為抓人眼球的活動海報、宣傳 banner 或社交媒體配圖。這款 AI海報設計與製作工具生成圖片豐富的海報,在海報排版上搭配清晰視覺層級、按品類匹配的風格和預留文字區域,覆蓋活動、音樂節、電影、產品釋出和促銷場景。你可以把它當作 AI宣傳單製作工具來製作促銷宣傳單,當作活動海報設計工具,當作電影海報生成器,當作音樂節海報設計工具,當作產品釋出會海報的 banner設計 AI,或當作平面設計海報工作室。從活動主題出發,用品牌風格參考圖變換產品或場景照片,或在已認可草稿上做定向精修,完成可印刷或可分享的成品。
抖音短影片雙路徑生產體系(單 Skill 版)。Path A[付費·高質量]:策略大腦→(可選:素材混剪/AI高光提取)→指令碼最佳化→AI生圖/素材準備→配音渲染(百鍊/GPT-SoVITS/CosyVoice/VoxCPM2+剪映/Remotion/ffmpeg/數位人)。Path B[免費·動畫風]:採集熱點→指令碼→edge-tts免費配音+HyperFrames開源渲染→MP4,零雲費開箱快。觸發詞分層:①"抖音短影片/選題規劃/合規閘門/營運策略" ②"口播指令碼/AI生圖/AI配音/影片渲染/Remotion渲染" ③"蹭熱點/快速出片/免費做影片" ④"混剪/高光提取/素材粗剪/autoclip
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,可文生圖或參考圖生圖,做中文海報、商品圖、資訊圖和社媒畫面。
用 MiniMax H3 這款 AI影片生成器創作高質感 2K AI 影片。從文字創意出發完成文生影片,讓靜態圖片自然動起來,用首尾畫面做首尾幀影片的完整轉場,也可以結合圖片、影片和音訊參考,以多模態影片生成塑造統一場景。適合 AI 廣告影片、電商產品影片、品牌宣傳影片、動態海報、遊戲 UI、電影片頭和社交短影片創作,形成電影感畫面與同步的原生立體聲。使用 Beatra 賬號即可開始,創作進度與成片集中管理。
輸入品牌名稱、行業方向或參考圖,生成專業 AI Logo、品牌標識和應用圖示。這款 AI logo 設計工具從你的品牌簡報出發——公司名、行業氣質、配色偏好——先探索多個商標設計方向,再用精確品牌色、簡潔幾何和可縮放構圖精修最強概念。製作企業 logo、創業公司標誌、字母標、徽章、組合標識和 VI設計中的主標,從網站 favicon 到門頭招牌都清晰可辨。從文字描述出發,將已有草圖和品牌素材轉化為精緻標識,或在已認可草稿上做定向精修。
將使用者明確糾正與自我檢視整理成分層記憶,並依使用情況升級或封存。
在保留公式、格式和活頁簿結構的前提下建立、檢查或編輯 Excel 檔案。
處理 Word 與 DOCX 文件的作業指南,著重維持樣式、編號與版面。
面向多家影片模型 API 的 AI 影片生成與編排技能。
把資料庫、表格與匯出的原始資料變成可決策結論的資料分析技能。
資料月份:2026-10 · 下載/星標數聚合自公開技能註冊庫(ClawHub、SkillHub),按月更新。口徑說明見資料方法。