makerworld-publish
Skill2 starsChanged 26 days agoMITView on GitHub
Use when a model is ready to be published on MakerWorld and needs its licence choice, print profiles, photos and monetisation plan checked against MakerWorld's own pages. Runs the business-strategist in a fresh context and writes a publish plan whose every rule is quoted from a fetched MakerWorld URL.
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
- 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
- slicer-questionSkill
- style-bibleSkill
- tech-packSkill
- unit-costSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 14
After the model prints and /preprint-check has passed on its 3MF.
≈ “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
Publish plan for: $ARGUMENTS
Output on disk: <model folder>\makerworld\publish-plan.md (licence choice with quoted rule, files, profiles, photo checklist, money mechanics, tracking row) and, if anything could not be fetched, research\inbox\makerworld\<model-slug>.md. This skill never uploads anything; the maker publishes by hand.
When to use
After the model prints and /preprint-check has passed on its 3MF; before the upload. Not for pricing physical sales (/unit-cost), not for the IP facts themselves (/ip-check must already have a file on record for this design).
Steps
- Fetch this run, with WebFetch (curl fallback on HTTP 402/403): https://makerworld.com/en/user-agreement, https://makerworld.com/en/exclusive-model-policy, https://makerworld.com/en/faq, https://wiki.bambulab.com/en/makerworld/tutorials/creator-commission-incentives. Record the "last updated" or page date for each. Never use a remembered number.
- Build the licence matrix from the fetched text: for the Standard Digital File Licence, MakerWorld Exclusive and each Creative Commons option offered in the upload form, one row each with short quoted permissions (about 15 words at most per quote) for commercial use of prints, remixing, re-hosting, and where derivatives may be published. Link a verified MakerWorld note in
knowledge\if one exists and skip rows it already covers. - Match the matrix to the intent argument; list what the intent rules out. If AI tools generated any part of the model, quote the page's rule on AI-generated content and Exclusive eligibility. Undecided: numbered NEEDS MAKER questions.
- Files: list every STL/3MF with path. Profiles: one per printer you publish for (
knowledge\00-gear-inventory\), each sliced with the installed CLI perknowledge\02-bambu-studio\cli-slicing.md(tools\slice_cli.py), each with a/preprint-checkPASS path. No PASS, no profile in the plan. - Photos: quote the real-print photo rule from the fetched page; checklist per listing image (which print, which plate, which filament as recorded in the load record in
knowledge\00-gear-inventory\). - Money: quote the point value, cash-out threshold, boost mechanics, membership fee and commission rates from the fetched pages with dates; add a tracking row template (date, downloads, boosts, points, cash-out).
- Confirm
research\ip\has a file for this design; if not, stop and returnNEEDS: /ip-check. Write the plan; return paths and NEEDS MAKER questions.
Common rationalizations
| Rationalization | Reality |
| "I remember the point value." | Remembered numbers drift. Fetch the page; quote with date. |
| "A render is fine for the cover photo." | Quote MakerWorld's real-print photo rule from the fetched page and follow it. |
| "One printer's profile will work on the other." | Different printer, different profile; each is sliced and /preprint-check-ed separately. |
| "The licence does not matter for a free model." | The licence sets what others may do with it. Choose from the quoted matrix against the maker's intent. |
Red flags (stop and fix)
- A rule or number in the plan with no fetched URL and date beside it.
- A profile listed without a
/preprint-checkPASS path. - No
/ip-checkfile for the design. - Licence chosen while intent is "undecided".
- Any upload, publish or print action: this skill only writes a plan.
Verification
- All four MakerWorld URLs fetched this run; page dates recorded in the plan.
- Licence matrix rows are quotes, each with URL.
- Each profile names its 3MF path and its
/preprint-checkPASS path. /ip-checkfile path cited.publish-plan.mdwritten; paths and NEEDS MAKER questions returned.
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.

