CtrlK
BlogDocsLog inGet started
Tessl Logo

upgrade-deps

Follow the upstream plugin template and OBS version for this plugin.

55

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/upgrade-deps/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is a well-organized, concise, multi-step upgrade workflow with concrete commands and a useful troubleshooting feedback loop, held back only by a few under-specified action details and missing inter-step validation.

Suggestions

Make the version-finding and hash steps fully executable, e.g. give the git/gh tag command and the sha256 computation command for the OBS source zip.

Add an explicit validation checkpoint after the merge step (e.g. 'cmake --preset windows-x64 --fresh' succeeds before committing) to convert the workflow into a validate-then-proceed loop.

Specify the exact JSON keys to edit in CMakePresets.json and buildspec.json so the version/hash update is copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, omitting explanations of what OBS/CMake are and using tight step lists with concrete paths and commands, so every token earns its place per the 'lean and efficient' anchor.

3 / 3

Actionability

It provides concrete URLs, file paths (CMakePresets.json, buildspec.json) and copy-paste cmake commands, but leaves gaps such as 'search for tags to find the latest release version' and unspecified hash computation, fitting the 'some concrete guidance but incomplete; missing key details' anchor rather than fully copy-paste ready.

2 / 3

Workflow Clarity

Steps are clearly sequenced and the troubleshooting section gives a real feedback loop with recovery commands, but intermediate steps (merge resolution, version bump, deps update) lack validation checkpoints, and the judging guidelines cap destructive/batch workflows without validation at 2.

2 / 3

Progressive Disclosure

The skill is under 50 lines, single-purpose, needs no external references, and is organized into clearly labeled sections (Update the plugin template, Update OBS version, Update the OBS deps, Try build, Troubleshooting), which the scoring notes allow to score 3.

3 / 3

Total

10

/

12

Passed

Description

50%

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 a single vague sentence that names the right domain but gives no trigger guidance and uses abstract language, leaving it mediocre across all dimensions.

Suggestions

Rewrite in third person with concrete actions, e.g. 'Upgrades the OBS plugin template and OBS Studio dependency version for this plugin, resolving merge conflicts and updating CMakePresets/buildspec hashes.'

Add an explicit 'Use when...' trigger clause, e.g. 'Use when upgrading OBS plugin dependencies, syncing with the upstream obs-plugintemplate, or bumping the OBS Studio version.'

Include natural trigger terms users would say ('upgrade dependencies', 'update OBS version', 'sync plugin template') alongside the existing jargon.

DimensionReasoningScore

Specificity

Names a concrete domain ('upstream plugin template', 'OBS version') and an action ('Follow'), but 'Follow ... for this plugin' is abstract and not a comprehensive list of actions, matching the 'names domain and some actions' anchor rather than the vague 'Helps with' level or the multi-action level.

2 / 3

Completeness

It states what the skill does ('Follow the upstream plugin template and OBS version') but provides no 'Use when...' trigger guidance, so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

'OBS version' is a natural term a user would say, but 'upstream plugin template' is jargon and common variations like 'upgrade', 'update', or 'deps' are missing, fitting the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

It targets a fairly specific OBS-plugin niche, but the generic 'Follow ... for this plugin' wording could overlap with other plugin-upkeep skills, matching the 'somewhat specific but could still overlap' anchor rather than a clearly distinct trigger set.

2 / 3

Total

8

/

12

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
sorayuki/obs-multi-rtmp
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.