一键导入
add-ollama-cloud-model
Add an Ollama Cloud model to models.json. Load when the user asks to add, configure, or set up an Ollama cloud model in pi.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Add an Ollama Cloud model to models.json. Load when the user asks to add, configure, or set up an Ollama cloud model in pi.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guidelines for creating or modifying pi.dev extensions in this repo (~/.pi). Load when the user asks to build, edit, debug, or refactor a pi.dev extension.
Review a GitHub PR and emit the findings as a markdown artifact (rendered HTML report in the browser). Use when the user asks to review a PR. Pairs with the gh skill (read-only diff) and the artifact tool (visual report).
Read-only GitHub CLI access via gh. Only commands that do not write, delete, or modify are allowed. Use when working with GitHub repos, issues, PRs, actions, releases, or other GitHub resources.
| name | add-ollama-cloud-model |
| description | Add an Ollama Cloud model to models.json. Load when the user asks to add, configure, or set up an Ollama cloud model in pi. |
The user will either provide a direct ollama.com URL or a model name.
fetch_contentfetch_content on https://ollama.com/search?q=<name>, find the closest matching result, then fetch that model's pageOn the model page, scan all available tags for entries ending in :cloud.
For each cloud variant collect:
qwen3.5:cloud, qwen3.5:397b-cloud)If no cloud variants are found, tell the user and stop.
If one cloud variant is found, proceed with it directly.
If multiple cloud variants are found, list them with their context window and input support, and ask the user which one(s) to add before proceeding.
Strip the :cloud or :<params>-cloud suffix and convert to title case.
Examples:
qwen3.5:cloud → Qwen 3.5qwen3.5:397b-cloud → Qwen 3.5 397Bllama3.3:70b-cloud → Llama 3.3 70BCheck if ~/.pi/agent/models.json exists. If not, create it with an empty providers object.
Merge the new model(s) into the ollama-cloud provider block. If the provider block doesn't exist yet, add it with this exact shape:
"ollama-cloud": {
"api": "openai-completions",
"apiKey": "!grep ^OLLAMA_API_KEY ~/.pi/agent/configs/.env | cut -d= -f2",
"baseUrl": "https://ollama.com/v1",
"compat": {
"supportsDeveloperRole": false
},
"models": []
}
Each model entry:
{
"id": "<full-cloud-tag>",
"name": "<derived name from step 3>",
"contextWindow": <value from model page>,
"input": <derived from model page capabilities>,
"reasoning": <true if model page explicitly states reasoning/thinking support, false otherwise>
}
For input: map all supported modalities listed on the model page (e.g. ["text"], ["text", "image"]). Do not assume — read what the page says.
For reasoning: only set true if the model page explicitly mentions thinking, reasoning, or a reasoning mode. Default to false if unclear.
Do not duplicate a model that is already present in the list.
Do not verify the API key or make any test API calls at this stage. Just update the models.json file and confirm to the user that the model was added successfully. Tell the user the model was added, then remind them of the two steps to start using it:
/scoped-models to enable the model/model to open the picker and switch to it