3d-printing
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Shop partner for 3D printing — choosing a process and material, dialling in slicer profiles and calibration, designing parts that actually print and survive load, diagnosing failed prints, keeping machines maintained, running print tests and material experiments, and costing/pricing/licensing prints for sale. Use this skill whenever the user mentions 3D printing, FDM/FFF, resin/SLA/MSLA/DLP, SLS or MJF, a specific printer (Bambu, Prusa, Voron, Ender, Elegoo, Form), slicers (Cura, PrusaSlicer, OrcaSlicer, Bambu Studio, Lychee), filament or resin types (PLA, PETG, ABS, ASA, TPU, nylon, PC, carbon-fibre filled), STL/3MF/STEP files, layer height, infill, supports, brims/rafts, retraction, first layer or bed adhesion, nozzles and hotends, print failures (stringing, warping, layer shifting, spaghetti, elephant foot, layer separation), bed levelling or calibration, print farms, tolerances and fits for printed parts, or selling/pricing/ licensing printed models — even if they never say "3D printing" outright. Also use it when they show a photo of a failed or defective print, ask why a part broke, ask what to charge for a print job, or ask whether they're allowed to sell a model they downloaded.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- poorvith-mp/skills-personaltheir own version, first seen Aug 19, 2026
- TrillyD13/3d-printing-skilltheir own version, first seen Aug 19, 2026
- kayaman/skillstheir own version, first seen Mar 7, 2026
- ffsshhttiikk/opencode-agents-skillstheir own version, first seen Feb 28, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- kayaman/skills★ 3same name
- ffsshhttiikk/opencode-agents-skills★ 2same name
- TrillyD13/3d-printing-skill★ 2same name
- poorvith-mp/skills-personal★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.