Skip to content

Why SK is Still Relevant

Key Points

  • Semantic Kernel still useful in 2026 despite Agent Framework superseding it for orchestration.
  • Strengths: prompt template engine (Liquid, Handlebars), plugin ecosystem, Process Framework for stateful agents (preview).
  • For existing SK apps: don't rewrite for the sake of it.
  • For new prompt-template-heavy apps: SK templates + Microsoft.Extensions.AI execution can coexist.

What SK still does well

Prompt templates

{{#each items}}
- {{this.title}}: ${{this.price}}
{{/each}}

{{#if isVip}}
You're a VIP — here are exclusive offers:
{{/if}}

Compile-time-checked templates with helpers. Cleaner than string interpolation for complex prompts.

var template = await _factory.CreatePrompt(...);
var rendered = await template.RenderAsync(arguments, kernel);

Plugin ecosystem

Many community plugins for SK (web search, math, time, etc.). Some still useful for prototyping.

Process Framework

SK Process (preview): structured workflows with steps. Similar to Durable Functions but prompt-aware.

For deterministic workflows with prompts: useful.

Hybrid: SK templates + Agent Framework

// SK for templating
var template = _factory.Create("greeting.yaml");
var rendered = await template.RenderAsync(args);

// Agent Framework for execution
var resp = await _agent.InvokeAsync(rendered);

Best of both. SK templates aren't going away; Agent Framework executes.

When stick with SK

  • Existing production app; team familiar.
  • Heavy prompt template usage.
  • Process Framework adoption.
  • Stable; not migrating soon.

When migrate to Agent Framework

  • New project — Agent Framework is the default.
  • Need OTel GenAI conventions.
  • Multi-vendor aspirations.
  • Replacing SK Planners (deprecated anyway).

Don't migrate without reason

Working SK code: keep working. Migrate when adding NEW features or hitting limitations.

SK status (2026)

  • Active development.
  • Process Framework continues.
  • Some areas (planners) deprecated.
  • Microsoft positions SK as complementary, not competing, with Agent Framework.

Senior considerations

  • Don't religiously migrate: pragmatism beats purity.
  • Hybrid is OK: pick the right tool per concern.
  • Plan around deprecations: planners gone; alternatives needed.
  • Eval after migration: ensure quality preserved.

Cross-references