ollama

Documentation Community
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: Ollama API Documentation Comprehensive assistance with Ollama development - the local AI model runtime for running and interacti…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “When to Use This Skill”, “Quick Reference”, “1. Basic Chat Completion (cURL)”, “2. Simple Text Generation (cURL)”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name ollama directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “When to Use This Skill / Quick Reference / 1. Basic Chat Completion (cURL)” before expanding.

Boundaries And Review

  • Dependencies: Prepare Vendor-specific API keys before running a full task.
  • Permissions: Declared permissions include read / write / shell-exec / env-read; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.
Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates
Fluxly category
Documentation
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
85 / 100 · heuristic scan, not runtime safety proof
Author / version / license
@rawveg · no license declared
Fluxly token estimate
Lean
Fluxly setup estimate
Manual integration
External API key
Required · Vendor-specific
Detected OS requirements
macOS · Linux · Windows · Docker
Runtime requirements
Python · Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Detected network behavior
External requests
Install commands
None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools,默认拥有全部工具权限。; 上游仓库已 220 天未更新,可能与最新 agent 行为不一致。

Output preview ollama.preview
# 6. Structured Outputs (JSON Schema)

from pydantic import BaseModel
from openai import OpenAI

client = OpenAI(base_url="http://localhost:11434/v1", api_key="ollama")

class FriendInfo(BaseModel):
    name: str
    age: int
    is_available: bool

class FriendList(BaseModel):
    friends: list[FriendInfo]

completion = client.beta.chat.completions.parse(
    temperature=0,
    model="llama3.1:8b",
    messages=[
        {"role": "user", "content": "Return a list of friends in JSON format"}
    ],
    response_format=FriendList,
)

friends_response = completion.choices[0].message
if friends_response.parsed:
    print(friends_response.parsed)

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.