Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for /printing-press-polish or /printing-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a broken/lost internal copy. Trigger phrases: "import the CLI", "bring it into my library", "fetch from public library", "I don't have it locally yet".
Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for /printing-press-polish or /printing-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a broken/lost internal copy. Trigger phrases: "import the CLI", "bring it into my library", "fetch from public library", "I don't have it locally yet".
allowed-tools
Bash, Read, Glob, Grep, AskUserQuestion
created_by
user
/printing-press-import
Bring a published CLI from the public library
()
into the internal library at so it matches
the form the generator would produce. Manuscripts ride along.
5 files · 17 KB10 KB
Install
It’s free, and every skill you add syncs into every AI tool on your computer, instantly.
The internal library is the working copy; the public library is the
durable artifact. After import, the CLI is ready for polish, emboss, or
re-publish — the publish step will re-apply the module path rewrites.
When to run
The public library has a CLI you don't have locally
The internal copy is broken, lost, or out of sync
You want a clean baseline before running polish on a published CLI
If the user is asking to polish a CLI and mentions "in/from the public
library" or "from the repo", suggest running this skill first.
Setup
PRESS_HOME="${PRINTING_PRESS_HOME:-$HOME/printing-press}"
PRESS_LIBRARY="$PRESS_HOME/library"
PRESS_MANUSCRIPTS="$PRESS_HOME/manuscripts"
SCRIPTS_DIR="$(dirname "${BASH_SOURCE[0]:-.}")/references"if ! command -v go >/dev/null 2>&1; thenecho""echo"[setup-error] Go toolchain not found."echo""echo"This Printing Press flow runs Go-based build or validation commands."echo"Install Go 1.26.6 or newer from https://go.dev/dl/, then verify with:"echo" go version"echo"Then re-run this skill."echo""return 1 2>/dev/null || exit 1
fi_pp_check_disk_space() {
_pp_disk_warn_kb="${PRINTING_PRESS_DISK_WARN_KB:-3145728}"
_pp_disk_fail_kb="${PRINTING_PRESS_DISK_FAIL_KB:-524288}"case"$_pp_disk_warn_kb$_pp_disk_fail_kb"in""|*[!0-9]*) return 0 ;;
esac
_pp_disk_path="$PRESS_HOME"while [ ! -e "$_pp_disk_path" ] && [ "$_pp_disk_path" != "/" ]; do
_pp_disk_path="$(dirname "$_pp_disk_path")"done
_pp_disk_avail_kb="$(df -Pk "$_pp_disk_path" 2>/dev/null | awk 'BEGIN {
if ((getline header) <= 0 || (getline record) <= 0) exit
field_count = split(record, fields)
if (field_count >= 4) print fields[4]
}')"case"$_pp_disk_avail_kb"in""|*[!0-9]*) return 0 ;;
esacif [ "$_pp_disk_avail_kb" -lt "$_pp_disk_fail_kb" ]; thenecho""echo"[setup-error] Critically low disk space on the Printing Press workspace volume."echo"PRESS_DISK_PATH=$_pp_disk_path"echo"PRESS_DISK_AVAIL_KB=$_pp_disk_avail_kb"echo"PRESS_DISK_FAIL_KB=$_pp_disk_fail_kb"echo"Free disk space or set PRINTING_PRESS_HOME to a volume with more room, then re-run this skill."echo""return 1
fiif [ "$_pp_disk_avail_kb" -lt "$_pp_disk_warn_kb" ]; thenecho""echo"[low-disk] Printing Press workspace volume is low on free space."echo"PRESS_DISK_PATH=$_pp_disk_path"echo"PRESS_DISK_AVAIL_KB=$_pp_disk_avail_kb"echo"PRESS_DISK_WARN_KB=$_pp_disk_warn_kb"echo"This flow may need several GiB for generated files, Go build cache, module downloads, or repository clones."echo""fi
}
_pp_check_disk_space || { return 1 2>/dev/null || exit 1; }
The four reference scripts live alongside this SKILL.md under
references/:
import-backup.sh <api-slug> (prints zip path on stdout)
import-rewrite.sh <staging> <api-slug>
import-place.sh <staging> <api-slug>
If setup emitted [low-disk], surface the advisory to the user and continue unless setup also emitted [setup-error]. [low-disk] means this run may need several GiB for repository clones, staged files, backups, Go build cache, or module downloads.
Phase 1 — Resolve the CLI
The argument can be anything natural: an API slug (notion), a brand
name (cal.com), an old CLI name (notion-pp-cli), or close enough
(Allrecipes). Resolve via the public library's registry.json —
which carries name, category, api, description, and path for
every entry, in one fetch.
If you get one match: use it. If multiple: present at most 4 to the user
via AskUserQuestion showing name + description per candidate. If
zero: tell the user the public library doesn't have that CLI.
The matched entry gives you everything you need:
LIB_PATH from .path (e.g., library/productivity/cal-com)
API_SLUG from .name
CATEGORY from .category
Don't slurp whole files when reasoning over candidates. The fields
above are enough; if you genuinely need more, the per-CLI manifest is
just <LIB_PATH>/manifest.json and the description there can be pulled
the same way (gh api -H "Accept: ... raw" .../manifest.json | jq -r '.description').
Phase 2 — Decide on overwrite
Check whether the internal library already has this CLI:
If neither exists: straightforward import — proceed to Phase 3.
If either exists: read provenance from both sides to decide whether
to overwrite. Don't read whole .printing-press.json files — pull just
the fields that matter:
Same run_id — public is the same generation as internal. Likely
no-op; ask before clobbering. If the user wants to import anyway
(e.g., to recover from a broken internal copy), proceed.
Public newer generated_at — public has changes the internal
doesn't. Importing is the safe move; ask the user to confirm.
Internal newer generated_at — internal has work the public
doesn't (in-progress polish, manual fixes). Importing would clobber
that. Stop and surface this to the user — they likely want to publish
the internal changes first.
Either side missing .printing-press.json — older or hand-imported.
Ask the user.
When the user confirms overwrite, the backup step in Phase 3 captures
the current internal state.
Phase 3 — Import
STAGING=$(mktemp -d)
# Fetch (remote unless --from-clone was passed)if [[ -n "${CLONE_PATH:-}" ]]; then
bash "$SCRIPTS_DIR/import-fetch.sh""$LIB_PATH""$STAGING" --clone"$CLONE_PATH"else
bash "$SCRIPTS_DIR/import-fetch.sh""$LIB_PATH""$STAGING"fi# Backup if anything is being clobbered. Prints zip path on stdout.if [[ -d "$LIB_TARGET" || -d "$MAN_TARGET" ]]; then
BACKUP_ZIP=$(bash "$SCRIPTS_DIR/import-backup.sh""$API_SLUG")
echo"Backed up to: $BACKUP_ZIP"fi# Reverse the publish-step module path rewrites.
bash "$SCRIPTS_DIR/import-rewrite.sh""$STAGING""$API_SLUG"# Atomically move staging into place.
bash "$SCRIPTS_DIR/import-place.sh""$STAGING""$API_SLUG"
Phase 4 — Verify internal consistency
After the move, confirm the imported CLI builds and is structurally
intact. Treat any failure as a real problem — don't paper over it.
cd"$LIB_TARGET"# Module path is local form
grep -q "^module ${API_SLUG}-pp-cli\$" go.mod \
|| { echo"FAIL: go.mod still on public module path"; exit 1; }
# No public module path leaked into sourceif grep -rq "github.com/mvanhorn/printing-press-library/library" \
--include='*.go' --include='*.yaml' --include='*.yml' .; thenecho"FAIL: source still references public module path"exit 1
fi# Build
go build ./... \
|| { echo"FAIL: go build"; exit 1; }
# Doctor (self-check)
make doctor 2>/dev/null \
|| ./bin/${API_SLUG}-pp-cli doctor 2>/dev/null \
|| true# best-effort; not all CLIs have doctor wired the same way
