Name: smarty
Rating: 55.2 (1 reviews)
Author: membranedev

smarty

Smarty integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Smarty data.

Quality

62%

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

Quality

Content

61%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 a solid, command-heavy integration guide with good connection-state handling, but it is held back by a misleading intro paragraph, an incoherent step reference, and missing validation guidance around batch action execution. It is actionable yet improvable on tightness and workflow rigor.

Suggestions

Remove or correct the opening "Smarty is a template engine for PHP" paragraph, which is both filler and inaccurate for this address-validation integration.

Fix the "skip to Step 2" reference to point to a real, labeled step (or relabel the sections as Step 1/Step 2) so the workflow sequence is coherent.

Add a validation/check step for batch and write operations (e.g., verify-us-addresses-bulk), such as inspecting the output for errors and retrying failed rows, to satisfy the destructive/batch workflow requirement.

Dimension	Reasoning	Score
Conciseness	Mostly command-driven and efficient, but the opening paragraph explains what Smarty is (a concept Claude knows) and is also factually misleading for this address platform, plus filler like "so you can focus on the integration logic rather than auth plumbing"; matches the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	Provides copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run, request) and an action-key table, matching the mostly-executable anchor; not a 5 because the Popular actions table has an empty Description column and action parameters are not shown.	4 / 5
Workflow Clarity	A connection sequence with state-based feedback loops exists (READY/BUILDING/CLIENT_ACTION_REQUIRED polling), but the "skip to Step 2" reference points to a non-existent step and batch/destructive actions like verify-us-addresses-bulk lack validation checkpoints, capping clarity per the destructive/batch rule.	3 / 5
Progressive Disclosure	Well-organized into clearly headed sections (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with no bundle files present, matching the good-structure anchor; not a 5 because the skill is ~160 lines and the proxy-flag reference table could live in a separate file.	4 / 5
	Total	14 / 20 Passed

Description

63%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 a clear purpose and an explicit trigger, but its trigger vocabulary is thin and the "Smarty" name is ambiguous against the famous PHP template engine, limiting distinctiveness. It is competent but not comprehensive.

Suggestions

Add the actual capability terms users would say (e.g., address verification, autocomplete, ZIP code lookup) so the description triggers on real requests rather than only the product name.

Disambiguate "Smarty" from the PHP template engine, e.g. "Smarty (address validation platform) integration".

Replace the generic "interact with Smarty data" trigger with concrete situations such as "Use when the user wants to verify, autocomplete, or look up addresses."

Dimension	Reasoning	Score
Specificity	Lists several concrete management actions over named entities ("Manage Organizations, Pipelines, Users, Goals, Filters"), matching the anchor that lists several specific actions with minor coverage gaps; not a 5 because the verbs are uniform ("Manage") and capabilities like address verification/autocomplete are absent.	4 / 5
Completeness	Provides both a "what" ("Manage Organizations, Pipelines, Users, Goals, Filters") and an explicit "when" ("Use when the user wants to interact with Smarty data"), but the trigger is generic so it does not reach the concrete-trigger anchor of 5.	4 / 5
Trigger Term Quality	Only repeats "Smarty" and "Smarty data"; the natural phrases users actually say (verify address, address autocomplete, ZIP lookup) are missing, matching the anchor with some relevant keywords but missing common variations and synonyms.	3 / 5
Distinctiveness Conflict Risk	Names CRM-style entities giving it a niche, but "Smarty" is heavily overloaded with the well-known PHP template engine (which the body even references), so it could still trigger for the wrong intent; not a 4 because disambiguation is absent.	3 / 5
	Total	14 / 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/smarty/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.