alonso-skills/ghost-theme
Build, customize, and deploy Ghost CMS themes. Use this skill whenever the user mentions Ghost themes, Ghost CMS, Handlebars templates (.hbs files), Ghost Admin, Ghost membership/subscription integration, Ghost custom settings, or Ghost content API — even if they don't say "theme" explicitly. Trigger on: building a blog theme, creating a Ghost site, editing .hbs templates, adding member-only content, Ghost hero sections, Ghost routing (routes.yaml), Ghost image optimization, Ghost dark mode, Ghost search, Ghost deploy, gscan validation, Ghost JSON-LD/SEO, or any mention of {{ghost_head}}, {{ghost_foot}}, {{#foreach}}, {{#get}}, {{img_url}}, {{asset}}, @custom, @member, or Portal. Also use when the user has an existing Ghost theme they want to modify, extend, or debug — not just for new themes.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that thoroughly covers what the skill does, when to use it, and includes extensive Ghost-specific trigger terms. It uses proper third-person voice and provides both high-level actions and granular technical triggers. The only minor concern is that the description is quite long, but the density of useful trigger information justifies the length.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: build, customize, deploy Ghost CMS themes, editing .hbs templates, adding member-only content, Ghost routing, image optimization, dark mode, search, gscan validation, JSON-LD/SEO, and modifying/extending/debugging existing themes. | 3 / 3 |
Completeness | Clearly answers 'what' (build, customize, deploy Ghost CMS themes) and 'when' with an extensive explicit 'Use this skill whenever...' and 'Trigger on:' clause covering numerous scenarios. Also explicitly notes it applies to existing theme modification, not just new themes. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including file extensions (.hbs), tool names (gscan, Ghost Admin, Portal), template helpers ({{ghost_head}}, {{#foreach}}, {{img_url}}), config files (routes.yaml), and natural phrases like 'building a blog theme', 'creating a Ghost site', 'member-only content'. Covers both technical and casual user language. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — Ghost CMS theming is a clear niche. The description includes Ghost-specific terminology (gscan, {{ghost_head}}, @custom, Portal, Ghost Admin) that would not overlap with generic web development or other CMS skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exceptionally well-structured skill that serves as a clean routing layer to detailed reference files. It provides concrete setup commands, clear constraints ('Do not write Ghost theme files from scratch'), and an efficient lookup table that maps user needs to specific references. The Common Workflows section adds significant value by showing how references combine for real tasks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude's competence with web development, doesn't explain what Ghost CMS is, what Handlebars templates are, or how Docker works. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | Provides concrete, copy-paste-ready bash commands for setup, specific URLs for Ghost Admin, exact file references for each task, and clear instructions like activating 'dev-theme' in Docker. The routing table maps specific needs to specific reference files with key topics listed. | 3 / 3 |
Workflow Clarity | The Quick Start section has a clear sequence (copy template → install → build → docker up → dev → activate theme). Common Workflows section maps multi-step processes to exactly which references to read in order. The validation step is addressed via GScan reference. The instruction 'Do not write Ghost theme files from scratch' is a clear safety constraint. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the SKILL.md is a concise overview with a well-organized routing table pointing to 13 one-level-deep reference files. Each reference is clearly signaled with descriptive key topics. Common Workflows section shows which 2-3 references to combine for specific tasks, preventing unnecessary reading. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents