ghost-database

Use this skill for persistent PostgreSQL storage in agent workflows — spin up databases on demand, test schema migrations safely on forks, and pass databases as assets between agents using Ghost. **Trigger when user asks to:** - Create a new PostgreSQL database quickly - Manage database lifecycle in agent workflows - Fork a database to test changes safely - Run analytics or heavy queries on a fork without impacting the production database - Share a database snapshot so others can spin up their own copy - Pass a database as an input or output between agents - Create a database for agents - Need many databases that are billed only when queried - Set up the Ghost MCP server or CLI **Note:** If the Ghost MCP server is already installed, use its tools directly — this skill is for environments without the MCP or as a reference for what's possible. **Keywords:** Ghost, ghost.build, database, create database, fork database, PostgreSQL, managed Postgres, MCP, agent database, connection string

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

82%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 highly actionable with concrete CLI and MCP examples and a well-structured fork-safety workflow. Its main weaknesses are mild redundancy (read-only mode and trigger guidance each appear twice) and a long monolithic file where some content could be externalized.

Suggestions

Consolidate the MCP read-only mode explanation into one location instead of repeating it in both 'Additional features' and 'MCP Integration'.

Trim or remove the 'When to Use Ghost' section since its good-fit/bad-fit criteria largely restate the frontmatter description's triggers.

Move the four platform-specific install snippets into a references file (e.g. references/INSTALL.md) and keep a single recommended install command in SKILL.md.

Dimension	Reasoning	Score
Conciseness	Most content is concrete executable commands and examples that earn their tokens, but MCP read-only mode is explained twice (Additional features and MCP Integration) and the 'When to Use Ghost' section restates the description's triggers — minor duplication that could be trimmed.	4 / 5
Actionability	Provides copy-paste ready CLI commands (ghost create, sql, fork, share, resume, schema) with real example SQL and parallel MCP parameter-object calls covering the common lifecycle cases.	5 / 5
Workflow Clarity	The fork workflow includes an explicit validate-on-fork → apply-or-rollback feedback loop, but the create/query and share workflows lack validation checkpoints and migration validation is deferred to another skill.	4 / 5
Progressive Disclosure	Well-organized single-file sections with clear headers and full CLI reference deferred to `ghost --help`; some inline content (four platform install variants, the duplicated 'When to Use' guidance) could be split or trimmed for a leaner overview.	4 / 5
	Total	17 / 20 Passed

Description

100%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 is exemplary: it concisely states concrete capabilities, provides explicit trigger guidance in third person, and supplies a keyword block for discoverability. It clearly distinguishes the skill's niche with no significant conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'spin up databases on demand, test schema migrations safely on forks, and pass databases as assets between agents' — reinforced by a nine-item trigger list of specific operations, giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both 'what' (persistent PostgreSQL storage, forking, asset passing) and 'when' via a 'Trigger when user asks to:' clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes a dedicated Keywords block covering 'Ghost, ghost.build, database, create database, fork database, PostgreSQL, managed Postgres, MCP, agent database, connection string' alongside natural user phrases, spanning synonyms and product identifiers.	5 / 5
Distinctiveness Conflict Risk	Targets a clear niche — Ghost managed PostgreSQL for agent workflows — with distinctive triggers (Ghost, ghost.build, agent database, fork database) and minimal overlap risk with other skills.	5 / 5
	Total	20 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: timescale/pg-aiguide
Path: skills/ghost-database/SKILL.md
Commit: ee14d8b

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