Name: appcues
Rating: 48 (1 reviews)
Author: membranedev

appcues

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

Quality

51%

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

Quality

Content

46%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 CLI usage sections are strong — executable, well-sequenced, with good connection-state feedback loops — but the document is dominated by a heavily padded, largely irrelevant keyword list that wrecks token efficiency and structure, and destructive-action workflows lack validation.

Suggestions

Remove or move the "Appcues Overview" keyword list; it is padded with duplicates and unrelated terms (Blockchain, NFTs, GDPR) and adds no actionable value.

Add explicit validation/verification guidance before destructive actions like delete-user-profile, delete-segment, and unpublish-flow (e.g. confirm with a read action first).

Move the full Popular actions table and proxy flag reference into a separate reference file, leaving SKILL.md a lean overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The "Appcues Overview" is a ~390-item bullet list with many duplicates and large swaths of irrelevant padding (Blockchain, NFTs, Metaverse, GDPR, Robotics), constituting severely verbose content Claude does not need.	1 / 5
Actionability	It provides copy-paste-ready, fully executable commands across install, login (including headless), connection ensure, polling, action list/run with JSON input, and proxy requests, covering the common cases.	5 / 5
Workflow Clarity	The connection flow has clear state checkpoints and a poll-after-action feedback loop, but destructive actions (delete-user-profile, delete-segment, unpublish-flow) lack validation/verification steps, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The file is monolithic with no bundle files or references, and the giant inline keyword list is content that clearly belongs in a separate file or should be removed, leaving minimal effective structure.	2 / 5
	Total	11 / 20 Passed

Description

57%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 and is anchored to a distinct product name, but its action language is generic and it lacks the natural Appcues-specific trigger terms (flows, tours, onboarding) users would actually say.

Suggestions

Replace generic verbs with concrete Appcues actions, e.g. "Create and publish flows, manage user profiles and segments, track events."

Add concrete trigger terms users naturally say, such as "product tours," "onboarding flows," "user segments," or "in-app announcements."

Make the 'when' clause specific, e.g. "Use when the user wants to build or manage Appcues flows, segments, or user events."

Dimension	Reasoning	Score
Specificity	It names the domain ("Appcues integration") but the actions "Manage data, records, and automate workflows" are generic rather than concrete Appcues-specific operations, matching the anchor for minimal/generic actions.	2 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Appcues data"), but the trigger clause is generic rather than tied to concrete use cases.	4 / 5
Trigger Term Quality	"Appcues" and "interact with Appcues data" are relevant keywords, but the description omits the natural terms users would actually say (flows, tours, onboarding, segments), leaving only some relevant keywords.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "Appcues" gives it a clear niche with minimal conflict risk against other Membrane app skills, though the generic "manage data, records" phrasing leaves minor overlap with broad data skills.	4 / 5
	Total	13 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (559 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: membranedev/application-skills
Path: skills/appcues/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.