agentleFS
poorvith-mppoorvith-mp/skills-personal/skills/3d-printing/SKILL.md

3d-printing

Skill1 starsChanged 3 months agoMITView on GitHub

Tune filament profiles: temperature, flow, retraction and cooling against material and printer. Use when troubleshooting FDM/resin slicing, print bed adhesion, or layer lines.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start with temperature: Run a temperature tower for the specific filament and spool.

    line 17
  2. Distinctive:

    NEVER weaken or skip a failing test to make a change land.

    line 37
  3. Distinctive:

    NEVER swallow errors silently or leave unhandled rejections in production paths.

    line 38
  4. Distinctive:

    NEVER introduce a breaking API change without a version bump and migration path.

    line 39

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

3D Printing

Diagnose 3D print quality problems that trace back to material and thermal settings.

Process

  1. Identify the symptom precisely — stringing, layer separation, warping, under-extrusion, elephant foot and poor overhangs each point at different settings.
  2. Change one variable at a time. Print a calibration tower rather than adjusting four settings and printing one part.
  3. Start with temperature. Run a temperature tower for the specific filament and spool; published ranges are a starting point, not a value.
  4. Then flow and extrusion multiplier, measured against a single-wall cube's actual wall thickness.
  5. Then retraction — distance and speed, tuned on a stringing test, and different for direct drive versus bowden.
  6. Then cooling, which trades overhang quality against layer adhesion. PLA and ABS want opposite answers.
  7. Record the working profile per filament and printer, including ambient conditions. Humidity in the filament explains a surprising share of unexplained failures.

Deliverables

  • Symptom-to-cause diagnosis
  • Calibration sequence with one variable per test
  • Saved profile per material and printer with conditions noted

Verification & Quality Checklist

  • Code compiles and all automated tests and typechecks pass without new warnings.
  • Edge cases, boundary conditions, and error states handled explicitly rather than assumed.
  • No hardcoded secrets, credentials, or insecure defaults introduced.
  • Changes are covered by a test that fails without them.

Anti-Patterns & Constraints

  • NEVER weaken or skip a failing test to make a change land.
  • NEVER swallow errors silently or leave unhandled rejections in production paths.
  • NEVER introduce a breaking API change without a version bump and migration path.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.