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

daily

Daily integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Daily 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/daily/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 clear connection workflow that includes state-based validation checkpoints. Its main weakness is moderate verbosity in the introductory and connective prose; progressive disclosure and organization are solid for a single-file CLI skill.

Suggestions

Trim the opening "Daily is a platform..." marketing paragraph and editorial asides like "so you can focus on the integration logic rather than auth plumbing" to assume Claude's competence.

Fix the dangling "Step 2" reference by explicitly numbering the connection steps (1. ensure, 2. search/run) so the skip-to instruction is unambiguous.

Add a brief validation note after `membrane action run` (e.g., check the `output` field for errors) to strengthen the feedback loop for destructive actions like delete-recording or delete-room.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands and tables, but the opening marketing paragraph ("Daily is a platform for adding video and audio calls...") and connective prose such as "so you can focus on the integration logic rather than auth plumbing" could be trimmed, fitting the mostly-efficient anchor.	3 / 5
Actionability	It provides copy-paste-ready, fully executable commands for every common case (install, login, connection ensure, action list/run, request proxy) plus a concrete action-key table and flag reference, matching the fully-executable anchor.	5 / 5
Workflow Clarity	There is a clear sequence (install → authenticate → connect → poll/handle states → search → run) with validation via state polling (READY/BUILDING/CLIENT_ACTION_REQUIRED), though the dangling "Step 2" reference is a minor gap keeping it below 5.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is well-sectioned into clearly headed topics appropriate for a CLI skill, with good organization and no nested references, matching the good-structure anchor.	4 / 5
	Total	16 / 20 Passed

Description

58%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 states both what and when and is anchored to the Daily brand, but its single generic verb and generic CRM entity list limit specificity, trigger-term coverage, and distinctiveness. It reads more like a templated CRM description than one tailored to Daily's actual video-calling capabilities.

Suggestions

Replace the generic entity list with Daily's real capabilities (e.g., meetings, rooms, recordings, participants, transcriptions) and use specific verbs like create, list, eject, and delete.

Add concrete natural trigger phrases such as "Use when the user wants to start or manage video calls, meetings, rooms, or recordings in Daily."

Drop "and more" and align the listed objects with the skill body so the description does not invite overlap with unrelated CRM skills.

Dimension	Reasoning	Score
Specificity	"Manage Persons, Organizations, Deals, Leads, Projects, Activities and more" names the domain and several concrete entities but relies on a single generic action verb ("Manage"), so it does not list several distinct concrete actions as a 4 requires.	3 / 5
Completeness	Both "what" (Daily integration; manage the listed entities) and "when" ("Use when the user wants to interact with Daily data") are present and explicit, though the "when" trigger is generic rather than concrete, matching the 4 anchor.	4 / 5
Trigger Term Quality	It includes "Daily" and "Daily data" plus entity names, but is missing common natural variations and synonyms users would actually say, fitting the "some relevant keywords" anchor rather than good coverage.	3 / 5
Distinctiveness Conflict Risk	The "Daily" brand names a niche, but the generic CRM-style entity list (Deals, Leads, Organizations, Persons) would overlap with actual CRM/sales skills, so it is only somewhat specific with real overlap risk.	3 / 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/daily/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.