Why should you care?

Admins enable hospital or CRM capabilities by skill name without knowing individual plugin classes.

See it live — copy this example

Paste into an ASP.NET Core 8+ / AgentNest project, then run with dotnet run (set your API keys in user-secrets).

// AgentNest.Agents/Skills/SkillRegistry.cs
public sealed class SkillRegistry
{
    public IReadOnlyList<string> CrmSkill => ["crm", "email", "calendar"];
    public IReadOnlyList<string> HospitalSkill => ["allergy", "labs", "triage"];
    public IEnumerable<KernelPlugin> ResolvePlugins(Kernel kernel, IEnumerable<string> skill) =>
        kernel.Plugins.Where(p => skill.Contains(p.Name));
}

What happened?

• SkillRegistry names plugin groups.
• ResolvePlugins filters kernel plugins when building tenant-specific agents.

Practice next

1. Document skill-to-plugin mapping in AgentNest wiki.
2. Expose GET /api/ai/skills for admin UI checkboxes.
3. Enable skills per tenant via TenantAiContext.
4. Add ErpSkill with gl, ap, ar plugins.
5. Persist enabled skills in SQL per tenant row.

Remember

AgentNest skills are logical plugin groupings. Map skills to kernel plugins for tenant enablement. Expose skill lists to admins for self-service config.

Tenant feature toggles

A CRM-only customer refuses hospital plugins in their contract.

Outcome: SkillRegistry loads CrmSkill only — kernel surface matches SKU.