CtrlK
BlogDocsLog inGet started
Tessl Logo

add-ollama-tool

Add Ollama MCP server so the container agent can call local models and optionally manage the Ollama model library.

61

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/add-ollama-tool/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable, copy-paste-ready guidance and a well-sequenced, validated workflow; it is mostly lean and well-structured, with only minor over-explanation and no use of separate reference files.

DimensionReasoningScore

Conciseness

The body is largely efficient with executable code blocks and minimal concept padding; it does explain a few integration specifics (e.g. the credential-lane rationale, shared-block note) that slightly exceed what is strictly necessary, fitting the 'efficient; minor trimmable over-explanation' anchor rather than a clean 5.

4 / 5

Actionability

Provides copy-paste-ready bash and TypeScript snippets for every step (cp commands, the exact mcpServers entry, the env spread, the stderr branch, .env.example additions, validation commands), covering the common cases concretely and completely.

5 / 5

Workflow Clarity

Four clearly sequenced phases (Pre-flight, Apply, Configure, Verify) with explicit validation checkpoints ('All must be clean before proceeding', wiring/registration tests) and a Troubleshooting section providing feedback loops for error recovery.

5 / 5

Progressive Disclosure

Well-organized into clear sections/phases with appropriate use of inline code and an opt-in advanced branch (management tools); however there are no separate reference files and some larger code blocks (registration/env wiring) are inlined where the rubric would reward cleaner splitting, leaving it just below the score-5 anchor.

4 / 5

Total

18

/

20

Passed

Description

57%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly conveys what the skill does and is reasonably specific and distinct, but it lacks an explicit 'Use when...' trigger clause and has only partial natural-keyword coverage.

Suggestions

Add an explicit 'Use when...' clause naming the natural triggers (e.g. 'Use when the user wants to use local Ollama models, run inference offline, or manage the Ollama model library').

Broaden trigger-term coverage with synonyms users actually say, such as 'offline models', 'self-hosted LLM', or 'run models locally'.

Optionally surface 1-2 concrete tool actions (e.g. list models, generate responses) to lift specificity toward the comprehensive anchor.

DimensionReasoningScore

Specificity

Names the domain (Ollama MCP server, local models, model library) and concrete actions ('call local models', 'optionally manage the Ollama model library'), but stops short of listing multiple distinct operations like list/generate/pull/delete; minor coverage gaps versus the score-5 anchor.

4 / 5

Completeness

The 'what' is clearly stated (adds an MCP server exposing local Ollama models and optional library management), but there is no explicit 'Use when...' clause or equivalent trigger guidance for when Claude should invoke it, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes relevant terms like 'Ollama', 'local models', 'MCP server', and 'model library', but omits common natural variations a user might say (e.g. 'offline models', 'self-hosted LLM', 'ollama tools') and any file-extension-like trigger, so keyword coverage is partial.

3 / 5

Distinctiveness Conflict Risk

The Ollama/local-models niche is fairly specific and unlikely to collide with unrelated skills, with only minor overlap risk against other local-model tool skills, fitting the 'mostly distinct' anchor.

4 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
nanocoai/nanoclaw
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.