Name: daily
Rating: 37.6 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

daily

Documentation and capabilities reference for Daily

Quality

35%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/daily/SKILL.md

The canonical home for this skill is daily in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

42%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 a comprehensive but verbose reference catalog of Pipecat/Daily capabilities with a few good code examples buried among long provider enumerations. Workflows are sequenced but lack executable steps and validation, and everything is inlined with no progressive disclosure to sub-files.

Suggestions

Trim the provider-name enumerations and capability lists to the actionable essentials Claude cannot derive, or move them to a separate references file.

Add runnable commands and validation checkpoints to the workflow sections (e.g., a verify step after pipeline assembly, a deploy-health check).

Split the bulk reference material (per-provider integration details, transport options) into separate referenced files so SKILL.md stays a lean overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The body is a long enumeration of provider names and capability lists ("20+ LLM providers including...", "30+ text-to-speech providers") that largely restates upstream reference material Claude can already find, with several padded sections beyond the mostly-efficient anchor 3.	2 / 5
Actionability	A few sections give executable code (Pipeline, FunctionSchema, CustomProcessor), but most workflows and capability sections are abstract descriptions or numbered lists without runnable code, leaving concrete guidance incomplete per the anchor 3.	3 / 5
Workflow Clarity	Numbered workflows exist with clear sequencing, but they contain no validation checkpoints, commands, or error-recovery loops, and several involve deployment/scaling operations the rubric caps at 3 without validation.	3 / 5
Progressive Disclosure	The document has clear section structure but is a monolithic single file: long provider integration lists and per-capability detail that belong in separate reference files are inlined, and no bundle files exist to split depth.	3 / 5
	Total	11 / 20 Passed

Description

28%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 a vague label rather than a capability statement: it names the Daily domain but provides no concrete actions and no usage triggers. It fails to answer when Claude should invoke the skill and what specifically it does.

Suggestions

Replace generic phrasing with concrete actions, e.g. "Look up Daily/Pipecat voice-agent APIs, transports, and provider integrations".

Add an explicit trigger clause such as "Use when the user asks about Daily, Pipecat, real-time voice bots, or integrating STT/TTS/LLM providers".

Include natural user-facing keywords and synonyms (Daily, Pipecat, voice assistant, WebRTC transport, function calling) to improve trigger matching.

Dimension	Reasoning	Score
Specificity	The phrase "Documentation and capabilities reference for Daily" names the domain (Daily) but offers only a generic action ("reference") with no concrete capabilities enumerated, sitting between the vague anchor 1 and the minimal-action anchor 2.	2 / 5
Completeness	It gives only a vague "what" (a reference) with no "Use when..." trigger guidance, matching the anchor for a vague what and absent when; per the rubric a missing when caps completeness low.	2 / 5
Trigger Term Quality	"Documentation" and "capabilities reference" are generic terms plus a proper noun; users would not naturally say this phrase when needing the skill, fitting the one-or-two-generic-keywords anchor rather than the no-keywords anchor 1.	2 / 5
Distinctiveness Conflict Risk	The "Daily" proper noun scopes it somewhat, but "documentation and capabilities reference" is generic phrasing that could overlap with other reference-style skills, matching the somewhat-specific-but-overlapping anchor 3.	3 / 5
	Total	9 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/daily/SKILL.md
Commit: 57c135b

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.