ghost

Extract a language-agnostic artifact bundle with SPEC.md, tests.yaml, INSTALL.md, README.md, and VERIFY.md.

66|2|Updated Feb 18, 2015
One-click install
npx skills add https://github.com/tkersey/dotfiles --skill ghost
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ghost
Source: https://github.com/tkersey/dotfiles/tree/main/codex/skills/ghost
Command: npx skills add https://github.com/tkersey/dotfiles --skill ghost

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates turning a software repository into a language-agnostic ghost package by extracting a strict SPEC.md, exhaustive tests.yaml, INSTALL.md, README.md, and VERIFY.md while preserving upstream LICENSE files and provenance.

Core Features & Use Cases

  • Harvests and paraphrases upstream documents into a coherent, language-neutral artifact set (SPEC.md, tests.yaml, INSTALL.md, README.md, VERIFY.md) without shipping implementation code.
  • Preserves licensing and provenance information verbatim to enable reproducible verification and audits.
  • Use Case: IT teams want a portable contract for multi-language reimplementation or thorough documentation audits of a codebase.

Quick Start

Use the ghost skill to generate a ghost artifact bundle from a target repository and place it in a new sibling directory named after the source repository.

Frequently Asked Questions about ghost

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract a language-agnostic spec from an existing repository?

To extract a language-agnostic spec from a repository, this Skill harvests upstream documents like SPEC.md, tests.yaml, and README.md into a standalone, non-executable artifact bundle. It paraphrases these into a language-neutral contract without shipping implementation code.

What is a ghost artifact bundle and when do I need one?

A ghost artifact bundle is a language-agnostic collection of documentation and contracts extracted from a repository. You need one when you want a portable specification for multi-language reimplementation or thorough documentation audits without carrying the implementation code.

How do I generate reproducible documentation contracts from a codebase?

You generate reproducible documentation contracts by applying deterministic normalization to the extracted specs and recording provenance. This ensures the outputted artifacts can be consistently regenerated and audited across different environments.

Does spec extraction preserve upstream LICENSE files and provenance?

Yes, spec extraction preserves upstream LICENSE files and provenance information verbatim. This ensures reproducible verification and audits while maintaining the original licensing context for the extracted artifact bundle.

Can I use extracted ghost packages for cross-language verification?

Yes, you can use extracted ghost packages for cross-language verification. The outputted artifacts are standalone, non-executable documentation and contracts specifically designed to verify implementations across different programming languages.

What is the best way to create a portable contract for multi-language reimplementation?

The best way to create a portable contract for multi-language reimplementation is to generate a ghost artifact bundle. This process collects and paraphrases upstream documents into a language-neutral spec set while preserving licensing and provenance for reproducible verification.