ghst
Analysis
This is a transparent Ghost CLI skill, but it gives an agent broad staff-level power to publish, delete, bulk-change, export, and reconfigure a Ghost site.
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
# `ghst api` Direct raw Ghost API requests... `--method <method>`... `--body <json>`... `--input <path>`
The raw API command is an escape hatch that can send arbitrary Ghost API requests using the configured staff credentials, beyond safer resource-specific workflows.
`delete [options] <id>`... `import [options] <filePath>`... `export [options]`: Export members as CSV... `bulk [options]`: Run a bulk member operation.
Member deletion, import/export, and bulk operations mean one command can affect many subscribers or move sensitive business data at once.
[0] node | package: @tryghost/ghst | creates binaries: ghst
The skill relies on an external npm package to provide the executable, and the provided install spec does not show a pinned version.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
`GHOST_STAFF_ACCESS_TOKEN`... Add the variables directly to your `~/.openclaw/.env` file... `GHOST_STAFF_ACCESS_TOKEN="your-staff-access-token-id:secret"`
The skill clearly requires a Ghost staff access token and stores it in agent-accessible configuration; this is expected for the Admin API but is a powerful credential.
