Name: asknicely
Rating: 59.2 (1 reviews)
Author: membranedev

asknicely

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

Quality

69%

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

The body is highly actionable with executable commands and clear section structure, but its workflow guidance lacks the validation/confirmation steps that destructive and batch operations (GDPR deletes) demand, capping workflow clarity.

Suggestions

Add an explicit confirmation/dry-run checkpoint before destructive or batch actions, e.g. requiring user confirmation before running 'Bulk Delete Contacts (GDPR)' or 'Delete Contact'.

Include a verify-after-run step for destructive operations (e.g. re-fetch the contact to confirm removal) to form a validate→fix→retry feedback loop.

Consider moving the popular-actions table into a references file and keeping only the most common few inline to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command examples with brief explanations and well-organized tables, with only minor over-explanation such as the opening 'AskNicely is a customer experience platform...' paragraph — matching anchor 4 (efficient, minor instances of over-explanation that could be trimmed).	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands covering install, auth, connection, action search/run, and proxy, plus flag tables — matching anchor 5 (fully executable, copy-paste ready, common cases covered).	5 / 5
Workflow Clarity	The install→auth→connect→search→run sequence has validation checkpoints (polling connection state, handling CLIENT_ACTION_REQUIRED), but the skill exposes destructive and batch operations (e.g. 'Bulk Delete Contacts (GDPR)', 'Delete Contact') with no confirm/dry-run/verify step, which caps workflow_clarity at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with no nested-reference problem and no bundle files requiring navigation, though the sizable inlined popular-actions table is a minor organization gap — matching anchor 4 (good structure, mostly well placed, minor gaps).	4 / 5
	Total	16 / 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 answers both 'what' and 'when' with an explicit trigger clause and names a distinctive app, but it relies on generic verbs and omits AskNicely-specific natural terms like 'surveys', 'NPS', and 'feedback' that users would actually say.

Suggestions

Replace generic verbs ('Manage data, records, automate workflows') with AskNicely-specific capabilities such as 'send surveys, collect NPS and survey responses, manage contacts'.

Expand the 'Use when' clause with concrete trigger phrases users would naturally say, e.g. 'Use when the user wants to send surveys, check NPS scores, or manage AskNicely contacts and responses'.

Add common synonyms and file/extension-free domain terms ('NPS', 'feedback', 'survey responses') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (AskNicely) and a few actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete capabilities — matching anchor 3 (names domain and 1-2 concrete actions, not comprehensive).	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with AskNicely data') are present, but the 'when' clause is generic rather than concrete — matching anchor 4 (both what and when; when could be more specific).	4 / 5
Trigger Term Quality	Includes relevant keywords ('AskNicely', 'data', 'records', 'workflows', 'interact with AskNicely data') but misses the natural AskNicely-specific terms users would say ('surveys', 'NPS', 'feedback', 'responses'), matching anchor 3 (some keywords, missing common variations).	3 / 5
Distinctiveness Conflict Risk	The named app 'AskNicely' gives a clear niche and distinct triggers, but the generic verbs ('manage data, records, automate workflows') create minor overlap risk with CRM/survey skills — matching anchor 4 (mostly distinct, minor overlap risk).	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/asknicely/SKILL.md
Commit: f484c82

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.