plugins/maccing-pictura/skills/setup/SKILL.md
Use when pictura returns PICTURA_SETUP_REQUIRED or PICTURA_API_KEY_REQUIRED. Guides inline configuration during first use.
npx skillsauth add andredezzy/maccing pictura-setupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill handles inline configuration when pictura tools detect missing configuration.
PICTURA_SETUP_REQUIRED returned from pictura_generate, pictura_edit, or pictura_upscalePICTURA_STOCK_SETUP_REQUIRED returned from pictura_stock_searchPICTURA_API_KEY_REQUIRED returned when config exists but API keys are missingWhen a pictura tool returns a setup required message, guide the user through configuration inline.
Ask the user which provider they want to use:
"I need to configure Pictura before generating images. Which provider would you like to use?
| Provider | Pros | API Key | |----------|------|---------| | Gemini (Recommended) | Free tier available, supports all 10 aspect ratios | Get key | | OpenAI | Fast, reliable, limited to 3 sizes | Get key |
Which provider would you like to use?"
After provider selection, ask for the API key:
"Please paste your [Provider] API key.
Get one at: [provider URL]
(The key will be stored securely with 600 permissions)"
Important: Never echo back or display the API key in responses.
Call pictura_config with the collected information:
pictura_config({
providers: {
generation: {
default: "gemini",
gemini: { apiKey: "user-provided-key" }
}
},
scope: "user"
})
Scope selection:
user scope (shared across projects, recommended for API keys)project scope only if user explicitly requests project-specific configAfter successful configuration, automatically retry the original pictura tool call that triggered setup.
User: Generate an image of a sunset
Claude: [calls pictura_generate]
Tool returns: PICTURA_SETUP_REQUIRED
Claude: I need to configure Pictura first. Which provider would you like to use?
- Gemini (recommended, free tier)
- OpenAI
User: Gemini
Claude: Please paste your Gemini API key.
Get one at: https://aistudio.google.com/apikey
User: [pastes API key]
Claude: [calls pictura_config with the key]
Claude: Configuration saved. Now generating your image...
Claude: [calls pictura_generate again with original prompt]
If user wants to reconfigure or add additional providers:
pictura_config with the updatesFor project-specific overrides:
pictura_config({
defaults: { quality: "draft", ratio: "1:1" },
scope: "project"
})
| Scope | Path | Purpose |
|-------|------|---------|
| user | ~/.claude/plugins/maccing/pictura/config.json | API keys, shared across projects |
| project | .claude/plugins/maccing/pictura/config.json | Project-specific overrides |
Precedence: Environment variables > Project scope > User scope > Defaults
Note: Generated images always output to .claude/plugins/maccing/pictura/output/ in the project directory, regardless of config scope. This ensures images are project-local assets.
When PICTURA_STOCK_SETUP_REQUIRED is returned, guide the user through stock provider configuration:
| Provider | Pros | API Key | |----------|------|---------| | Unsplash (Recommended) | Highest quality, free tier | Get key | | Pexels | Free, no attribution required | Get key | | Pixabay | Free, large library | Get key |
pictura_config({
providers: {
generation: { default: "gemini" },
stock: {
default: "unsplash",
unsplash: { apiKey: "user-key" }
}
},
scope: "user"
})
Multiple stock providers can be configured at once for cross-provider search.
tools
YCloud — a multi-channel communications provider (CPaaS: WhatsApp, SMS, Voice, Email), not a Meta-only BSP. This skill covers its WhatsApp Business operations: console navigation, plans/pricing, Embedded Signup, campaigns/inbox/journeys, auto-unsubscribe chatbot, the public-API-vs-dashboard-backend distinction, BSP migration, and read-only CDP automation. Use when operating YCloud for WhatsApp dispatch: plans, embedded signup, campaign sends, campaign analytics, inbox, auto-unsubscribe chatbot, opt-out attribution, dashboard automation, or comparing YCloud to other providers. Triggers on: 'ycloud', 'CPaaS', 'BSP', 'bulk campaign', 'whatsapp dashboard', 'embedded signup', 'auto-unsubscribe', 'opt-out chatbot', 'campaign analytics', 'dispatch automation', 'provider comparison', 'ycloud free plan', 'zero markup'.
development
WhatsApp Business Platform (Cloud API) production reference for the maccing growth stack. Covers Cloud API setup, message types, templates (creation, approval, pacing, strategy), per-message pricing, webhooks, bulk sending at scale, WhatsApp Flows, media handling, Node.js/TypeScript SDK, error codes, compliance (LGPD, opt-in/opt-out), Calling API, MM Lite, Business Management API, business profile fields, dispatch operations (chip warming, direct API setup, BSP migration, number longevity), and 2025-2026 platform changes. Use when the user asks about whatsapp, whatsapp api, cloud api, WABA, BSP, whatsapp template, whatsapp marketing, message template, WhatsApp dispatch, WhatsApp number quality, WhatsApp Brazil, WhatsApp opt-in, WhatsApp webhook, WhatsApp flows, WhatsApp pricing, or anything related to sending or receiving WhatsApp messages via the Cloud API.
tools
Meta Ads (Facebook + Instagram) production reference. Use when managing Meta/Facebook/Instagram ad campaigns, creating ads, CAPI setup, audience targeting, creative testing, or automating via Marketing API. Triggers on "meta ads", "facebook ads", "instagram ads", "CAPI", "conversions API", "meta pixel", "advantage+", "lookalike audience", "custom audience", "meta campaign", "facebook campaign", "ad set", "ad creative", "click-to-whatsapp", "CTWA".
development
Use when user wants to verify, validate, test, or check if pictura is working correctly. Also triggers for troubleshooting, debugging, or diagnosing pictura issues.