Name: ghost
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

ghost

Ghost integration. Manage Posts, Users, Members, Settingses. Use when the user wants to interact with Ghost data.

Quality

66%

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

Quality

Content

71%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 an actionable, well-structured guide to driving Ghost through the Membrane CLI, with concrete commands and a clear connection-state workflow. Its main weaknesses are inconsistent step numbering and the absence of any progressive disclosure into reference files despite a sizeable inline actions table.

Suggestions

Fix the workflow numbering: label "Step 1: Connect" and "Step 2: Search and run actions" explicitly so the "skip to Step 2" and "1b" references resolve.

Add at least one concrete create/update example with a real Ghost field payload (e.g. create-post with title/mobiledoc) instead of the generic {"key":"value"}.

Move the 20-row popular-actions table and the proxy-flags table into a references/ file (e.g. ACTIONS.md) and link to it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands, tables, and state-handling detail that Claude does not already know about the Membrane CLI; the only clear over-explanation is the opening "Ghost is a content management system..." intro and a few Membrane-internals asides.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure/get, action list/run, and proxy requests, plus a 20-row actions table, but create/update examples only show a generic {"key":"value"} input rather than a concrete post payload.	4 / 5
Workflow Clarity	The connection lifecycle is sequenced with explicit state checkpoints (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a re-poll feedback loop, but numbering is inconsistent (a "1b" with no "1a" and a reference to "Step 2" that is never labeled).	4 / 5
Progressive Disclosure	The file is well-sectioned with headers but is ~170 lines entirely inline with no bundle files or one-level-deep references; the large popular-actions and proxy-options tables are content that could live in a reference file for a skill this size.	3 / 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 answers both what and when and is anchored to a distinct platform (Ghost), but it relies on a single generic verb and a vague trigger phrase, with a typo ("Settingses") that undermines specificity. It is solid but not exemplary.

Suggestions

Replace the single verb "Manage" with distinct concrete actions, e.g. "Create, update, and list posts, pages, members, and staff users in Ghost".

Expand the trigger clause with natural phrases users say: "Use when the user wants to manage a Ghost blog, newsletter, members, or publishing workflow."

Fix the typo "Settingses" → "Settings" and consider naming the actual settings actions.

Dimension	Reasoning	Score
Specificity	"Manage Posts, Users, Members, Settingses" names the Ghost domain and several entities, but applies a single generic verb ("Manage") rather than listing distinct concrete actions, so it is not comprehensive. The typo "Settingses" further signals incomplete coverage.	3 / 5
Completeness	It states both what ("Ghost integration. Manage Posts, Users, Members, Settingses") and when ("Use when the user wants to interact with Ghost data"), but the when-clause is somewhat generic rather than enumerating concrete trigger phrases.	4 / 5
Trigger Term Quality	"Ghost", "Posts", "Users", "Members" are relevant keywords, but the trigger phrase "interact with Ghost data" is generic and misses common natural variations users would say (blog, newsletter, publishing, author).	3 / 5
Distinctiveness Conflict Risk	The named platform "Ghost" gives it a clear niche and low conflict risk, but the generic "Manage Posts, Users, Members" conceptually overlaps with other CMS skills (e.g. WordPress).	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/ghost/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.