Name: aspireiq
Rating: 52.8 (1 reviews)
Author: membranedev

aspireiq

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

Quality

59%

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

Quality

Content

56%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 delivers strong, executable CLI guidance with a sensible connection-handling workflow, but it is undermined by a large padded enumeration of repetitive terms that should be removed or moved to a reference file. Structure and actionability are good; token efficiency is the main weakness.

Suggestions

Remove or relocate the ~145-line 'Creator Campaign X' enumeration (lines 23-168); it adds padding without actionable value and should be a curated, separate reference if kept at all.

Define the unlabeled 'Step 2' target (e.g., add a '## Step 2: Search and run actions' header) so the 'skip to Step 2' references resolve to a real section.

Tighten 'Use action names and parameters as needed.' into concrete guidance, and resolve placeholder tokens (CONNECTION_ID, QUERY) with a brief note on where to obtain them.

Dimension	Reasoning	Score
Conciseness	A ~145-line enumerated list of repetitive 'Creator Campaign X' terms (lines 23-168) is heavy, low-value padding that crowds the document; this is noticeably verbose with padded sections, matching anchor 2 rather than 3 because of the sheer volume of padding.	2 / 5
Actionability	Provides concrete, mostly copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy requests with a flag table; minor gaps remain (e.g., unresolved placeholders like CONNECTION_ID and 'Use action names and parameters as needed'), keeping it at anchor 4 not 5.	4 / 5
Workflow Clarity	The connect-to-poll-to-run sequence is clear with explicit state checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-again feedback loop; a 'Step 2' is referenced but never labeled as a section, a minor validation/organization gap that holds it at anchor 4.	4 / 5
Progressive Disclosure	Section structure exists for the actionable parts, but no bundle/reference files are present and the large enumerated entity list is inlined rather than split into a separate reference file; matches anchor 3 (content that should be separate is inline) rather than 4.	3 / 5
	Total	13 / 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 a clear product-specific trigger, but its action language is generic and it lacks concrete capability examples or natural trigger synonyms. It is functional but could be sharpened.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete AspireIQ capabilities (e.g., 'discover creators, manage campaigns, track post performance, send payments').

Expand the 'Use when...' clause with concrete trigger phrases users would actually say (e.g., 'when the user mentions influencer campaigns, creator outreach, or AspireIQ').

Add natural synonyms/variants (e.g., 'influencer marketing', 'creator management') to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('AspireIQ integration') and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete and coverage is not comprehensive; sits at anchor 3, not 4 because no specific capabilities are enumerated.	3 / 5
Completeness	Both 'what' (integration, managing data/records, automating workflows) and an explicit 'when' ('Use when the user wants to interact with AspireIQ data') are present, but the trigger clause is somewhat generic rather than listing concrete trigger phrases, so it lands at anchor 4 not 5.	4 / 5
Trigger Term Quality	Contains the relevant product keyword ('AspireIQ', 'interact with AspireIQ data') but misses common variations or synonyms users might say; matches anchor 3 rather than 4 due to thin natural-term coverage.	3 / 5
Distinctiveness Conflict Risk	The AspireIQ product name gives it a clear, distinct niche, but the generic action phrasing ('Manage data, records, and automate workflows') overlaps with other integration skills, placing it at anchor 4 rather than 5.	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/aspireiq/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.