openwork-models

Manage OpenWork inference model aliases, openwork model overlays, discounts, validation, and automated base model refreshes from models.dev. Use when adding, removing, discounting, auditing, or updating OpenWork models, including requests like "update the models" that should trigger the GitHub update-models workflow and report when its PR merges.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%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 body is exemplary across all dimensions: concise, fully executable, clearly sequenced workflows with explicit validation and failure feedback, and a clean overview structure backed by real one-level-deep script references. No actionable weaknesses found.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: terse sections with executable commands, no padding or re-explanation of concepts Claude already knows, and every token (e.g., the domain-specific 'usage factor' definition) earns its place.	5 / 5
Actionability	Fully executable, copy-paste-ready commands for every common case (search, add, remove, discount, sync, validate, trigger workflow) plus a concrete TS alias block, covering the common cases specifically.	5 / 5
Workflow Clarity	Multi-step workflows (Add/Remove/Discount/Update) are clearly sequenced with an explicit validation section ('Before finishing, run validate + build-models.mjs') and feedback loops for failure (unmerged PR / workflow failure reported with URLs).	5 / 5
Progressive Disclosure	SKILL.md is a well-organized overview with one-level-deep references to real bundled scripts (all three referenced .mjs files exist in ./scripts/), no nested references, and bulk logic correctly kept out of the body.	5 / 5
	Total	20 / 20 Passed

Description

92%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 is strong: it names concrete actions, provides explicit 'Use when' trigger guidance with realistic user phrasing, answers both what and when, and is clearly scoped to a niche. The only minor gap is a few missing natural synonym variations, keeping trigger_term_quality at 4.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Manage OpenWork inference model aliases, openwork model overlays, discounts, validation, and automated base model refreshes' plus 'adding, removing, discounting, auditing, or updating'), giving comprehensive coverage rather than a single generic verb.	5 / 5
Completeness	Explicitly answers both 'what' (manage aliases, overlays, discounts, validation, refreshes) and 'when' ('Use when adding, removing, discounting, auditing, or updating OpenWork models, including requests like "update the models"'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural trigger coverage with verbatim user phrasing ('update the models') and verb-based triggers (adding, removing, discounting, auditing, updating), but lacks a few synonymous variations a user might say; not a full 5-anchor match.	4 / 5
Distinctiveness Conflict Risk	A clear niche scoped to OpenWork inference model management, with domain-specific triggers unlikely to fire for unrelated skills, matching the distinct niche anchor.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: different-ai/openwork
Path: .opencode/skills/openwork-models/SKILL.md
Commit: 7b76a2b

Reviewed: 3 days 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.