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

inksprout

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

Quality

68%

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

Quality

Content

75%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 well-structured, highly actionable CLI guide with explicit connection-state validation and feedback loops. Weaknesses are minor: a little product-blurb padding, placeholder values in examples, and a slightly inconsistent step numbering scheme.

Suggestions

Tighten the intro and remove filler like "Use action names and parameters as needed." to improve token efficiency.

Fix the step labeling (label the action-search/run section as "Step 2" and rename "1b" to match a consistent numbered sequence) so the cross-references resolve.

Add at least one fully concrete action-run example with real values (not just <actionId> placeholders) to close the actionability gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, built around concrete executable commands (install, login, connection ensure, action run, request) with little padding, but retains minor over-explanation such as the product-description intro ("Inksprout is a content marketing platform...") and filler like "Use action names and parameters as needed." that could be trimmed.	4 / 5
Actionability	Provides concrete, copy-paste-ready commands throughout (e.g., `membrane connection ensure "https://inksprout.co/" --json`, `membrane action run <actionId> --connectionId=CONNECTION_ID --json`) plus a flags table, but placeholders like CONNECTION_ID and a thin two-row Popular actions table leave minor gaps versus fully concrete examples.	4 / 5
Workflow Clarity	The connection workflow has an explicit validation feedback loop (poll until READY, branch on CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR, re-poll after action), but the sequence labeling is inconsistent ("skip to Step 2" with no labeled Step 2, and a "1b" without a "1a"), a minor navigation gap below the top anchor.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections (Overview, Working with Inksprout, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with easy navigation and no nested references, but as a single ~145-line file over the 50-line simple-skill threshold it does not split content into separate files.	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 is solid: it names the domain, enumerates concrete resources, and includes an explicit 'Use when' trigger. Its main weaknesses are a single generic verb ('Manage') for action specificity and a single trigger phrase lacking synonyms.

Suggestions

Replace the generic 'Manage' with specific verbs per resource (e.g., 'Create and update Pipelines, invite Users, configure Filters') to lift action specificity.

Expand the 'Use when' clause with concrete trigger scenarios (e.g., 'Use when the user wants to list summaries, summarize content, or manage Inksprout pipelines and users').

Add a few natural synonyms or action keywords users would actually say (e.g., 'summarize', 'summaries', 'content marketing') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the Inksprout domain and enumerates four concrete resource types ("Manage Organizations, Pipelines, Users, Filters"), but the single generic verb "Manage" repeated across all four provides only minimal action specificity, fitting the 1-2 concrete-actions anchor rather than comprehensive coverage.	3 / 5
Completeness	Explicitly answers both what ("Manage Organizations, Pipelines, Users, Filters") and when ("Use when the user wants to interact with Inksprout data"), but the when is a single generic trigger clause rather than the multiple concrete trigger scenarios that define the top anchor.	4 / 5
Trigger Term Quality	Includes the distinctive brand keyword "Inksprout" and a natural trigger phrase ("Use when the user wants to interact with Inksprout data"), but offers no synonyms or common variations of trigger terms, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The distinctive brand name "Inksprout" establishes a clear niche and low conflict risk, but the generic resource nouns (Organizations, Users, Filters) carry minor overlap risk with other integration skills, placing it just below the minimal-conflict top anchor.	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/inksprout/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.