setup_skill
- TypeScript
5
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill andredezzy/maccing --skill setup- SKILL.md3.4 KB
Overview
This skill guides inline configuration when pictura tools return PICTURA_SETUP_REQUIRED or PICTURA_API_KEY_REQUIRED. It walks users through provider selection, secure API key collection, saving configuration, and automatically retrying the original pictura call. The flow supports reconfiguration and project-specific overrides.
How this skill works
When a pictura tool signals setup is required, the skill prompts the user to pick a provider (Gemini recommended or OpenAI), requests the provider API key without echoing it, and calls pictura_config to persist settings. It defaults to a user-scoped config unless the user explicitly requests a project-scoped override. After successful save, it retries the original pictura operation automatically.
When to use it
- A pictura tool returns PICTURA_SETUP_REQUIRED during generation, edit, or upscale.
- A pictura call returns PICTURA_API_KEY_REQUIRED because API keys are missing.
- You are starting pictura for the first time and need inline guidance to configure a provider.
- You want to switch providers or add an additional provider to pictura.
- You need to save project-specific defaults or override global settings.
Best practices
- Recommend Gemini by default (free tier, broad aspect ratio support) but offer OpenAI if preferred.
- Never echo or display the API key back to the user; confirm only that it was received and stored.
- Default to user scope for API keys unless the user explicitly requests project scope for overrides.
- Validate that the user pasted a non-empty key before calling pictura_config; handle failures with a clear retry prompt.
- After saving configuration, automatically retry the original tool call and report success or errors to the user.
Example use cases
- User asks to generate an image and pictura returns PICTURA_SETUP_REQUIRED; guide them to pick Gemini and paste the key, then regenerate the image.
- User has a user-level key but wants a project-specific override for different quality or ratio defaults; collect desired overrides and save with scope: project.
- User switched providers and needs to update the default generation provider; prompt which provider to make default and store its key securely.
- User lost access to a provider key and wants to reconfigure; collect new key and confirm configuration saved, then retry the previous operation.
FAQ
Gemini is recommended for free tier access and broader aspect ratio support; choose OpenAI if you prefer its performance or already have a key.
Will my API key be shown back to me?
No. The key is never echoed or displayed; you will receive only a confirmation that it was stored securely.
When should I use project scope instead of user scope?
Use project scope only when you need project-specific defaults or separate keys for a project. User scope is recommended for general API keys shared across projects.