Name: dacast
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

dacast

Dacast integration. Manage Videos, Playlists, Channels. Use when the user wants to interact with Dacast data.

Quality

74%

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/dacast/SKILL.md

Quality

Content

75%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 highly actionable with executable commands and a well-validated connection workflow, but it opens with unnecessary background and keeps a large action reference inline that would benefit from a separate file.

Suggestions

Remove or trim the introductory "Dacast is a video streaming platform..." paragraph and the "so you can focus on the integration logic" commentary.

Label the post-connection section as "Step 2" (or remove the "skip to Step 2" phrasing) so the cross-reference resolves.

Move the 20-row Popular actions table into a references file (e.g. ACTIONS.md) and link to it from the body.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening "Dacast is a video streaming platform..." paragraph and phrases like "so you can focus on the integration logic rather than auth plumbing" explain context Claude does not need, matching the level-3 anchor of mostly-efficient-with-some-unnecessary-explanation.	3 / 5
Actionability	It supplies copy-paste-ready bash commands for every common case (install, login, connection ensure/get, action list/run, proxy request) with flag tables, matching the fully-executable level-5 anchor.	5 / 5
Workflow Clarity	The connect→wait→search→run sequence includes explicit state validation (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but the dangling "skip to Step 2" reference (no labeled Step 2) is a minor checkpoint gap that keeps it below 5.	4 / 5
Progressive Disclosure	No bundle files exist, so scoring is against structure: clear section headers organize the content well, but the 20-row Popular actions table is inline reference material that could live in a separate file, the minor organization gap characteristic of level 4.	4 / 5
	Total	16 / 20 Passed

Description

73%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 cleanly answers both what and when in third person and targets a distinct platform, but relies on the generic verb "Manage" and a broad when-clause rather than concrete actions and trigger phrases.

Suggestions

Replace the generic "Manage" with concrete verbs, e.g. "List, create, update, and delete Videos, Playlists, and Channels".

Tighten the when-clause with concrete triggers, e.g. "Use when the user wants to list, search, or manage Dacast videos, live streams, playlists, or channels".

Add "live streams" alongside Videos/Playlists/Channels to match the full action surface shown in the body.

Dimension	Reasoning	Score
Specificity	"Manage Videos, Playlists, Channels" names the Dacast domain plus three target entities, but the single generic verb "Manage" is not the concrete action language (extract/fill/merge) of the level-4 anchor, so it sits at level 3 rather than 4.	3 / 5
Completeness	It states both what ("Manage Videos, Playlists, Channels") and when ("Use when the user wants to interact with Dacast data"), but the when-clause is generic rather than the concrete trigger phrases required for level 5.	4 / 5
Trigger Term Quality	"Videos, Playlists, Channels" plus "Dacast" are natural terms a user would say, giving good keyword coverage; it stops short of level 5 only because synonyms like "live streams" or "broadcast" are absent.	4 / 5
Distinctiveness Conflict Risk	"Dacast integration" targets a specific named platform with distinct triggers, giving a clear niche and minimal overlap with other skills.	5 / 5
	Total	16 / 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/dacast/SKILL.md
Commit: f484c82

Reviewed: 4 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.