ollama-setup

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

85%

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

A well-structured, highly actionable body with a clear sequenced workflow, validation checkpoints, and properly signaled one-level references. The main weakness is redundancy (hardware sizing stated twice) and minor padding in the Output/Resources sections.

Suggestions

De-duplicate hardware/RAM requirements: state sizing once (e.g., in the model-selection step) and have Prerequisites reference it, rather than repeating the 8/16/32 GB tiers in both sections.

Trim the six-item Output list and remove the generic 'Hardware sizing guide' Resources entry that has no real link, keeping only concrete external references.

Reference the existing references/examples.md from the Examples section (or move the inline scenarios there) to reduce inline length and use the bundle file that is currently unreferenced.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and does not explain concepts Claude already knows, but RAM/hardware sizing is duplicated between Prerequisites and the Instructions model-selection list, the Overview restates the description, and the Resources section includes a generic non-link entry; it could be tightened, matching anchor 2.	2 / 3
Actionability	It provides dense, copy-paste-ready executable commands (brew install, curl install script, docker run, ollama pull/run, curl /api/tags) and specific model names with sizes, matching anchor 3.	3 / 3
Workflow Clarity	A clear 10-step numbered sequence includes explicit validation checkpoints (verify with 'ollama list'/'ollama run', confirm the REST API, validate latency) and a dedicated error-cause-to-solution table as a feedback loop, matching anchor 3.	3 / 3
Progressive Disclosure	The body is a clear overview with well-signaled one-level-deep references to references/skill-workflow.md and references/errors.md (both verified to exist), with detailed code snippets and extra error scenarios appropriately split out, matching anchor 3.	3 / 3
	Total	11 / 12 Passed

Description

90%

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

A strong description with good natural trigger coverage and a clear niche, weakened only by listing a single action verb and a duplicated 'Configure auto-configure' phrasing. It clearly answers both what the skill does and when to use it.

Suggestions

Fix the duplicated 'Configure auto-configure Ollama' to a single verb, and enumerate concrete actions (e.g., install, select models by hardware, integrate clients) instead of the single verb 'configure' to lift specificity.

Remove the generic filler 'Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.' — the explicit trigger phrases already convey this and the filler adds no signal.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Ollama", "local LLM deployment") and one action ("Configure ... Ollama") but does not list multiple concrete actions; the duplicated phrasing "Configure auto-configure Ollama" is also a specificity/quality flaw, placing it at anchor 2 rather than 3.	2 / 3
Completeness	It answers both what ("Configure ... Ollama ... local LLM deployment ... eliminate hosted API costs") and when via an explicit "Use when" clause plus concrete trigger phrases, so it is not capped at 2.	3 / 3
Trigger Term Quality	It lists six natural trigger phrases a user would actually say ("install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs"), giving good coverage matching anchor 3.	3 / 3
Distinctiveness Conflict Risk	The Ollama / local-LLM-hosting niche with dedicated triggers ("install ollama", "self-hosted AI") is distinct and unlikely to fire for unrelated skills, matching anchor 3.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 2cafb23

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.