print-request-inbox

Capture Discord 3D print requests and extract model metadata into a local queue.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/DisruptionEngineer/build-useful-skills --skill print-request-inbox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: print-request-inbox
Source: https://github.com/DisruptionEngineer/build-useful-skills/tree/main/print-request-inbox
Command: npx skills add https://github.com/DisruptionEngineer/build-useful-skills --skill print-request-inbox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture 3D print requests posted in Discord's #print-requests channel, extract model metadata from supported URLs and plain text, and log them for downstream evaluation and fulfillment.

Core Features & Use Cases

  • Ingests MakerWorld, Thingiverse, Printables, or plain text descriptions from authorized users.
  • Extracts model metadata, assigns a unique PR-XXXX ID, and stores requests in a structured local queue for tracking.
  • Routes requests to the evaluation pipeline and confirms receipt in the channel.

Quick Start

Post a MakerWorld, Thingiverse, or Printables link (or a plain description) in the #print-requests channel to create a new print request.

Frequently Asked Questions about print-request-inbox

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

FAQPage Schema
How do I automatically capture Discord 3D print requests and extract model metadata?

Capturing Discord 3D print requests and extracting model metadata is done by monitoring the #print-requests channel, parsing supported URLs like MakerWorld and Thingiverse, and logging them into a structured local queue using an Ollama Qwen3 8B model.

What 3D model platforms are supported for extracting print request metadata?

Supported 3D model platforms for extracting print request metadata include MakerWorld, Thingiverse, and Printables URLs, as well as plain text descriptions. The system automatically parses these links to capture the required model information for the queue.

How do I assign a unique ID to 3D print requests in a Discord queue?

Assigning a unique ID to 3D print requests in a Discord queue is handled automatically by generating a PR-XXXX identifier for each validated submission when it is persisted to the local data directory at ~/.agents/data.

Do I need an Ollama model to process plain text 3D print requests?

Yes, an Ollama Qwen3 8B model is required to process plain text 3D print requests and supported URLs for accurate metadata extraction before assigning a unique PR-XXXX ID.

What is the best way to track 3D print request status for downstream evaluation?

Tracking 3D print request status for downstream evaluation is best achieved by persisting captured Discord submissions in a structured local queue file using a defined schema that triggers system routing to the evaluation pipeline.

Can I restrict Discord print requests to authorized users only?

Yes, restricting Discord print requests to authorized users only is supported by applying user validation rules before metadata extraction, ensuring only approved submissions receive a unique PR-XXXX ID and enter the local queue.