skills.rest
sunyonghuan
sunyonghuanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

process

Build and validate C# Process plugins for Netor.Madorin with DEBUG self-tests.

46|7|Updated Apr 9, 2026
Search Tags:#csharp#plugin development#debugger#self-test#jit#aot#process plugin
One-click install
npx skills add https://github.com/sunyonghuan/Netor.Madorin --skill process-sunyonghuan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: process
Source: https://github.com/sunyonghuan/Netor.Madorin/tree/main/skills/plugin-development/subskills/process
Command: npx skills add https://github.com/sunyonghuan/Netor.Madorin --skill process-sunyonghuan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create and verify C# Process plugins that run as isolated executable tools and communicate cleanly with the Madorin host, so you can ship richer plugins without hand-writing protocol plumbing.

Core Features & Use Cases

  • Process-based plugin architecture: Build executable plugins with stdin and stdout JSON messaging for isolation and compatibility.
  • Strongly typed development flow: Use the generated debugger, plugin metadata, and framework scaffolding instead of manual protocol code.
  • Testing and release readiness: Validate every tool in DEBUG self-test mode, then publish JIT self-contained or AOT builds.
  • Use Case: Create a reliable utility plugin that exposes several tools, confirms parameter binding locally, and then ships as an installable executable.

Quick Start

Ask the assistant to generate a C# Process plugin with a DEBUG-only self-test entry point, typed tools, and a complete build, test, and publish workflow.

Frequently Asked Questions about process

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

FAQPage Schema
How do I build a C# process plugin for isolated tool execution?▼

Validate C# process plugins by running DEBUG-only self-tests to confirm parameter binding and tool execution locally. You must verify every tool in DEBUG mode before publishing JIT self-contained or AOT builds.

What is the difference between JIT and AOT builds for C# process plugins?▼

JIT self-contained builds and AOT builds are the supported publishing options for C# process plugins. AOT offers native ahead-of-time compilation, while JIT provides self-contained deployment for your executable plugin tools.

Can I use this approach to create utility plugins with multiple tools for Netor.Madorin?▼

Yes, you can create a utility plugin that exposes several tools. The process plugin architecture supports multiple tools within a single executable, confirming parameter binding locally before shipping as an installable build for the Madorin host.

What are the limitations of building process-based executable plugins?▼

Process-based executable plugins require strict stdin and stdout JSON messaging isolation. You must maintain DEBUG-only self-tests and ensure per-tool verification passes, as skipping protocol validation before publish leads to host communication failures.

Related Skills

Explore More Software Engineering Skills→
microsoftmicrosoft
1.2k

winapp-frameworks

Provide framework-specific Windows development guidance for Electron, .NET, C++, Rust, Flutter, and Tauri.

Official
Intermediate
NitzanSelwynNitzanSelwyn

convex-component-authoring

Build self-contained Convex components with isolated schemas and modular exports.

Community
Intermediate
cacr92cacr92
4

ipc-communication

Implement JSON-based IPC between Rust orchestrators and platform agents via stdin/stdout.

Community
Advanced
kangnam7654kangnam7654
1

paperclip-create-plugin

Scaffold Paperclip plugins and update manifest, worker, UI, tests, and package.json.

Community
Advanced