veloxdev-drive-workflow-with-ai

Expose a VeloxDev workflow graph as LLM tools with policy gates, skills, and MCP servers.

37|12|Updated Jun 5, 2025
One-click install
npx skills add https://github.com/Axvser/VeloxDev --skill veloxdev-drive-workflow-with-ai-axvser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: veloxdev-drive-workflow-with-ai
Source: https://github.com/Axvser/VeloxDev/tree/main/skills/veloxdev-drive-workflow-with-ai
Command: npx skills add https://github.com/Axvser/VeloxDev --skill veloxdev-drive-workflow-with-ai-axvser

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It lets a .NET developer hand control of a VeloxDev node-graph workflow editor to an LLM agent, so the model can inspect, create, connect, and execute nodes through the same undoable commands the GUI uses, without writing a custom tool layer. ## Core Features & Use Cases - Workflow tool surface: Wire a WorkflowAgentScope onto a tree to give an IChatClient 62 tools for querying topology, mutating the graph, running compiled chains, and reverse-computing node results. - Policy gates and budgets: Gate node execution, generic commands, and interaction handlers behind host-configured flags, plus read/write tool-call budgets and confirmation handlers. - Skills and MCP integration: Load switchable Agent-Skills folders from disk and connect external MCP servers (stdio or HTTP), each usable standalone without the workflow layer. - Use Case: A WPF app developer adds an AI assistant panel that lets users ask the model to build a data-processing pipeline on the canvas, with execution disabled by policy until the host explicitly enables it. ## Quick Start Set up a VeloxDev agent scope on my workflow tree with synchronization context, auto-discovery, and skills, then connect it to my chat client so the AI can inspect and edit the graph.

Frequently Asked Questions about veloxdev-drive-workflow-with-ai

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I let an LLM control a VeloxDev workflow graph?

Call tree.AsAgentScope() to build a WorkflowAgentScope, configure it with WithSynchronizationContext and WithAutoDiscovery, then pass scope.CreateContextProviders() to chatClient.AsAIAgent. The provider contributes the full tool set and prompt each turn.

How do I restrict what the AI agent can do to the workflow?

Node execution tools are off by default and require WithAllowNodeExecution(true). Generic commands need WithAllowedGenericCommands listing exact names, and WithMaxToolCalls, WithMaxReadToolCalls, and WithMaxWriteToolCalls cap tool usage per session.

Can I use the MCP or skills subsystem without a workflow tree?

Yes. McpScope and SkillScope each export their own context provider, so a host that only wants MCP servers or switchable skills attaches that single provider to the agent without any workflow layer.

Why do agent tool calls fail or touch the graph from the wrong thread?

Workflow components are UI-bound, so WithSynchronizationContext must be called on the UI thread. Without it, tool calls execute on a thread pool thread, and the wrapper marshals everything including post-await continuations onto the provided context.

Why do tools appear twice in the agent prompt?

The framework unions ChatOptions.Tools with the context provider's contribution without deduplicating by name. Never pass the scope's tools through ChatOptions.Tools or re-register subsystem management tools with WithTools.

What format must a disk-based skill folder follow?

A disk skill is a folder named in lowercase kebab-case containing a SKILL.md with YAML frontmatter carrying name and description, matching the Agent Skills convention. An optional references folder is read only when the model calls read_skill_resource.