Skip to main content
ClaudeWave
ES, Spanish
Skill1k estrellas del repoactualizado 1mo ago

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.

Instalar en Claude Code
Copiar
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-image
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.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`.
agent-browserSkill

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.

composioSkill

Use 1000+ external apps via Composio - either directly through the CLI or by building AI agents and apps with the SDK

connectSlash Command

Walk the user through installing the optional composio skill and turning on screen memory

continual-learnSkill

Persist learning across turns by actively maintaining MENTAL_MODEL.md in the workspace. Use for iterative coding, debugging, benchmarking, or any feedback-driven task; read and update the file with actual filesystem writes before every response, never just hidden/internal memory.

create-taskSkill

Create an end-to-end Continual Learning Bench task. Use when adding a new src/tasks/<name> benchmark task, including design interview, concrete Jinja prompt templates, JSON action contracts, observation templates, debug schedule, behavioral E2E tests, validation, smoke/debug runs with icl and icl_notepad, and README documentation.

cua-driverSkill

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").

data_analysisSkill

High-performance data analysis using Polars - load, transform, aggregate, visualize and export tabular data. Use for CSV/JSON/Parquet processing, statistical analysis, time series, and creating charts.

docxSkill

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.