Name: picky-assist
Rating: 56.8 (1 reviews)
Author: membranedev

picky-assist

Picky Assist integration. Manage data, records, and automate workflows. Use when the user wants to interact with Picky Assist data.

Quality

65%

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

Quality

Content

67%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 solid, actionable integration guide with concrete CLI commands and a well-sequenced connection workflow, but it is undermined by an LLM-generated filler opening and inconsistent step numbering that slightly reduce conciseness and workflow clarity.

Suggestions

Delete the filler opening sentence ('I don't have enough information about Picky Assist...') — it is LLM-generated noise that wastes context tokens.

Fix the inconsistent step numbering: the body references 'Step 2' and '1b' without a clear numbered Step 1, so renumber the connection flow coherently (1, 2, 3).

Make the 'Popular actions' section actionable by listing 2-3 example action ids or names (e.g., send broadcast, list contacts) instead of only restating the discovery command.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the opening 'I don't have enough information about Picky Assist to provide a description' is LLM-generated filler that earns no tokens, matching anchor 3 rather than the lean anchor 4.	3 / 5
Actionability	Provides concrete, executable commands throughout (install, login, connection ensure, action run, proxy flags) that are mostly copy-paste ready; not a 5 because the 'Popular actions' section merely restates the discovery command instead of giving examples.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-polling checkpoints and explicit READY/BUILDING/CLIENT_ACTION_REQUIRED branching; capped below 5 by inconsistent step numbering ('Step 2', '1b') that weakens the sequence.	4 / 5
Progressive Disclosure	No bundle files exist, and the self-contained body is organized into clear sections appropriate for an overview skill; minor organization gaps (inconsistent numbering) keep it at anchor 4 rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

62%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 competent — it states what the skill does and when to use it with an explicit trigger — but its actions are generic and it misses the concrete Picky Assist capabilities (Contacts, Broadcasts, Workflows) that would make it specific and distinctive.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Picky Assist capabilities such as managing contacts and contact lists, sending broadcasts, and building workflows.

Expand the 'Use when...' clause with concrete trigger phrases users would actually say (e.g., 'when the user wants to send a broadcast, manage contacts, or configure Picky Assist workflows').

Add a distinguishing phrase that sets it apart from general CRM/messaging skills, e.g., 'specifically for the Picky Assist platform'.

Dimension	Reasoning	Score
Specificity	Names the Picky Assist domain plus a few generic actions ('Manage data, records, and automate workflows') but lacks concrete capabilities like Contacts, Broadcasts, or Workflows, so it is not comprehensive — matches anchor 3.	3 / 5
Completeness	Provides a clear 'what' (manage data, records, automate workflows) and an explicit 'Use when...' clause; not a 5 because the trigger phrases are generic rather than concrete and varied.	4 / 5
Trigger Term Quality	Includes the natural product name 'Picky Assist' and 'interact with Picky Assist data', but offers no synonyms or file-extension variations users would naturally say — matches anchor 3.	3 / 5
Distinctiveness Conflict Risk	The named 'Picky Assist' niche makes it mostly distinct with only minor overlap risk against other CRM/messaging skills, matching anchor 4 rather than the broader anchor 3.	4 / 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/picky-assist/SKILL.md
Commit: f484c82

Reviewed: 5 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.