agentleFS
OpenAIKnown publisheropenai/community-plugins/plugins/autodesk-fusion/skills/edit-fusion-design/SKILL.md

edit-fusion-design

Skill18 starsChanged 2 months agoApache-2.0View on GitHub

Prepare, execute and verify authorized Fusion CAD changes using resolved entities, explicit units and state-bound plans. Use for reviewed parameter, sketch, feature, assembly or configuration operations.

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
  1. Very specific:

    Verify meaningful numerical postconditions and feature health.

    line 14

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

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

Inspect the selected document and exact operation schema. Resolve design intent, units, frame, occurrence context and configuration. Generated configuration instances and external sources are not implicitly editable.

Prepare one operation with fusion_changes_prepare; review inputs, effects, state and policy blockers. Execute the unchanged hash with a unique idempotency key under the existing scoped grant. Prepare dependent operations only after inspecting the previous result. Parameter batches have documented local atomicity; feature sequences and cross-system writes do not.

Preserve driving constraints and parametric history. Never convert to direct mode, break references, fetch latest versions or interrupt an active command as a convenience.

For offset planes, sweep, loft, draft, split-body and mirror, read the CAD feature contracts. Keep native geometry in one editable component, explicit cut/intersect participants, ordered loft sections and exact sweep-path membership. Mirror creates separate bodies; split does not preserve unsplit originals. Draft's optional tangent/symmetric flags expand its effect and must be part of the reviewed request. Reinspect changed construction planes or axes before using their handles.

Verify meaningful numerical postconditions and feature health. Reinspect stale state. For partial/unknown outcomes, inspect receipts and the model before any new write; never blindly replay. fusion_recovery_prepare does not silently undo user work.

Saving is a separate cloud effect. Unsupported variants stay explicit. Assisted native tools require their separate broad grant and have different guarantees. See workflow.

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.