Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
Utilizes the Vectorworks RAG + MCP server to search and retrieve Python and VectorScript API documentation.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
This skill file instructs AI agents on how to utilize the Vectorworks RAG (Retrieval-Augmented Generation) and MCP server. It details documentation searches, VectorScript code generation, and troubleshooting steps.
The Vectorworks RAG + MCP Server integrates local Vectorworks Python and VectorScript developer documentation. Using sentence-transformers and a FAISS semantic index, it provides immediate API lookups and code generation recommendations directly to AI models. This avoids syntax hallucinations when generating CAD or BIM layout scripts.
/search, /answer) and a WebSocket JSON-RPC 2.0 interface (default port 8765) acting as the MCP endpoint.vw.answer to receive a detailed breakdown with citations. Do not write complex routines without consulting the retrieved document chunks first.The server provides three tools via WebSocket:
| Tool | Parameters | Description |
|---|---|---|
vw.search | query: string, k?: int (default 6) | Returns semantic search hits from the Vectorworks SDK/VectorScript references. |
vw.answer | query: string, k?: int | Returns a draft explanation or script snippet synthesized from indexed document blocks. |
vw.get | doc_id: string, chunk_id: string | Retrieves a specific document chunk to review source context or examples. |
Find details on drawing a standard rectangle with attributes using VectorScript:
// Tool Call: vw.search
{
"query": "Rect or CreateRectangle or PushAttrs"
}
// Tool Call: vw.answer
{
"query": "How do I draw a rectangle in VectorScript and set its fill color?"
}
Consulting a search result from vw.get, construct a standard VectorScript block:
Procedure CreateCustomRect;
VAR
h : HANDLE;
Begin
{ Draw rectangle }
Rect(0, 0, 150, 100);
h := LNewObj;
{ Set fill style and color to red }
SetFPat(h, 1); { Solid fill }
SetFillBack(h, 65535, 0, 0); { RGB 16-bit color }
ReDraw;
End;
Run(CreateCustomRect);
http://localhost:8000 (FastAPI UI)ws://localhost:8765API_PORT (FastAPI): Default 8000MCP_PORT (WebSocket): Default 8765Ensure the Docker containers are running and port 8765 is bound:
# Verify WebSocket port
curl http://localhost:8000/search?q=PushAttrs
If you update or add new documentation files inside the data/ folder, rebuild the FAISS database index:
docker compose run --rm app python -m app.indexer --rebuild
Connection Refused on ws://localhost:8765
docker compose up -d in the vectorworks-mcp directory and inspect container logs via docker compose logs app.API signature hallucination / Incorrect Pascal syntax
vw.search with the specific function name or topic, then review output references.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
日本語の概要は準備中です。原文の説明を表示しています。
Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.
日本語の概要は準備中です。原文の説明を表示しています。
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.
日本語の概要は準備中です。原文の説明を表示しています。
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
日本語の概要は準備中です。原文の説明を表示しています。
agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.
日本語の概要は準備中です。原文の説明を表示しています。