find-stl

This skill serves as a deterministic pipeline for AI agents tasked with physical prototyping and additive manufacturing. It allows an agent to bridge the gap between a design concept and a physical 3D-printable object by automating the search, validation, and acquisition of model files from Printables. Instead of relying on manual browsing, the agent uses this tool to locate suitable parts, verify file types, and organize them into a project-ready directory.

The skill provides a structured manifest.json for every downloaded model, ensuring that attribution, license IDs, and file checksums are recorded, which is critical for compliance and professional project tracking. It is designed for engineers, makers, and designers who need to rapidly fetch verified CAD or mesh assets (STL, 3MF, ZIP) for immediate printing or inspection.

• Automated Printables GraphQL integration to resolve time-limited download links effectively.

• Direct command-line interaction for targeted searching, limiting results, and fetching full model packages.

• Manifest generation that captures source URLs, author details, license information, and file hashes to maintain clear project documentation.

• Batch-ready file organization, placing all assets into dedicated output directories for integration with slicer software or further CAD modification.

• Supports multi-format acquisition, prioritizing printable file types like STL and 3MF to streamline the manufacturing readiness phase.

• Ensure you have Python 3 installed to run the underlying scripts in the scripts/ directory.

• Always review the license information generated in the manifest.json to ensure compliance with the model author's requirements.

• The tool is best used in a pipeline where an agent first identifies a part requirement (e.g., 'iphone 15 pro dock') and then executes a download followed by a notification to the user for printing.

• Be aware that Printables download links are transient; the agent script manages session state through its native API integration, but results should be processed promptly.

• Typical inputs include descriptive search queries, and outputs consist of organized local folders containing the model source files alongside the mandatory manifest.