printer

Print existing workspace PDF, TXT, DOCX, and image files to the default printer.

9|1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/flaz78/9Lives --skill printer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: printer
Source: https://github.com/flaz78/9Lives/tree/main/workspace/skills/printer
Command: npx skills add https://github.com/flaz78/9Lives --skill printer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you print local documents from your 9Lives workspace without manually opening apps and finding the correct file and printer settings.

Core Features & Use Cases

  • Local file printing: Sends an existing workspace file (PDF, TXT, DOCX, images) to the default printer.
  • Print control: Supports optional page count via copies and optional destination via printer name (Linux/CUPS).
  • Safe, predictable execution: Validates that filePath exists in the workspace and follows clear confirmation rules before printing when quantities are ambiguous.

Quick Start

Ask the agent to print the file storage/output/report.pdf on the default printer with one copy.

Frequently Asked Questions about printer

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

FAQPage Schema
How do I print local workspace files like PDFs and DOCX without opening an app?

You can print local workspace files by sending existing PDFs, TXT, DOCX documents, and images directly to a default printer for immediate physical document delivery, bypassing manual application setups.

Can I choose a specific printer and set copy counts for document delivery?

Yes, local printing supports optional destination selection via printer name and optional page count through copies, allowing deterministic physical document delivery on Linux/CUPS systems.

What happens if I try to print a file that is not in my local workspace?

Printing requires validating the filePath against the workspace first. If the file does not exist in the workspace, the process will fail to ensure safe, predictable execution before sending to the printer.

Why does local printing fail when no printing backend is available?

Local printing fails without a backend because the system requires a configured default printer to execute the physical document delivery, emitting a clear error so you can check your printing setup.

Is CUPS required to print documents from a local-first workspace?

A printing backend like CUPS is required for Linux systems to handle the destination printer name and execute the physical printing of your local-first workspace files.

What is the best way to get immediate physical document delivery for a TXT file?

The best way is to use deterministic local printing to send the existing TXT workspace file directly to the configured default printer, ensuring immediate physical output without manual steps.