Name: dailybot
Rating: 64.8 (1 reviews)
Author: membranedev

dailybot

DailyBot integration. Manage Users, Roles, Goals, Organizations. Use when the user wants to interact with DailyBot data.

Quality

77%

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/dailybot/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.

A highly actionable, well-structured integration guide with concrete Membrane CLI commands throughout. Its main weakness is the lack of validation/verification steps around destructive action execution, which caps workflow clarity.

Suggestions

Add a validation/verification step to the 'Running actions' workflow for destructive and batch operations (e.g. list the resource before delete, confirm with the user, then verify the result in the `output` field) to lift workflow clarity above 3.

Trim non-earning prose such as 'It's used by project managers, scrum masters, and team leads in various industries.' to improve token efficiency.

Consider moving the 21-row 'Popular actions' reference table into a separate one-level-deep file (e.g. ACTIONS.md) and signaling it from the body, to strengthen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete Membrane CLI commands that earn their place, but includes minor over-explanation such as 'It's used by project managers, scrum masters, and team leads in various industries.' that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready commands for every common case (install, login, connection ensure, action list/run, request proxy) with flags and a populated actions table, fully executable without gaps.	5 / 5
Workflow Clarity	The connection setup is well-sequenced with a state-machine feedback loop, but the action-execution workflow exposes destructive operations ('Delete Check-in', 'Remove User from Team') with no validation or verification steps, capping this dimension at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references, but everything lives inline in a single ~165-line file (including a 21-row actions table) with no one-level-deep references to split out the reference bulk.	4 / 5
	Total	16 / 20 Passed

Description

78%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.

A concise, well-formed description that states both capability and a use-trigger around a clearly named product niche. It would benefit from more varied action verbs and concrete trigger phrases (standups, check-ins) to lift completeness and trigger quality.

Dimension	Reasoning	Score
Specificity	Names the DailyBot domain and several concrete entities to 'Manage' ('Users, Roles, Goals, Organizations'), but reuses one generic verb across nouns rather than listing distinct CRUD actions, leaving minor coverage gaps (e.g. check-ins, teams, forms appear in the body but not here).	4 / 5
Completeness	Explicitly answers both 'what' ('DailyBot integration. Manage Users, Roles, Goals, Organizations.') and 'when' ('Use when the user wants to interact with DailyBot data.'), but the 'when' clause is generic rather than naming concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes the natural product keyword 'DailyBot' and core entity names with an explicit 'Use when the user wants to interact with DailyBot data' trigger, but misses common natural variations like 'standups', 'check-ins', or 'team updates'.	4 / 5
Distinctiveness Conflict Risk	The named product 'DailyBot integration' carves a clear niche with distinct triggers, making it unlikely to fire for unrelated skills.	5 / 5
	Total	17 / 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/dailybot/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.