openloomi-lifestyle-image
Identify whether a user is asking OpenLoomi to generate a lifestyle image, portrait, personal visual, or lifestyle scene. Use this skill for chat messages that may request image generation for a user's lifestyle, identity, persona, personal brand, social profile, memories, interests, or real-life scene; distinguish true generation intent from ordinary image understanding, prompt-writing, editing, or negated requests.
git clone --depth 1 https://github.com/melandlabs/openloomi /tmp/openloomi-lifestyle-image && cp -r /tmp/openloomi-lifestyle-image/skills/openloomi-lifestyle-image ~/.claude/skills/openloomi-lifestyle-imageSKILL.md
# OpenLoomi Lifestyle Image
## Purpose
Decide whether the user is asking to generate a lifestyle image through OpenLoomi's existing lifestyle image flow. This skill only judges intent and prepares a decision signal for the host app. Do not call image generation providers from this skill.
## Decision
Return a lifestyle image generation decision only when the user clearly wants OpenLoomi to create or generate a lifestyle-oriented image.
Use `matched: true` when the request asks to generate, create, make, draw, design, render, or produce a lifestyle image, personal visual, avatar-like lifestyle scene, personal brand image, social profile visual, or life-scene image based on the user's profile, memory, interests, chat context, or uploaded reference image.
Use `matched: false` when the user is only asking to:
- Analyze, identify, describe, OCR, classify, or understand an uploaded image.
- Write or improve a prompt without asking to generate the image now.
- Edit an existing image without asking for lifestyle generation.
- Discuss image generation conceptually.
- Say not to generate an image, or says image generation is unnecessary.
- Ask an unrelated design, document, code, or chat question.
## Reference Images
Set `hasReferenceImage: true` when the current user message includes an uploaded image that appears intended as style, subject, persona, or visual reference for generation.
Do not set `matched: true` only because an image was uploaded. If the user asks what the image shows, who the character is, or asks for image understanding, return `matched: false`.
If the user uploads a reference image and also asks to generate a lifestyle image from or inspired by it, return `matched: true` and `hasReferenceImage: true`.
## Output Contract
When the host requests a structured decision, return only JSON with this shape:
```json
{
"matched": true,
"confidence": "high",
"reason": "explicit_lifestyle_image_generation_request",
"hasReferenceImage": false,
"refinedPrompt": "optional concise generation intent"
}
```
Rules:
- `matched` must be boolean.
- `confidence` must be `high`, `medium`, or `low`.
- Use `confidence: "high"` only when the user clearly wants generation now.
- Use `confidence: "medium"` when lifestyle generation is plausible but underspecified.
- Use `confidence: "low"` with `matched: false` for ordinary chat or image understanding.
- `reason` should be a short snake_case string.
- `hasReferenceImage` must be boolean.
- `refinedPrompt` is optional and should preserve the user's intent without inventing new identity details.
## Examples
User: "Generate a lifestyle image for my LinkedIn profile based on my interests."
Decision: `matched: true`, `confidence: "high"`, `hasReferenceImage: false`.
User: "Use this photo as a style reference and create a lifestyle portrait."
Decision: `matched: true`, `confidence: "high"`, `hasReferenceImage: true`.
User: "What character is in this image?"
Decision: `matched: false`, `confidence: "low"`, `hasReferenceImage: false`.
User: "Help me write a prompt for a lifestyle image."
Decision: `matched: false`, `confidence: "low"`, `hasReferenceImage: false`.
User: "Do not generate an image, just describe the idea."
Decision: `matched: false`, `confidence: "low"`, `hasReferenceImage: false`.Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
Drive a native macOS app via the cua-driver CLI (default) or MCP server — snapshot its AX tree, click/type/scroll by element_index, verify via re-snapshot. Use when the user asks you to operate, drive, automate, or perform a GUI task in a real macOS application on the host (e.g. "open a file in TextEdit", "navigate to /Applications in Finder", "click the Save button in Numbers").
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of "Word doc", "word document", ".docx", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a "report", "memo", "letter", "template", or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
openloomi HTTP API reference (local-first, served from the OpenLoomi Desktop app at http://localhost:3414). Use when working with openloomi backend routes — auth, AI, files, integrations, RAG, memory, Loop, pet, workspace, platform callbacks. Triggers: API endpoints, backend routes, /api/*, local API, port 3414, integrations REST, OAuth start, RAG search, loop state, memory search, pet state, audit logs
openloomi Connectors tools - manage the native 7 messaging integrations and pair with the composio skill for the 1000+ apps OAuth layer (Slack, Discord, X, Gmail, Outlook, Google Calendar/Drive/Docs, GitHub, Notion, Linear, HubSpot, LinkedIn, Jira, Asana). Triggers: connect platform, integration status, list accounts, disconnect, list-accounts, status, connect, send-reply, native vs composio, 1000+ apps, list connections.
Use this when users ask about openloomi features, capabilities, or how to use it. Examples: 'openloomi 怎么用', '你能做什么', 'What can you do?', 'How does openloomi work?', 'Tell me about openloomi features', 'What platforms does openloomi support?', 'How do I use scheduled tasks?', 'What is Loop?', 'How does the attention agent work?', 'What is a Decision Card?', 'How do connectors work?', 'How do I extend Loop with custom types?', 'What is a classifier rule?', 'How do I plug openloomi into Claude Code / Codex?'
openloomi Memory tools - search and manage the holistic context (people, projects, decisions, knowledge base, chat insights). Triggers: memory search, knowledge base, search documents, list insights, who is John, what did we decide about X, tiered memory, knowledge graph, people/projects/decisions, search-all, conversation memory