fluxly Search skills… ⌘K 中文 Publish

solidworks-cad

Design Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Design
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
85 / 100 · community maintained
Author / version / license
@Soljourner · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Python
Permissions
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。; 上游仓库已 211 天未更新，可能与最新 agent 行为不一致。

Output preview solidworks-cad.preview 
---
name: solidworks-cad
description: Automate parametric pump impeller design in SolidWorks via API This skill provides guidance for…
category: design
runtime: Python
---

# solidworks-cad output preview

## PART A: Task fit
- Use case: Automate parametric pump impeller design in SolidWorks via API This skill provides guidance for automating parametric pump impeller design and other mechanical component modeling using the SolidWorks API. SolidWorks provides a comprehensive API that allows users to automate design tasks, create parametric models, manipulate assemblies, and generate drawin….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Overview of SolidWorks API / Licensing Requirements / API Access Methods” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Automate parametric pump impeller design in SolidWorks via API This skill provides guidance for automating parametric pump impeller design and other mechanical component modeling using the SolidWorks API. SolidWorks provides a comprehensive API that allows users to automate design tasks, create parametric models, manipulate assemblies, and generate drawin…”.
- **02** When the source has headings, the agent prioritizes “Overview of SolidWorks API / Licensing Requirements / API Access Methods” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: Automate parametric pump impeller design in SolidWorks via API This skill provides guidance for automating parametric pump impel…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “Overview of SolidWorks API”, “Licensing Requirements”, “API Access Methods”, “1. VBA Macros”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name solidworks-cad directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “Overview of SolidWorks API / Licensing Requirements / API Access Methods” before expanding.

Boundaries And Review

  • Dependencies: It usually needs no extra API key, so start with a small validation task.
  • Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.