setup-autodesk-fusion
Skill18 starsChanged 2 months agoApache-2.0View on GitHub
Configure and diagnose Fusion interoperability, transport selection, scoped profiles and qualification. Use for setup or connection problems, not design edits.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- create-fusion-deliverablesSkill
- edit-fusion-designSkill
- handoff-fusion-engineeringSkill
- inspect-fusion-designSkill
- prepare-fusion-manufacturingSkill
- reconcile-fusion-dataSkill
- run-fusion-cloud-recipesSkill
- analyze-log-signalsSkill
- inspect-infrastructure-healthSkill
- investigate-application-performanceSkill
- monitor-iot-edgeSkill
- review-business-kpisSkill
- setup-grafana-observabilitySkill
- audit-ios-readinessSkill
- plan-react-native-portSkill
- port-react-native-sliceSkill
- verify-swiftui-paritySkill
- audit-review-eval-validitySkill
- benchmark-review-configsSkill
- normalize-review-runsSkill
- recommend-review-reference-architectureSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 6
Call fusion_connection_status and fusion_capabilities_list first.
- Distinctive: line 12
Use a trusted private profile for the user's scope.
- Distinctive: line 16
Run qualification on approved synthetic documents.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Call fusion_connection_status and fusion_capabilities_list first. Distinguish synthetic fixture, managed and assisted modes. Fixture output is not evidence that Autodesk is installed.
Read setup and resolve the installed plugin root. Use its bundled CLI without startup npm. Discover the explicitly configured native endpoint and enroll the actual Python tool/schema hash; never guess tools, scan ports or silently switch transports. For the typed add-in, install the assembled package and follow the add-in guide.
For additional required native arguments, use native-enroll --fixed-arguments-file with a trusted absolute JSON-object file and explicitly reviewed values. Do not infer defaults, reuse an old mapping's values or override the script argument. An optional --url is saved as the selected endpoint. Enrollment rejects changed profiles and never executes the native tool or establishes qualification.
Use a trusted private profile for the user's scope. Existing valid grants cover routine work; changed target, billing, publication or manufacturing risk needs matching authority. Never edit policy to bypass a denial or invent qualification evidence.
Cloud PKCE and native Data MCP authentication are separate. Let the user complete the supported Autodesk sign-in URL; never collect passwords or copy Codex credentials. Enterprise extensions are privileged deployment code.
Run qualification on approved synthetic documents. Report the connection evidence and exact remaining configuration or licensed-environment gate.
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.

