native

Scaffold Native AOT plugins with startup composition and ToolAttribute design.

46|7|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/sunyonghuan/Netor.Madorin --skill native-sunyonghuan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: native
Source: https://github.com/sunyonghuan/Netor.Madorin/tree/main/Plugins/Samples/ReminderPlugin/.github/skills/plugin-development/subskills/native
Command: npx skills add https://github.com/sunyonghuan/Netor.Madorin --skill native-sunyonghuan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you build Native AOT plugins that stay compatible with Cortana’s plugin architecture, avoid common startup and serialization mistakes, and keep implementation aligned with the platform’s runtime constraints.

Core Features & Use Cases

  • Native plugin scaffolding: Create a clean plugin layout for Native AOT delivery, including startup, tools, contracts, and infrastructure.
  • AOT-safe implementation rules: Keep tool parameters, dependency registration, and custom return models compatible with Native AOT and JsonContext requirements.
  • Operational use cases: Use it for building local tools, background services, and high-performance plugins that can be published and installed reliably.

Quick Start

Ask the assistant to scaffold a Native plugin using this skill’s layout, rules, and publish flow.

Frequently Asked Questions about native

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

FAQPage Schema
How do I build a Native AOT plugin for Cortana?

Building a Native AOT plugin for Cortana requires scaffolding a clean layout with startup, tools, and infrastructure, then applying AOT-safe rules for tool parameters and custom return models.

What is a PluginJsonContext and when do I need it for Native AOT plugins?

PluginJsonContext is a serialization configuration required for Native AOT plugins to handle custom return models, registering custom data models to ensure compatibility with AOT compilation constraints.

Does Cortana plugin development require a specific startup composition?

Cortana plugin development requires a disciplined startup composition using a hosted service pattern, configuring a single PluginAttribute entry and managing dependencies to maintain platform runtime compatibility.

How do I make tool parameters AOT-safe in my Cortana plugin?

Making tool parameters AOT-safe in a Cortana plugin requires using types compatible with Native AOT serialization and registering custom models through PluginJsonContext to prevent runtime trimming issues.

Can I use background services in a Native AOT Cortana plugin?

You can use background services in a Native AOT Cortana plugin by scaffolding hosted service patterns compatible with AOT, enabling high-performance background tasks within the plugin architecture.

What are the limitations of using Native AOT for plugin development?

Native AOT plugin development limits you to AOT-safe dependencies and requires explicit JsonContext registration for custom models, as reflection-based serialization is unsupported and strict hosting patterns must be followed.