slicer-question
Skill2 starsChanged 25 days agoMITView on GitHub
Use when a Bambu Studio setting, grouping, AMS mapping or 3MF question needs an answer with exact UI labels and config keys. Runs the bambu-studio-expert in a fresh context and writes the answer with sources to work\reports\answers\<slug>.md.
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
- material-pickSkill
- mcp-new-toolSkill
- ortho-sheetSkill
- pi-power-budgetSkill
- preprint-checkSkill
- promo-planSkill
- qa-gateSkill
- render-criticSkill
- research-oneSkill
- research-topicSkill
- retopoSkill
- safety-sheetSkill
- sculptSkill
- style-bibleSkill
- tech-packSkill
- unit-costSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Read the notes in knowledge\02-bambu-studio\ first.
- Very specific: line 16
If the question names a 3MF, run .venv\Scripts\python.exe tools\audit_3mf.py <3mf> --json and quote the relevant keys.
- Distinctive: line 18
Write the answer file; return the path.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 as <slug> | <question>. Output: work\reports\answers\<slug>.md (60 lines or fewer; every claim with a URL or repo path; UI labels as Tab > Section > Setting with the config key; unverified labels marked "(label not verified)").
When to use
Any slicer question: settings, grouping, prime tower, profiles, CLI, 3MF contents. Not for gating a file before printing (/preprint-check) and not for raw research of a new fact (/research-one).
Steps
- Read the notes in
knowledge\02-bambu-studio\first; cite them rather than restating. Readknowledge\00-gear-inventory\for your printers and nozzles. - If the question names a 3MF, run
.venv\Scripts\python.exe tools\audit_3mf.py <3mf> --jsonand quote the relevant keys; resolve profile values withtools\resolve_profile.py. - For anything not in a note, fetch the source (PrintConfig.cpp and GUI .cpp files of https://github.com/bambulab/BambuStudio via raw.githubusercontent.com, and https://wiki.bambulab.com; curl on 402/403) and quote briefly with line numbers. New facts also go to
research\inbox\bambu-studio\<slug>.mdfor/verify. - Write the answer file; return the path.
Common rationalizations
| Rationalization | Reality |
| "I know this setting." | Notes seeded from memory were wrong several times. Read the note or the source. |
| "The label is close enough." | You need Tab > Section > Setting exactly, or "(label not verified)". |
Red flags
- A setting named without its config key or a URL.
- Editing or slicing a 3MF while
knowledge\00-gear-inventory\current-load.mdis missing or undated.
Verification
- Answer file exists at the output path.
- Every claim has a URL or repo path; every UI label has its config key.
- New facts queued in
research\inbox\.
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.

