model-researcher
Add new/custom AI models to opencode.json. Use proactively for bleeding-edge releases, non-standard providers, self-hosted models, or custom endpoints. Examples: - user: "Add the new Claude 4.5" → websearch for API specs, add provider entry with baseUrl, verify model ID format - user: "Use my local Ollama instance" → configure custom provider with http://localhost:11434, set model ID format - user: "Configure this OpenAI-compatible proxy" → add provider with custom baseUrl, set apikey env var, verify compatibility - user: "Model X just released, add it" → research provider documentation, find model ID and capabilities, add to config
What this skill does
# Model Researcher
Add new or custom AI models to opencode.json with verified specifications.
<critical_prohibition>
## EXTREMELY STRICT: Banned Legacy Models
The following models MUST NOT be used in any configuration as they are DEPRECATED, REPLACED, or OBSOLETE in the current Q4 2025 market:
- **OpenAI**: GPT-o series (`o1-mini`, `o1-preview`), GPT-4o, GPT-4 Turbo.
- **Anthropic**: Claude 3.5 series (`sonnet-3.5`, etc.), Claude 3 series.
- **Google**: Gemini 1.5 series, Gemini 2 series.
- **Meta**: Llama 3 series.
The market has moved to **GPT-5.2**, **Claude 4.5**, and **Gemini 3**. Any attempt to configure these models MUST be rejected.
</critical_prohibition>
<when_to_use>
- Model is too new for models.dev
- Non-standard or custom provider (self-hosted, proxy, enterprise)
- User heard about a new release and wants to use it immediately
- Model exists but with non-default configuration needs
</when_to_use>
<question_tool>
**Batching:** Use the `question` tool for 2+ related questions. Single questions → plain text.
**Syntax:** `header` ≤12 chars, `label` 1-5 words, add "(Recommended)" to default.
When to ask: Vague model reference, multiple providers available, or specs unverified.
**Critical:** MUST confirm specs with user before applying model configuration.
</question_tool>
<critical_rule>
## Verify Before Configure
**MUST NOT hallucinate model specifications.** Models have precise identifiers, context limits, and API requirements. A wrong value means broken requests or wasted tokens.
Before ANY configuration:
1. Confirm the model actually exists
2. Find the exact model identifier (API name, not marketing name)
3. Get verified context and output token limits
4. Identify required provider configuration
</critical_rule>
<workflow>
## Step 1: Clarify What the User Wants
Ask if unclear:
- "Which provider will you access this through?" (direct API, OpenRouter, Together, self-hosted, etc.)
- "Do you have API access already, or do you need setup help?"
## Step 2: Research the Model
Use web search to find authoritative sources:
```
websearch("${MODEL_NAME} API context limit tokens official documentation")
websearch("${MODEL_NAME} model ID API identifier ${PROVIDER}")
```
**Priority sources (most to least trustworthy):**
1. Official provider documentation/blog posts
2. Provider's API reference or changelog
3. Official GitHub repos or release notes
4. OpenRouter/Together model pages (they list specs)
5. Reputable tech news (for very new announcements)
**Red flags - search more if you only find:**
- Reddit speculation
- Tweets without official confirmation
- Your own training data (MAY be outdated)
## Step 3: Confirm Findings with User
Before touching config, MUST present your research:
```
I found the following for [MODEL]:
Provider: OpenAI
Model ID: gpt-5.2-2025-12-11
Context limit: 400000 tokens (Direct) | 272000 tokens (OAuth)
Output limit: 128000 tokens
Special options: [e.g., reasoning modes, vision support]
Source: [URL]
Does this match what you expected? Should I add this to your config?
```
**MUST NOT proceed without user confirmation.**
## Step 4: Apply Configuration
Read the current config first:
```
read ~/.config/opencode/opencode.json
```
Then apply using surgical edits. Choose the right pattern:
### Pattern A: GPT-5.2 (OpenAI)
OpenAI GPT-5.2 supports specialized reasoning modes via `variants` (Cycle with `ctrl+t`). Note that models configured via OAuth plugins (e.g., `opencode-openai-codex-auth`) often have different enforced limits.
```jsonc
{
"provider": {
"openai": {
"models": {
"gpt-5.2": {
"limit": { "context": 400000, "output": 128000 }, // Use 272000 for OAuth
"variants": {
"pro": {
"reasoningEffort": "xhigh",
"reasoningSummary": "detailed",
},
"thinking": { "reasoningEffort": "high" },
"instant": { "reasoningEffort": "low", "textVerbosity": "low" },
},
},
"gpt-5.2-codex": {
"limit": { "context": 400000, "output": 128000 }, // Use 272000 for OAuth
},
},
},
},
}
```
### Pattern B: Other Labs (DeepSeek, Zhipu, MiniMax, Moonshot)
For labs using OpenAI-compatible or Anthropic-compatible endpoints (Verified Q4 2025):
```jsonc
{
"provider": {
"deepseek": {
"npm": "@ai-sdk/openai-compatible",
"name": "DeepSeek",
"options": { "baseURL": "https://api.deepseek.com" },
"models": {
"deepseek-v3.2": { "limit": { "context": 128000, "output": 32768 } },
},
},
"zhipu": {
"npm": "@ai-sdk/openai-compatible",
"name": "Zhipu AI (ZAI)",
"options": { "baseURL": "https://api.z.ai/api/paas/v4" },
"models": {
"glm-4.7": { "limit": { "context": 200000, "output": 128000 } },
},
},
"minimax": {
"npm": "@ai-sdk/openai-compatible",
"name": "MiniMax",
"options": { "baseURL": "https://api.minimax.chat/v1" },
"models": {
"minimax-m2.1": { "limit": { "context": 204800, "output": 128000 } },
},
},
"moonshot": {
"npm": "@ai-sdk/openai-compatible",
"name": "Moonshot AI (Kimi)",
"options": { "baseURL": "https://api.moonshot.cn/v1" },
"models": {
"kimi-k2-thinking": { "limit": { "context": 256000, "output": 64000 } },
},
},
},
}
```
### Pattern C: Claude 4.5 Opus (Extended Thinking)
For models that need specific options like Anthropic's extended thinking:
```jsonc
{
"provider": {
"anthropic": {
"models": {
"claude-4-5-opus-thinking": {
"id": "claude-4-5-opus-20251124",
"name": "Claude 4.5 Opus (Extended Thinking)",
"options": {
"thinking": {
"type": "enabled",
"budgetTokens": 32000,
},
},
},
},
},
},
}
```
## Step 5: Validate
After editing, remind user to test:
```
Config updated. To verify it works:
1. Restart OpenCode or run: opencode
2. Run /models and select [model name]
3. Send a test message
If you see errors, check:
- API key is set (run /connect if needed)
- Model ID matches provider's documentation exactly
- Context limits aren't higher than the model actually supports
```
</workflow>
<research_queries>
| Scenario | Search Query |
| ------------------------ | ------------------------------------------------------- |
| New OpenAI model | `"gpt-5.2" site:openai.com OR site:platform.openai.com` |
| New Anthropic model | `"claude-4.5" site:anthropic.com API` |
| New Google model | `"gemini 3" site:ai.google.dev context window` |
| OpenRouter availability | `"${MODEL}" site:openrouter.ai` |
| Together AI availability | `"${MODEL}" site:together.ai` |
| Self-hosted specs | `"${MODEL}" context length output tokens huggingface` |
</research_queries>
<spec_checklist>
Before configuring, ensure you have:
- [ ] **Model ID**: Exact API identifier (not marketing name)
- [ ] **Context limit**: Maximum input tokens
- [ ] **Output limit**: Maximum output/completion tokens
- [ ] **Provider**: Which service hosts it
- [ ] **Base URL**: For custom providers only
- [ ] **Special options**: Vision, reasoning modes, thinking budgets
- [ ] **Availability**: Is it actually accessible (not waitlist-only)?
</spec_checklist>
<handling_uncertainty>
If you cannot verify specifications:
1. **Be honest**: "I couldn't find official documentation for the exact context limit."
2. **Provide best guess with source**: "Based on [source], it appears to be 128k, but this isn't confirmed."
3. **Suggest conservative defaults**: "I'll configure with 100k context as a safe starting point. You can increase it once you confirm the actual limit."
4. **Recommend checking**: "Try the provider'sRelated in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.