Work on WCF services, clients, bindings, contracts, and migration decisions for SOAP and multi-transport service-oriented systems on .NET Framework or compatible stacks. USE FOR: working on WCF services, bindings, or clients; deciding whether a service should stay WCF or move to modern HTTP APIs; reviewing transport, security, or interoperability. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files,
SkillScore91Maintained
Automatic
◆Coding pack
Last verified 8/19/2026
What it changes
Passed 20 of 22 test cases with the skill, and 17 of 22 without it.
Without skill77%
With skill91%
Checks it passed that the model alone missed
States that successful local service startup is insufficient to confirm client interoperability.
Requires validating interoperability against actual client consumers in the target deployment ecosystem.
Advises retaining WCF or CoreWCF where SOAP, WS-* protocols, or multi-transport requirements are actively required.
and 1 more in the full report
3 fixed17 passed either way2 still failing0 broke
Pass-rate lift
+14 pp
Tokens
+3%
Agent turns
0%
Response time
-11%
Model gemini-3.6-flashMeasured 8/19/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
Our enterprise system communicates with external banking systems using WS-Security username tokens, message-level encryption, and NetTcp bindings. The management team proposed replacing all services with standard ASP.NET Core REST JSON endpoints in a single sprint. Provide an architectural evaluation of this plan.
What was checked, without and with the skill
Checked
Without skill
With skill
Advises retaining WCF or CoreWCF where SOAP, WS-* protocols, or multi-transport requirements are actively required.
Missed
Passed
Rejects replacing WS-* and multi-transport requirements with HTTP-only REST without addressing underlying security and protocol dependencies.
Passed
Passed
case-02 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md33 lines3 files
Windows Communication Foundation
Trigger On
working on WCF services, bindings, or clients
deciding whether a service should stay WCF or move to modern HTTP APIs
reviewing transport, security, or interoperability settings
Workflow
Use WCF where SOAP, WS-* features, or multi-transport service requirements are real; do not rewrite those needs into HTTP-only guidance by accident.
Keep contracts, bindings, behaviors, and hosting configuration explicit because WCF complexity compounds through configuration indirection.
For new REST-style services, prefer modern ASP.NET Core APIs instead of extending WCF into a shape it is no longer best suited for.
Plan migrations per endpoint and capability: transport, security model, transaction requirements, metadata, and client compatibility.
Validate interoperability and deployment assumptions with the actual client ecosystem, not only local service startup.
When WCF coexists with ASP.NET, be explicit about which runtime behaviors are shared and which are not.
Deliver
stable WCF service or client configuration
realistic migration guidance to newer stacks where appropriate
clear contract and binding ownership
Validate
WCF is used for a reason the modern stack does not replace directly
binding and security behavior are explicit
interop is verified with real consumers
References
migration.md - WCF to gRPC/REST/CoreWCF migration paths, decision framework, and endpoint-by-endpoint migration strategy
patterns.md - WCF maintenance patterns for configuration, contracts, hosting, security, diagnostics, and client proxy management