material-pick
Skill2 starsChanged 25 days agoMITView on GitHub
Use when a part needs a filament choice with the numbers that justify it (HDT at both loads, drying, bed temperature, compatibility). Runs the materials-scientist in a fresh context and returns the recommendation with URLs; the lead saves it beside the part spec.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-reviewSkill
- ai-mesh-cleanSkill
- cad-buildSkill
- couponSkill
- curriculumSkill
- dfm-reviewSkill
- fileSkill
- gddSkill
- ip-checkSkill
- led-budgetSkill
- lesson-learnedSkill
- makerworld-publishSkill
- mcp-new-toolSkill
- ortho-sheetSkill
- pi-power-budgetSkill
- preprint-checkSkill
- promo-planSkill
- qa-gateSkill
- render-criticSkill
- research-oneSkill
- research-topicSkill
- retopoSkill
- safety-sheetSkill
- sculptSkill
- slicer-questionSkill
- style-bibleSkill
- tech-packSkill
- unit-costSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Before a material is written into a part spec or a 3MF.
- Very specific: line 15
Read knowledge\03-materials\ (the PLA vs PETG, HDT/Vicat and drying notes) and cite the notes and their URLs.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Overview
Input: $ARGUMENTS: the part and where it lives (heat, load, outdoors, contact with electronics). Output: a recommendation table in the reply (materials-scientist has no Write tool).
When to use
Before a material is written into a part spec or a 3MF; whenever an environment changes.
Steps
- Read
knowledge\03-materials\(the PLA vs PETG, HDT/Vicat and drying notes) and cite the notes and their URLs. - For anything missing, fetch the TDS or wiki page (Bash only for
curl -sL -A "Mozilla/5.0"on HTTP 402/403) and queue the new fact to/research-one. - Table per candidate: HDT at 1.8 / 0.45 MPa (test condition), Vicat, the drying row for your AMS or dryer, bed temperature for your plate (
knowledge\00-gear-inventory\), temperature class (low/high), verdict. - Recommend one material, named exactly (brand, line, colour where it matters) as a requirement; never assume it is loaded or owned. List alternatives with their costs and a "Not verified" list.
Common rationalizations
| Rationalization | Reality |
| "69 C is the HDT." | Without the load it is PARTIAL; TDS values are for annealed or standard specimens, not your print. |
| "PLA is fine, it's indoors." | Check the vendor's softening figure; a closed enclosure with electronics inside is not room air. |
Red flags
- A number without unit, load or URL.
- Mixing low-temp and high-temp classes in one job.
Verification
- Every candidate row sourced.
- AMS or dryer limit and drying rows cited.
- One recommendation, alternatives, Not verified list.
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.

