Name: magnolia
Rating: 56.8 (1 reviews)
Author: membranedev

magnolia

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

Quality

65%

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/magnolia/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 content is a well-structured, actionable integration guide with concrete CLI commands and a sensible connection state-machine workflow. Its main weakness is minor verbosity from explaining Magnolia basics and some marketing-flavored prose, plus a slightly loose step reference.

Suggestions

Cut the introductory paragraph defining what a CMS/Magnolia is; Claude already knows this, so start directly with how to use the Membrane CLI.

Tighten best-practice prose (e.g., 'This will burn less tokens and make communication more secure') into crisp directive bullets.

Replace the dangling 'skip to Step 2' with explicit labeled steps or section links so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening 'Magnolia is a content management system (CMS)... often used by enterprises...' and marketing-flavored best-practice lines ('burn less tokens') explain concepts Claude already knows and could be trimmed.	3 / 5
Actionability	Provides many copy-paste-ready commands (npm install, membrane login, connection ensure, action run, request with flags) that are mostly executable, with only minor gaps from placeholders like CONNECTION_ID and <agentType>.	4 / 5
Workflow Clarity	A clear install→authenticate→connect→search→run sequence with validation checkpoints (poll --wait until READY, handle CLIENT_ACTION_REQUIRED, re-poll after action) exists, but the loose 'skip to Step 2' reference without a labeled Step 2 leaves a minor gap below the 5 anchor.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with no nested references and no bundle files needed, but as a single ~159-line file it is good rather than the ideal clear-overview-with-one-level-references structure of 5.	4 / 5
	Total	15 / 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 cleanly states what the skill does and when to use it with an explicit 'Use when' clause and a distinctive product name, but the capability actions are generic and trigger phrasing lacks natural variations. It is solid but not comprehensive.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Magnolia actions (e.g., 'Create and publish pages, manage assets, configure templates, automate workflows').

Add natural trigger variations such as 'Use when the user mentions Magnolia CMS, pages, templates, or content publishing.'

Keep the explicit 'Use when' clause but pair it with concrete trigger phrases (e.g., file types or feature names) to lift completeness.

Dimension	Reasoning	Score
Specificity	Names the Magnolia domain plus a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete like 'extract' or 'fill', so it does not reach the several-specific-actions bar of 4.	3 / 5
Completeness	Both halves are present: a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Magnolia data'); the trigger could be more specific with concrete phrases, so it sits below the 5 anchor.	4 / 5
Trigger Term Quality	The main natural keyword is the product name 'Magnolia' in 'interact with Magnolia data', but common phrasing variations or synonyms are missing, matching the some-relevant-keywords anchor rather than comprehensive coverage.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the named product 'Magnolia' gives it a clear niche with low conflict risk, though the generic action verbs leave minor overlap risk with other data-management skills.	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/magnolia/SKILL.md
Commit: f484c82

Reviewed: 6 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.