> 核心功能: 本技能提供平台调优的社媒文案等能力。
Photo Captions
When the user shares a photo with context (location, camera, lens, film stock, subject, mood), generate captions for all platforms below in one response. Each platform has a distinct voice and format.
If the user specifies gear (camera body, lens, film stock, digital settings), include it where appropriate. Don't fabricate gear details the user didn't provide.
Platforms
- Tone: Short, grounded, specific. One strong observation about the scene. Skip the poetry — just say what you see or felt, plainly.
- Format: 1-2 line caption → blank line → gear line (if provided) → blank line → hashtags.
- Hashtags: Exactly 5 tags (Instagram's current limit). Pick the 5 most impactful: prioritize genre (e.g.
#filmphotography), location, film stock/gear, and one mood/style tag. Quality over quantity.
📷 Flickr
- Tone: Descriptive and contemplative. Flickr audiences appreciate story and craft.
- Format: Title (plain text, no markdown formatting — Flickr doesn't render it), dash, then 1-3 sentences of context/story. End with gear info.
- Include: Location context, what drew the photographer to the shot. Think photo essay voice.
🐦 X (Twitter)
- Tone: Punchy, concise, dry. Under 280 characters ideally. No hashtag spam.
- Format: One strong line about the image. Gear at the end if it fits naturally.
- Goal: Makes someone stop scrolling.
🪟 Glass
- Tone: Photographer-to-photographer. Understated, genuine. No hashtags, no engagement bait.
- Format: 1-3 sentences. Location and brief observation. Gear on a separate line with middle dots (·) as separators.
- Vibe: Like talking to a friend at a photo walk.
🟦 Tumblr
- Tone: More literary, expressive, slightly longer. Tumblr appreciates mood and storytelling.
- Format: Bold location as title. 2-4 sentences of narrative/reflection. Gear line. Then tags.
- Tags: Use spaces in Tumblr tags:
#film photographynot#filmphotography. 8-12 tags.
🔵 Bluesky
- Tone: Conversational, warm, community-minded. Similar energy to early Twitter.
- Format: 1-2 sentences, casual but thoughtful. Under 300 characters. Gear mention optional.
- No hashtags unless they add real value (Bluesky culture leans anti-hashtag-spam).
🧵 Threads
- Tone: Casual, Instagram-adjacent but more conversational. Think talking to followers, not curating a gallery.
- Format: 1-2 sentences, relaxed. Gear mention if interesting. No hashtags.
- Topic suggestion: After the caption, suggest a Threads topic (single word or short phrase, like "Film Photography", "Desert Southwest", "Street Photography") that best fits the post. Format it as:
Topic: [suggestion]
🔢 500px
- Tone: Technical and craft-focused. 500px is a photography-first community that values technique.
- Format: Title line, then 1-3 sentences covering the shot — technique, conditions, what made it work. Always include full gear details.
- Include: Camera settings, lighting conditions, or technique notes when available.
- Tone: Authentic, slightly self-deprecating, community-friendly. No self-promotion vibes, no precious language.
- Format: Post title (concise, descriptive) + comment body with context and gear.
- Title: Location or subject + gear in brackets, e.g.
Bombay Beach [Canon EOS 1V, Tri-X 400]. Keep it plain and factual — no clickbait phrasing, no dramatic adjectives in the title. - Comment: 2-3 sentences of context/story. Mention relevant subreddits: r/analog for film, r/photography for digital, r/streetphotography, r/LandscapePhotography, etc.
- Tone: Personal, conversational, like sharing with friends and family. Most accessible voice.
- Format: 2-3 casual sentences max — keep it short, Facebook audiences don't read walls of text. Story-driven — where you were, what you were doing, why it caught your eye. Gear mention only if it adds to the story.
- No hashtags (or 1-2 at most). Facebook audiences care about the story, not the craft.
🎞️ VSCO
- Tone: Minimal, poetic, understated. VSCO is the quiet gallery — let the image breathe.
- Format: 1 line max. Sometimes just a single word or short phrase. No hashtags.
- Vibe: Think whispered, not announced. VSCO captions are closer to titles than descriptions. The less you say, the better.
- No gear talk unless it's film stock and even then, keep it subtle.
📝 Substack
- Tone: Narrative, essayistic, author-voiced. Substack readers expect prose — this is a photo caption inside a long-form piece, not a social post.
- Format: 2-4 sentences that work as in-line caption text below a photo in a newsletter. Rich with context — where you were, what you noticed, why it stuck. Reads like a magazine photo caption crossed with a personal essay fragment.
- Include: Gear if it adds texture to the story. Location and conditions. The feeling behind the frame, not just the description of it.
- Vibe: Specific, unhurried, plain-spoken. Don't reach for literary effect — just say what happened and why it matters. The reader should feel like they're getting the real story, not a caption.
- No hashtags, no engagement bait, no calls to action.
- Tone: Descriptive and searchable. Pinterest is a discovery engine — think SEO meets aesthetics.
- Format: Two parts, both required:
- Title: Short, keyword-rich (5-10 words). Format:
[Subject/Mood] — [Location]or[Style] [Subject], [Location]. Examples: "Desert Road at Dusk, Amboy California" or "Film Photography, Mojave Desert Landscape" - Description: 2-3 sentences describing the scene, mood, and style. Include relevant keywords naturally (location, style, film stock if applicable, mood, themes like road trip, desert, americana, etc.)
- Goal: Someone searching "desert film photography" or "Route 66 aesthetic" should find this pin.
- No hashtags — Pinterest uses keywords in descriptions for discovery, not tags.
Edit Analysis
Always run the photo-edit-analysis skill alongside this one. After generating captions, deliver the edit analysis as a separate section titled 📊 Edit Analysis. Don't skip it, don't wait to be asked.
Guidelines
- Adapt all captions to the specific photo content, location, and mood.
- Don't repeat the same phrase across platforms. Each should feel native to its community.
- Don't start multiple captions with the same word or construction.
- Humor and wit are welcome but should match the photo's mood.
- If the photo is black and white, add relevant B&W tags where appropriate.
- Never be generic. Every caption should feel written specifically for that image.
- For film photos, lean into the analog aesthetic. For digital, focus on the moment and technique.
- If the user only wants specific platforms, generate only those.
- Write like a human, not a copywriter. No emdashes (—) anywhere, ever. No semicolons for drama, no overly polished prose. Use periods, commas, and natural sentence breaks. If you wouldn't say it out loud, don't write it. The middle dot (·) is fine for gear lines on Glass/Flickr/500px only.
Banned words and phrases
- "doing its thing", "golden hour doing its thing", "light doing its thing" — find a concrete description of what the light/fog/water is actually doing
- "captured" — say "shot", "took", "made" or just describe the scene directly
- "bathed in light" / "drenched in light" / "washed in light" — overused, find a specific alternative
- "timeless" / "fleeting moment" / "frozen in time" — stock photo clichés, never use
- "There's something about..." — vague filler opener, cut it
- "I found myself..." — sounds like a memoir, not a caption
- "Ever wonder..." / any rhetorical question opener — AI filler
- Starting a caption with "The [noun]..." or "A lone [noun]..." — stock photo voice
- "shot on [film/camera]" as a sentence opener — put gear info at the end, not the front
依赖说明
运行环境
- Agent平台: 支持SKILL.md的任意AI Agent( Code / Cursor / Codex / CLI等)
- 操作系统: Windows / macOS / Linux
依赖说明
| 依赖项 | 类型 | 是否必需 | 获取方式 |
|---|---|---|---|
| LLM API | API | 必需 | 由Agent内置LLM提供 |
API Key 配置
- 本Skill基于Markdown指令,无需额外API Key(除内容中明确标注的外部API)
可用性分类
- 分类: MD+execute(纯Markdown指令,部分功能需要exec命令行执行能力)
- 说明: 基于Markdown的AI Skill,通过自然语言指令驱动Agent执行任务
核心能力
- Generate platform-tuned social media captions for photography
- Use when
a user shares a photo and - 触发关键词: tuned, photo, generate, social, captions, platform, media
适用场景
| 场景 | 输入 | 输出 |
|---|---|---|
| 基础使用 | 用户请求 | 处理结果 |
不适用于：需要人工判断的复杂决策场景
使用流程
- 确认运行环境满足依赖说明中的要求
- 根据适用场景选择合适的使用方式
- 执行操作并检查输出结果
- 如遇错误，参考错误处理章节
示例
示例1：基础用法
输入: 用户请求
处理: 根据使用流程执行
输出: 处理结果
错误处理
| 错误场景 | 原因 | 处理方式 |
|---|---|---|
| 配置错误 | 参数缺失或格式错误 | 检查依赖说明中的配置要求 |
| 运行时错误 | 运行环境不满足 | 确认运行环境符合依赖说明 |
| 网络错误 | 连接超时或不可达 | 检查网络连接后重试，参考国内替代方案 |
常见问题
Q1: 如何开始使用Photo Captions？
A: 请先阅读使用流程章节，确认环境满足依赖说明中的要求。
Q2: 遇到错误怎么办？
A: 请参考错误处理章节，按照表格中的处理方式操作。
Q3: Photo Captions有什么限制？
A: 请参考已知限制章节了解具体限制。
已知限制
- 需要LLM支持，无LLM环境无法使用
- 复杂场景可能需要人工辅助判断
- 性能取决于底层模型能力
边界条件与限制
输入限制
- 图片内容: 该技能仅适用于用户分享的图片内容，不适用于版权受保护的媒体内容处理。
- 图片信息: 图片内容需包含足够的信息，如拍摄地点、相机、镜头、胶片类型、主题、情绪等，以便生成针对性的文案。
- 用户指定: 用户需明确指定所需生成的平台，若未指定，则默认生成所有支持平台的文案。
性能边界
- 处理速度: 该技能的响应速度取决于底层模型能力和运行环境，对于复杂的图片内容，处理时间可能较长。
- 输出长度: 每个平台的文案长度受限于平台特性，如Instagram的标签数量限制为5个。
兼容性约束
- 操作系统: 该技能支持Windows、macOS和Linux操作系统。
- Agent平台: 该技能支持SKILL.md的任意AI Agent，如 Code、Cursor、Codex、 CLI等。
- LLM支持: 该技能需要LLM支持，无LLM环境无法使用。
其他限制
- 复杂场景: 对于需要人工判断的复杂决策场景，该技能无法替代人工判断。
- 语言支持: 该技能目前仅支持英文，未来可能支持更多语言。
