Name: uscreen
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

uscreen

Uscreen integration. Manage data, records, and automate workflows. Use when the user wants to interact with Uscreen data.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/uscreen/SKILL.md

Quality

Content

76%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 CLI commands and a clean connection-state workflow, and is reasonably concise. Its main gap is the absence of validation/verification steps around running actions and proxying destructive requests, which caps workflow clarity.

Suggestions

Add a verification checkpoint before/after destructive action runs or proxy DELETE/PUT calls (e.g. confirm the target id, then re-fetch to verify the result).

Trim the introductory 'Uscreen is a platform...' paragraph and the 'so you can focus on integration logic' aside to save tokens.

Consider moving the 22-item entity list and the request-flags table into a references file to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight code blocks, a flags table, and short procedural steps, with only minor over-explanation (the 'Uscreen is a platform...' intro and the 'so you can focus on integration logic' aside) that could be trimmed, matching 'Efficient; minor instances of over-explanation.'	4 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure, action list/run, request proxy) with a complete flags table and JSON examples, matching 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases.'	5 / 5
Workflow Clarity	The connection flow is well sequenced with state polling and clientAction checkpoints, but executing actions and proxy requests (including DELETE) against live Uscreen data has no validation/verification step; per the rubric cap, destructive/batch workflows without validation cannot exceed 3.	3 / 5
Progressive Disclosure	Sections are well organized with clear headers and the skill is self-contained, but at ~157 lines with no bundle files the inline entity list and flags table could be split into a reference, matching 'Good structure; most content appropriately placed; minor organization gaps.'	4 / 5
	Total	16 / 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 correctly uses third person and includes an explicit 'Use when' trigger, but its capability language is generic ('manage data, records, automate workflows') rather than naming concrete Uscreen operations. Trigger coverage relies almost entirely on the proper noun 'Uscreen' and would benefit from domain-specific synonyms.

Suggestions

Replace generic verbs with concrete Uscreen actions, e.g. 'Create and manage customers, subscriptions, orders, collections, and coupons.'

Add natural trigger terms users actually say, such as 'video streaming', 'subscribers', 'memberships', or 'Uscreen storefront'.

Tighten the 'Use when' clause to cite specific intents, e.g. 'Use when the user wants to manage Uscreen customers, content, or subscriptions.'

Dimension	Reasoning	Score
Specificity	Names the Uscreen domain but its actions are minimal and generic ('Manage data, records, and automate workflows') rather than concrete operations, matching the anchor 'Names the domain but actions are minimal or generic.'	2 / 5
Completeness	It explicitly states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Uscreen data'), with the 'when' present but somewhat generic, matching 'Has both what and when; when could be more explicit or specific.'	4 / 5
Trigger Term Quality	It surfaces the natural keyword 'Uscreen' and 'interact with Uscreen data', but misses common synonyms a user would say (streaming, video, customers, subscriptions), matching 'Some relevant keywords but missing common variations or synonyms.'	3 / 5
Distinctiveness Conflict Risk	'Uscreen integration' targets a single named platform, giving a clear niche with minimal conflict risk, but the generic 'data, records' phrasing leaves minor overlap with adjacent integration skills, matching 'Mostly distinct; minor overlap risk.'	4 / 5
	Total	13 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/uscreen/SKILL.md
Commit: f484c82

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.