ghost cms
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill appears to do what it says—manage Ghost CMS posts—but it uses a Ghost Admin API key and can publish or delete blog content, so users should review actions carefully.
Before installing, confirm you trust the skill source, keep the Ghost Admin API config file private, and review any create/update/delete/publish action before letting the agent run it. Use trusted image files or URLs, and install Python dependencies from a trusted environment.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If invoked with valid credentials, the agent can create, publish, edit, or delete posts on the configured Ghost blog.
The skill explicitly supports mutating Ghost CMS content, including deletion and publishing workflows. This is expected for the purpose but can affect public blog content.
- 📝 **Create/Update/Delete posts** - Full CRUD operations
Use this only for Ghost sites you control, and require explicit user confirmation before publishing, updating, or deleting live content.
A supplied image URL may be fetched from the local environment and then uploaded to Ghost.
The code automatically downloads external feature-image URLs before uploading them to Ghost. This is related to image handling, but untrusted URLs could cause unwanted network fetches.
if feature_image and feature_image.startswith('http') and 'fu-ye.com' not in feature_image:
local_path = download_image(feature_image)Only use trusted image URLs and avoid passing arbitrary or unreviewed URLs as feature images.
Anyone or any agent process with access to the config file could use the Admin API key to manage the configured Ghost site.
The skill requires a Ghost Admin API key in a JSON config file. This is necessary for the integration, but it is a sensitive credential and the registry metadata lists no primary credential.
"admin_api_key": "your-id:your-secret"
Store the config file securely, avoid sharing it with unrelated projects, and rotate the Ghost integration key if it may have been exposed.
Dependency behavior may vary by environment or over time, and users rely on the package source they install from.
The setup instructions rely on unpinned PyPI packages outside an install spec. These are common packages and purpose-aligned, but the exact versions are not locked.
pip3 install requests pyjwt --user
Install dependencies from trusted package indexes and consider pinning known-good versions in a controlled environment.