pp-ollama-cloud
Routes every prompt to the right hosted Ollama model. Wraps chat, embeddings, catalog, and the OpenAI-compatible... Trigger phrases: `pick an ollama model`, `advise on a model`, `which ollama cloud model should I use`, `route this prompt`, `use ollama cloud`, `run ollama cloud`.
What this skill does
<!-- GENERATED FILE — DO NOT EDIT.
This file is a verbatim mirror of library/ai/ollama-cloud/SKILL.md,
regenerated post-merge by tools/generate-skills/. Hand-edits here are
silently overwritten on the next regen. Edit the library/ source instead.
See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->
# Ollama Cloud — Printing Press CLI
## Prerequisites: Install the CLI
This skill drives the `ollama-cloud-pp-cli` binary. **You must verify the CLI is installed before invoking any command from this skill.** If it is missing, install it first:
1. Install via the Printing Press installer. It defaults binaries to `$HOME/.local/bin` on macOS/Linux and `%LOCALAPPDATA%\Programs\PrintingPress\bin` on Windows:
```bash
npx -y @mvanhorn/printing-press-library install ollama-cloud --cli-only
```
2. Verify: `ollama-cloud-pp-cli --version`
3. Ensure the reported install directory is on `$PATH` for the agent/runtime that will invoke this skill.
If the `npx` install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.3 or newer):
```bash
go install github.com/mvanhorn/printing-press-library/library/ai/ollama-cloud/cmd/ollama-cloud-pp-cli@latest
```
If `--version` reports "command not found" after install, the runtime cannot see the binary directory on `$PATH`. Do not proceed with skill commands until verification succeeds.
## When to Use This CLI
Pick this CLI when you need agent-driven access to Ollama's hosted catalog and want routing intelligence baked in. Especially useful when the alternative is hardcoding a model name and hoping it stays right. Pairs naturally with multi-backend setups where ollama-cloud is one of several providers.
## Unique Capabilities
These capabilities aren't available in any other tool for this API.
### Routing intelligence
- **`advise`** — Picks the right Ollama Cloud model for a prompt by combining live catalog, heuristic prompt-feature extraction, curated cost/latency metadata, and an optional cheap meta-LLM tiebreak.
_When an agent needs to pick a hosted Ollama model and the default routing is wrong, reach for advise instead of hardcoding the model name._
```bash
ollama-cloud-pp-cli advise --prompt-file ./prompt.txt --task-hint coding --budget-remaining-usd 0.50 --json
```
- **`compare`** — Runs the same prompt against N hosted models in parallel and emits side-by-side response, tokens, and latency.
_Use when calibrating advisor recommendations or picking between two close models._
```bash
ollama-cloud-pp-cli compare --prompt-file ./p.txt --models qwen3-coder:480b,gpt-oss:120b,deepseek-v3.1:671b --json
```
- **`advise`** — With --explain, advise emits the full scoring trace: feature extraction, per-model scores, filter passes, tiebreak rationale.
_Reach for this when an advise recommendation surprises you and you want to understand why._
```bash
ollama-cloud-pp-cli advise --prompt-file ./p.txt --explain --format md
```
### Engagement canary
- **`advise-replay`** — Replays advisor recommendations and reports divergence between recommended models and actually-chosen models. Foundation for the divergence canary; the prompt corpus is not retained so judge-LLM scoring is not in scope until a corpus sidecar ships.
_Run weekly to detect advisor drift; surfaces divergence between recommended and actual-chosen models._
```bash
ollama-cloud-pp-cli advise-replay --since 7d --diverge-only --json --select rows,divergence_count,divergence_pct
```
### Operations
- **`budget`** — Probes the free-tier weekly cap with a 1-token chat. Parses Ollama Cloud's 429 prose and emits a structured verdict (ok | exhausted | unknown) with the upgrade URL so agents can pre-flight quota before launching long sessions.
_Run before launching a long agent session to confirm quota is available._
```bash
ollama-cloud-pp-cli budget --json
```
- **`cost-trace`** — Aggregates advisor-log cost estimates over a time window; compares per-model and per-task-hint spend.
_Use to decide whether to upgrade to a paid Ollama Cloud tier._
```bash
ollama-cloud-pp-cli cost-trace --since 7d --group-by task-hint --json
```
## Command Reference
**chat** — Manage chat
- `ollama-cloud-pp-cli chat chat` — Native Ollama chat endpoint. Supports streaming.
- `ollama-cloud-pp-cli chat completions` — OpenAI-compatible chat completions endpoint.
**embeddings** — Manage embeddings
- `ollama-cloud-pp-cli embeddings embed` — Native Ollama embeddings endpoint.
- `ollama-cloud-pp-cli embeddings openai-embed` — Generate embeddings (OpenAI-compatible)
**models** — Manage models
- `ollama-cloud-pp-cli models` — Catalog in OpenAI list-models format.
**ps** — Manage ps
- `ollama-cloud-pp-cli ps` — Shows currently-loaded models. On Ollama Cloud this typically reflects models with active sessions.
**show** — Manage show
- `ollama-cloud-pp-cli show` — Returns model metadata, template, modelfile, capabilities.
**tags** — Manage tags
- `ollama-cloud-pp-cli tags` — Returns the live catalog of hosted Ollama Cloud models.
### Finding the right command
When you know what you want to do but not which command does it, ask the CLI directly:
```bash
ollama-cloud-pp-cli which "<capability in your own words>"
```
`which` resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code `0` means at least one match; exit code `2` means no confident match — fall back to `--help` or use a narrower query.
## Recipes
### Advise with explain trace as markdown
```bash
ollama-cloud-pp-cli advise --prompt-file ./prompt.txt --task-hint coding --explain --format md
```
--explain populates the feature trace and filtered-candidate audit; --format md renders for humans.
### Detect catalog drift
```bash
ollama-cloud-pp-cli advise --validate-catalog --json --select uncurated_live,curated_not_in_live
```
Diffs live /api/tags against curated models.json overlay; flags both uncurated live models and stale curated patterns.
### Replay last week recommendations
```bash
ollama-cloud-pp-cli advise-replay --since 7d --dry-run --json --select divergence_count,divergence_pct,emitted
```
Engagement canary; dotted-path select keeps response under context budget.
### Side-by-side comparison
```bash
ollama-cloud-pp-cli compare --prompt-file ./prompt.txt --models qwen3-coder:480b,gpt-oss:120b --json
```
Runs the prompt against both models in parallel and reports per-model latency, tokens, and rate-limit state.
### Cost rollup by task hint
```bash
ollama-cloud-pp-cli cost-trace --since 7d --group-by task-hint --json --select groups,row_count
```
Aggregates the advisor JSONL log by task-hint so you can decide whether to upgrade the Ollama Cloud tier.
## Auth Setup
Bearer auth via OLLAMA_CLOUD_API_KEY (intentionally distinct from any local-Ollama env var). Free tier is rate-limited weekly; the budget command surfaces exhaustion before workflows fail.
Run `ollama-cloud-pp-cli doctor` to verify setup.
## Agent Mode
Add `--agent` to any command. Expands to: `--json --compact --no-input --no-color --yes`.
- **Pipeable** — JSON on stdout, errors on stderr
- **Filterable** — `--select` keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
```bash
ollama-cloud-pp-cli chat chat --model example-value --agent --select id,name,status
```
- **Previewable** — `--dry-run` shows the request without sending
- **Offline-friendly** — sync/search commands can use the local SQLite store when available
- **Non-interactive** — never prompts, every input is a flag
- **Explicit retries** — use `--idempotent` only when an already-existing create should count as success
### Response envelope
Commands that read from the local store or the API wrap output in a provenance envelope:
```json
{
"meta": {"sourceRelated in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.