Name: gathercontent
Rating: 55.2 (1 reviews)
Author: membranedev

gathercontent

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

Quality

62%

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/gathercontent/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 body is a well-structured, actionable guide to the Membrane/GatherContent CLI workflow with concrete commands, a state-machine-driven connection flow, and clear section navigation. Its weaknesses are a padded marketing intro, minor redundancy in the action-discovery sections, and placeholder-heavy examples without concrete resolved values.

Suggestions

Remove or compress the opening marketing paragraph ("GatherContent is a content operations platform...") since it explains context Claude can infer; lead with the integration mechanics instead.

Consolidate the overlapping "Searching for actions" and "Popular actions" sections, both of which describe `membrane action list --intent`, into one discovery section.

Add one fully resolved end-to-end example (a real connectionId and intent) showing how to parse the `--json` output and feed it into `membrane action run`.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and flags, but it includes an unnecessary marketing-style intro paragraph ("content operations platform that helps marketing teams manage and streamline...") and duplicated coverage of action discovery across the "Searching for actions" and "Popular actions" sections, fitting the score-3 anchor of mostly efficient with some unnecessary explanation.	3 / 5
Actionability	The skill provides many concrete, copy-paste-ready commands (install, login, connection ensure, action run with --input JSON, a full request flags table), but uses unresolved placeholders (CONNECTION_ID, QUERY, <actionId>) and gives no concrete example of parsing --json output, matching the score-4 anchor of mostly executable guidance with minor gaps.	4 / 5
Workflow Clarity	The connect-to-ready flow is a clear sequence with explicit checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a feedback loop (poll, inspect state, act, re-poll), but the top-level progression relies on headers and references an unlabeled "Step 2", a minor validation gap that fits the score-4 anchor.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is well-organized into navigable sections (Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) and has no nested or buried references, matching the score-4 anchor of good structure with minor organization gaps.	4 / 5
	Total	15 / 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 has an explicit and clearly scoped Use-when trigger tied to the GatherContent product name, giving it good completeness and distinctiveness. Its main weakness is specificity: the listed actions are generic verbs over abstract nouns rather than concrete GatherContent operations.

Suggestions

Replace generic actions with concrete GatherContent operations, e.g. "Create and manage Items, Projects, Templates, and Workflows, upload Files, and run bulk actions."

Add natural synonyms and file/format hints users would say, such as "content production," "content review and approval," or "GatherContent projects and items."

Tighten the "when" clause to name the trigger scenarios, e.g. "Use when the user wants to manage GatherContent projects, items, or content workflows."

Dimension	Reasoning	Score
Specificity	The description names the domain ("GatherContent integration") but the actions are minimal and generic — "Manage data, records, and automate workflows" uses abstract nouns rather than concrete GatherContent-specific actions (items, projects, templates), matching the score-2 anchor.	2 / 5
Completeness	Both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with GatherContent data") are present with an explicit Use-when trigger, but the "what" is vague rather than concrete, fitting the score-4 anchor of both present with room for greater specificity.	4 / 5
Trigger Term Quality	The product name "GatherContent" is the key natural keyword and appears in the "Use when..." clause, but beyond it only generic terms ("data", "records", "workflows") appear, missing common variations and synonyms like "content production" or "approvals" — matching the score-3 anchor of some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	The named product "GatherContent" gives a clear niche and distinct trigger, but the generic "manage data/records/automate workflows" phrasing carries minor overlap risk with other integration skills, matching the score-4 anchor of mostly distinct with minor overlap risk.	4 / 5
	Total	13 / 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/gathercontent/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.