Name: smaily
Rating: 64 (1 reviews)
Author: membranedev

smaily

Smaily integration. Manage Persons, Organizations, Deals, Activities, Notes, Files and more. Use when the user wants to interact with Smaily data.

Quality

76%

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

A well-structured, actionable CLI integration skill with copy-paste commands and a validated connection workflow. Main weaknesses are minor redundancy, a dangling step reference, and the lack of any progressive disclosure via reference files.

Suggestions

De-duplicate the 'action list' command: keep it once in 'Searching for actions' and have 'Popular actions' show concrete example invocations for Smaily entities instead of repeating the discovery command.

Fix the dangling navigation by labeling the connection steps explicitly (e.g. 'Step 1a. Ensure connection', 'Step 1b. Wait for ready', 'Step 2. Run actions') so 'Skip to Step 2' resolves.

Consider moving the detailed connection-state reference and proxy flags table into a references/ file and linking to it, so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	Largely efficient and command-driven, but the 'action list' command is repeated across 'Searching for actions', 'Popular actions', and 'Best practices', and the opening Smaily overview paragraph is mild padding Claude could infer.	4 / 5
Actionability	Provides concrete, copy-paste-ready commands (install, login, connection ensure, action run, request) plus a full proxy flags table; minor gaps include placeholder-only examples and a thin 'Popular actions' section with no concrete Smaily action examples.	4 / 5
Workflow Clarity	Clear install→auth→connect→search→run→proxy sequence with polling and state validation (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) on the connection flow; a dangling 'Skip to Step 2' reference with no matching 'Step 2' heading is a minor sequencing gap.	4 / 5
Progressive Disclosure	Well-organized into clear sections appropriate for an operational CLI skill, but it is a single ~150-line file with no external references, so detailed material (e.g. the connection-state machine, flags table) is inlined rather than split out.	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 solid third-person description that names the platform and concrete entities with an explicit 'Use when' trigger. It is distinct and reasonably complete, with only minor room to sharpen action verbs and trigger synonyms.

Dimension	Reasoning	Score
Specificity	Names multiple concrete resource types ('Persons, Organizations, Deals, Activities, Notes, Files') but relies on a single generic verb ('Manage') rather than distinct actions, leaving minor coverage gaps.	4 / 5
Completeness	Both 'what' (Smaily integration, managing entities) and 'when' ('Use when the user wants to interact with Smaily data') are present; the trigger clause is explicit but could be more specific.	4 / 5
Trigger Term Quality	Good keyword coverage with the app name 'Smaily' and named entities plus the natural trigger phrase 'Use when the user wants to interact with Smaily data', though a few synonyms/variations are missing.	4 / 5
Distinctiveness Conflict Risk	'Smaily' is a specific named platform with distinct entity triggers, giving it a clear niche and minimal conflict risk with other 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/smaily/SKILL.md
Commit: f484c82

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