Geepers Llm

Send requests to the dr.eamer.dev LLM API for chat completions, vision analysis, image generation, text-to-speech, and video generation across 12 model provi...

Security Scan

The skill's instructions clearly require an external API key and route requests to api.dr.eamer.dev (which matches the description), but the registry metadata fails to declare the required credential and other small inconsistencies leave unclear what will actually be used or stored.

Purpose & Capability

The SKILL.md describes a multi-provider LLM proxy (dr.eamer.dev) and the listed endpoints match that purpose. Minor inconsistency: the description text implies '12 model providers' while the 'Available Providers' list in the instructions shows 10 names. More importantly, the skill logically requires an API key for the proxy service (DREAMER_API_KEY) but the registry metadata declares no required environment variables or primary credential.

Instruction Scope

Runtime instructions explicitly instruct the agent to use an environment variable (DREAMER_API_KEY) and to POST requests to https://api.dr.eamer.dev and include X-API-Key. The instructions do not reference unrelated files or system paths, but they do reference an env var that the registry did not declare. That divergence means the agent may attempt to read an undeclared secret or the user may be unaware of the credential requirement.

Install Mechanism

No install spec and no code files — instruction-only skill. This is low-risk from an install/remote-code perspective because nothing is downloaded or written by an install step.

Credentials

The SKILL.md requires DREAMER_API_KEY for operation (and shows that API key is sent in X-API-Key), but the skill manifest lists no required env vars or primary credential. Requesting a single API key for the described proxy service is proportionate, but the manifest omission is an incoherence that could lead to accidental exposure or misconfiguration.

Persistence & Privilege

The skill does not request persistent/always-on presence (always:false) and does not declare actions that modify agent-wide configuration or other skills. Autonomy (disable-model-invocation:false) is the platform default and not a sole reason for concern here.

What to consider before installing

This skill is an instruction-only adapter for the third-party endpoint api.dr.eamer.dev and will send your prompts to that service. Before installing: (1) Be aware you need a DREAMER_API_KEY (the SKILL.md documents this) but the registry metadata does not declare it — confirm how and where to provide the key. (2) Treat it like any external LLM proxy: do not send sensitive data (passwords, secrets, personal data) unless you trust the operator and their data-handling policies. (3) Ask the publisher for source/homepage and for the missing required-env declaration so the manifest matches runtime instructions. (4) If you already have direct provider keys for the model you need, prefer calling those provider APIs directly (the skill itself even recommends that). If you want me to, I can draft questions to ask the publisher (e.g., data retention, logging, exact provider mapping) or help you verify the DREAMER_API_KEY usage.

Dreamer LLM

Access 12 LLM providers through a single unified API at https://api.dr.eamer.dev.

Authentication

Set your API key in an environment variable or pass it per-request:

export DREAMER_API_KEY=your_key_here

Get a key: email [e-mail] or visit https://dr.eamer.dev

Endpoints

Chat Completion

POST https://api.dr.eamer.dev/v1/llm/chat
Headers: X-API-Key: $DREAMER_API_KEY
Body:
{
  "model": "claude-sonnet-4-5-20250929",
  "messages": [{"role": "user", "content": "Hello"}],
  "provider": "anthropic"
}

Available Providers

anthropic, openai, xai, mistral, cohere, gemini, perplexity, groq, huggingface, ollama

List Models

GET https://api.dr.eamer.dev/v1/llm/models

Vision (image analysis)

POST https://api.dr.eamer.dev/v1/llm/vision
Body: { "model": "claude-sonnet-4-5-20250929", "image_url": "...", "prompt": "Describe this image" }

Image Generation

POST https://api.dr.eamer.dev/v1/llm/image
Body: { "prompt": "A sunset over the ocean", "provider": "openai" }

Text-to-Speech

POST https://api.dr.eamer.dev/v1/llm/tts
Body: { "text": "Hello world", "voice": "alloy" }

When to Use

• Comparing responses across multiple LLM providers
• Accessing providers you don't have direct API keys for
• Building applications that need multi-provider LLM access

Don't Use When

• You already have direct API keys for the provider you need
• You need streaming responses (use direct provider APIs instead)