[object Object]

← back to Cli Printing Press

fix(skills): correct briefing copy for CLI output description (#98)

23648d4791ec756b2b1c590d53047fe597d7773e · 2026-03-31 19:39:44 -0700 · Matt Van Horn

The briefing said users could "publish to the printing-press library"
which implies automatic inclusion. Users actually ship the CLI themselves
or apply to add it to the library.

Co-authored-by: Matt Van Horn <455140+mvanhorn@users.noreply.github.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Files touched

Diff

commit 23648d4791ec756b2b1c590d53047fe597d7773e
Author: Matt Van Horn <mvanhorn@users.noreply.github.com>
Date:   Tue Mar 31 19:39:44 2026 -0700

    fix(skills): correct briefing copy for CLI output description (#98)
    
    The briefing said users could "publish to the printing-press library"
    which implies automatic inclusion. Users actually ship the CLI themselves
    or apply to add it to the library.
    
    Co-authored-by: Matt Van Horn <455140+mvanhorn@users.noreply.github.com>
    Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---
 skills/printing-press/SKILL.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/skills/printing-press/SKILL.md b/skills/printing-press/SKILL.md
index 9160c439..3fab88a4 100644
--- a/skills/printing-press/SKILL.md
+++ b/skills/printing-press/SKILL.md
@@ -100,7 +100,7 @@ If the user typed `/printing-press` with no arguments (no API name, no `--spec`,
 
 > The Printing Press generates a fully functional CLI for any API. You give it an API name, a spec file, or a URL. It researches the landscape, catalogs every feature that exists in any competing tool, invents novel features of its own, then generates a Go CLI that matches and beats everything out there — with offline search, agent-native output, and a local SQLite data layer.
 >
-> By the end, you'll have a working CLI in `~/printing-press/library/` that you can use for yourself, distribute within your company, or publish to the printing-press library.
+> By the end, you'll have a working CLI in `~/printing-press/library/` that you can use for yourself, ship on your own, or apply to add to the printing-press library.
 >
 > The process takes 10-40 minutes depending on API complexity. Simple APIs with official specs (Stripe, GitHub) are faster. Undocumented APIs that need discovery (ESPN, Domino's) take longer.
 
@@ -136,7 +136,7 @@ Print as prose (in Victorian voice):
 > 3. I shall present what I found and what I invented — you will have a chance to add your own ideas or adjust the plan before I build
 > 4. I shall generate a Go CLI, build every feature from the plan, then verify quality through dogfood, runtime verification, and scoring
 >
-> **What you will have at the end:** A fully functional CLI at `~/printing-press/library/<api>-pp-cli` that you can use yourself, share within your company, or publish to the printing-press library.
+> **What you will have at the end:** A fully functional CLI at `~/printing-press/library/<api>-pp-cli` that you can use yourself, ship on your own, or apply to add to the printing-press library.
 >
 > **Time:** 10-40 minutes depending on API complexity.
 >

← 63970f8f feat(skills): add proactive auth intelligence and session tr  ·  back to Cli Printing Press  ·  fix(skills): fix authenticated sniff session transfer daemon 34a91421 →