# Automate Grasshopper Modeling Workflows

Grasshopper workflows often require many repeated component, connection, and parameter steps. This skill provides scripts and guidance to turn MMD plans into executable Grasshopper MCP workflows.

## Install

```bash
npx skillstore add amemiyalai/grasshopper-workflow
```

## Metadata

- - Slug: amemiyalai-grasshopper-workflow
- - Version: 1.0.0
- - Author: AmemiyaLai
- - GitHub username: AmemiyaLai
- - License: MIT
- - Repository: https://github.com/AmemiyaLai/grasshopper-mcp-workflow/tree/main/grasshopper-workflow/
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: medium
- - Risk factors: scripts, network, filesystem
- - Quality score: 50
- - Quality tier: warning
- - Public page: https://skillstore.pages.dev/skills/amemiyalai-grasshopper-workflow
- - Manifest: https://skillstore.pages.dev/api/skills/amemiyalai-grasshopper-workflow/manifest

## Capabilities

- Parse component\_info.mmd files into component and connection data.
- Generate placement\_info.json plans from parsed MMD structures.
- Create Grasshopper components through a local MCP client.
- Connect generated components and set slider or vector values.
- Create grouped Grasshopper components with optional colors.
- Run a CLI for parsing, generation, placement, grouping, and error checks.

## Use Cases

- Generate Parametric Layouts: Convert MMD component plans into structured placement steps for a Grasshopper definition.
- Automate Repetitive Grasshopper Setup: Create components, connect nodes, set sliders, and group related model sections with less manual work.
- Review MCP Modeling Workflows: Inspect generated placement plans before executing them against a local Grasshopper session.

## Prompt Templates

### Explain The Workflow

```
Explain how this Grasshopper workflow skill turns component_info.mmd into a Grasshopper definition. Keep the steps concise.
```

### Create A Placement Plan

```
Use the skill references to plan how I should generate placement_info.json from my component_info.mmd file.
```

### Debug Failed Connections

```
Review my Grasshopper workflow failure and identify likely causes in component IDs, parameter names, or connection order.
```

### Audit A Full Automation Run

```
Evaluate this placement workflow before execution. Check component creation, connection dependencies, slider ranges, grouping, and local file risks.
```

## Limitations

- Requires a running Grasshopper MCP server, usually on localhost port 8080.
- Works only with component formats and GUID mappings supported by the scripts.
- Does not validate all design intent before changing the Grasshopper document.
- Can overwrite local output files when users provide unsafe paths.

## Best Practices

- Review generated placement plans before executing them in Grasshopper.
- Use project-local input and output paths to avoid overwriting unrelated files.
- Run the MCP server only for trusted local Grasshopper sessions.

## Anti Patterns

- Do not execute placement files from untrusted sources without review.
- Do not point output arguments at important existing files.
- Do not assume every Grasshopper component name has a supported GUID mapping.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T09:12:11.808\+00:00
- - Summary: AI review did not confirm the static scanner high-risk malware indicators. Most external command, weak crypto, C2, reconnaissance, and entropy hits are false positives caused by Markdown examples, Grasshopper command names, and UUID-like component GUIDs. The remaining risk is medium because the skill includes Python scripts that read and write local files and send user-provided modeling commands to a local Grasshopper MCP socket.

## Stats

- - Views: 213
- - Downloads: 11
- - Favorites: 0
- - Popularity score: 0