Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Get Started Free →

SOAP to REST Converter Skill · a5c-ai | DecimalAI

a5c-ai/soap-to-rest-converter

SkillScore40Maintained

Convert SOAP web services to REST APIs with WSDL parsing and resource modeling

codingby a5c-ai

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Coding pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/a5c-ai-soap-to-rest-converter/SKILL.md

decimalai skills pull a5c-ai-soap-to-rest-converter --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/a5c-ai-soap-to-rest-converter/SKILL.md https://app.decimal.ai/s/a5c-ai-soap-to-rest-converter/SKILL.md

Raw file: /s/a5c-ai-soap-to-rest-converter/SKILL.md ↗ · machine-readable summary at /s/a5c-ai-soap-to-rest-converter.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

25 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 55d ago

Yes — +32% lift+2% tokens0% turns40% of whole cases pass with skill (10/25)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-01	✗→✓	▲ Improved	15%	0%
case-02	✗→✓	▲ Improved	-5%	0%
case-03	✗→✓	▲ Improved	-40%	0%
case-07	✗→✓	▲ Improved	6%	0%
case-19	✗→✓	▲ Improved	-25%	0%

Showing 5 of 25 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 7/31/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

a5c-ai / babysitter

library/specializations/code-migration-modernization/skills/soap-to-rest-converter/SKILL.md

View on GitHub ↗

License MITImported 7/31/2026Version v1

Skill contents

SKILL.md

SOAP to REST Converter Skill

Converts SOAP web services to REST APIs, handling WSDL parsing, operation mapping, and RESTful resource modeling.

Purpose

Enable SOAP modernization for:

WSDL parsing
Operation-to-endpoint mapping
Type conversion
Authentication migration
REST resource modeling

Capabilities

1. WSDL Parsing

Parse WSDL documents
Extract operations
Map data types
Identify bindings

2. Operation-to-Endpoint Mapping

Map operations to HTTP methods
Design resource URIs
Handle parameters
Transform responses

3. Type Conversion

Convert XML types to JSON
Map complex types
Handle enumerations
Transform arrays

4. Authentication Migration

Convert WS-Security
Implement OAuth2
Migrate certificates
Handle API keys

5. SOAP Envelope Removal

Strip envelope structure
Extract body content
Transform headers
Handle faults

6. REST Resource Modeling

Design resource hierarchy
Implement HATEOAS
Define link relations
Model collections

Tool Integrations

| Tool | Purpose | Integration Method | |------|---------|-------------------| | SOAP UI | WSDL analysis | GUI | | wsdl2rest | Conversion | CLI | | Custom transformers | Type mapping | Library |

Output Schema

json
{
  "conversionId": "string",
  "timestamp": "ISO8601",
  "source": {
    "wsdl": "string",
    "operations": "number"
  },
  "target": {
    "openapi": "string",
    "endpoints": "number"
  },
  "mappings": [
    {
      "soapOperation": "string",
      "restEndpoint": "string",
      "method": "string",
      "notes": "string"
    }
  ],
  "typeConversions": [],
  "manualReview": []
}

Integration with Migration Processes

api-modernization: SOAP to REST conversion

Related Skills

openapi-generator: REST spec generation
api-inventory-scanner: Endpoint discovery

Related Agents

api-modernization-architect: API design

Illustrative Want to see what a5c-ai/soap-to-rest-converter would put in front of your model? Preview the rendered body and check its trigger phrases — no LLM call, no signup.

Latest benchmark · publisher runVerified

8/1/2026, 01:52 UTC · 25 cases

Lift

+32%

40% vs 8%

Agent turns

0%

1.0 vs 1.0

Tokens

+2%

2,089.44 vs 2,044.48

fail → pass · 8pass → pass · 2fail → fail · 15

Per-case results (25)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-01 I need to migrate our legacy SOAP service defined at `http://internal/services/CustomerService?wsdl` into a modern REST architecture. Please analyze the WSDL and generate a JSON report detailing the conversion process. The output should include a unique tracking ID, execution timestamp, source WSDL details (WSDL location and operation count), target OpenAPI info (spec details and endpoint count), an array mapping each SOAP operation to its REST endpoint path, HTTP method, and notes, along with lists for data type conversions and items requiring manual review.	fail→pass	9,472	10,935	+15%	1	1	0%	2,353	2,712	+15%	0	0	—
case-02 We are upgrading our enterprise Inventory Management SOAP web service (`InventoryService.wsdl`) to RESTful web services. Please process the service definition and produce a structured JSON summary. The response needs to contain a conversion ID, timestamp, source WSDL metrics, target OpenAPI summary, a list of operation-to-endpoint mappings detailing the SOAP operation, REST URI, HTTP verb, and notes, as well as type conversion definitions and flagged manual review points.	fail→pass	16,054	12,470	-22%	1	1	0%	2,783	2,654	-5%	0	0	—
case-03 Could you convert our SOAP payment gateway WSDL (`https://api.legacy-pay.com/v2/PaymentProcessor?wsdl`) to a RESTful API specification? Output the results as a JSON object containing the conversion identifier, creation timestamp, source details (WSDL URL and total operations), target information (OpenAPI definition and endpoint count), a breakdown of mapped endpoints with their HTTP methods and notes, and arrays for data type transformations and manual review callouts.	fail→pass	25,379	13,376	-47%	1	1	0%	5,499	3,300	-40%	0	0	—
case-04 We are replacing our gRPC protobuf definitions (`order_service.proto`) with a GraphQL schema using Apollo Server. Please parse the `.proto` file and generate a GraphQL schema definition complete with queries and mutations.	fail→fail	7,081	14,218	+101%	1	1	0%	1,675	3,263	+95%	0	0	—
case-05 We need to host a new legacy SOAP 1.2 web service in Java using Apache CXF, including WS-Security UsernameToken signing and SAML assertion validation. Please provide the Java CXF code to create and expose this SOAP endpoint.	fail→fail	20,352	16,986	-17%	1	1	0%	4,204	4,422	+5%	0	0	—
case-06 Our REST API gateway running on NGINX needs rate limiting configured using `limit_req_zone` for incoming HTTP GET requests to prevent DDoS attacks. Please write the NGINX configuration snippet for this.	fail→fail	9,702	12,116	+25%	1	1	0%	1,659	3,017	+82%	0	0	—
case-07 We need a CLI tool recommendation for automated SOAP WSDL to REST API conversion in our CI pipeline. We are tempted to build a custom Python scraper or use SoapUI CLI. What standard CLI tool is recommended for automated conversion?	fail→pass	14,791	10,642	-28%	1	1	0%	2,523	2,677	+6%	0	0	—
case-08 When performing preliminary visual analysis and manual inspection of legacy WSDL structures before automated migration, which standard GUI tool is integrated into this workflow?	fail→fail	6,424	1,531	-76%	1	1	0%	992	722	-27%	0	0	—
case-09 When converting WSDL `xs:sequence` arrays and complex types into REST schemas, what target data serialization format and key mapping rules should be used?	fail→fail	13,929	11,607	-17%	1	1	0%	2,543	2,800	+10%	0	0	—
case-10 We are modernizing a SOAP service secured with WS-Security UsernameToken and digital certificates. What modern authorization standard should replace WS-Security for the new REST API?	fail→fail	10,811	10,332	-4%	1	1	0%	2,063	2,235	+8%	0	0	—
case-11 During SOAP envelope removal, how should SOAP Fault elements (`soap:Fault` with `faultcode` and `faultstring`) be handled when converting to REST HTTP responses?	fail→fail	15,303	17,108	+12%	1	1	0%	2,717	3,208	+18%	0	0	—
case-12 When modeling hypermedia REST resources from RPC-style SOAP operations like `GetCustomerDetails` and `GetCustomerOrders`, what structural hypermedia constraint should be applied to define navigational link relations?	fail→fail	11,782	10,466	-11%	1	1	0%	1,963	2,086	+6%	0	0	—
case-13 Map the SOAP operation `GetUserById(In: userId)` to a RESTful endpoint path and HTTP verb. Provide the output using the standard conversion schema JSON with `conversionId`, `timestamp`, `source`, `target`, `mappings`, `typeConversions`, and `manualReview`.	fail→fail	6,948	5,088	-27%	1	1	0%	1,538	1,529	-1%	0	0	—
case-14 Map the SOAP operation `CreateNewOrder(In: OrderRequest)` to a RESTful endpoint path and HTTP method. Format as the standard conversion schema JSON.	pass→pass	5,612	5,589	-0%	1	1	0%	1,161	1,592	+37%	0	0	—
case-15 Map the SOAP operation `UpdateAccountDetails(In: AccountData)` to a RESTful HTTP method and resource URI structure. Format output in the standard conversion JSON schema.	pass→pass	9,439	7,113	-25%	1	1	0%	2,071	2,041	-1%	0	0	—
case-16 Map the SOAP operation `RemoveProductFromCatalog(In: productId)` to a REST HTTP verb and endpoint path. Output using the standard conversion schema JSON.	fail→fail	4,730	3,873	-18%	1	1	0%	987	1,231	+25%	0	0	—
case-17 Legacy SOAP requests send routing tokens in `<soap:Header><RoutingToken>abc-123</RoutingToken></soap:Header>`. How should headers be transformed during SOAP envelope stripping for REST APIs?	fail→fail	12,373	12,563	+2%	1	1	0%	2,275	2,932	+29%	0	0	—
case-18 After mapping SOAP operations to REST endpoints, which skill or tool should be invoked to generate the formal REST OpenAPI specification document?	fail→fail	10,296	2,720	-74%	1	1	0%	1,690	835	-51%	0	0	—
case-19 Before starting WSDL parsing, which discovery skill can scan existing environments to locate and inventory all exposed endpoints?	fail→pass	6,285	1,620	-74%	1	1	0%	1,005	755	-25%	0	0	—
case-20 Which specialized agent role handles overall REST API design and architecture decision-making during the modernization process?	fail→pass	6,351	1,717	-73%	1	1	0%	1,037	729	-30%	0	0	—
case-21 When a WSDL schema defines an `xs:complexType` with `maxOccurs="unbounded"`, how should this XML type be transformed into REST JSON?	fail→fail	12,940	11,941	-8%	1	1	0%	2,322	2,854	+23%	0	0	—
case-22 A WSDL defines an `xs:restriction` with multiple `xs:enumeration` values. What target REST JSON schema structure represents these enumerations?	fail→fail	7,579	6,159	-19%	1	1	0%	1,520	1,697	+12%	0	0	—
case-23 When converting a complex SOAP operation with ambiguous RPC parameters that cannot be auto-mapped, which specific field in the conversion JSON schema should capture this item?	fail→pass	10,243	2,859	-72%	1	1	0%	1,673	1,041	-38%	0	0	—
case-24 In the conversion JSON schema, under which exact field name should XML schema data type to JSON schema data type mappings be stored?	fail→pass	11,906	2,131	-82%	1	1	0%	1,997	920	-54%	0	0	—
case-25 When modernizing SOAP payload processing, what action must be performed on the `<soap:Envelope>` and `<soap:Body>` XML wrapper structure?	fail→fail	5,354	2,902	-46%	1	1	0%	862	984	+14%	0	0	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 25 cases were attempted. The headline lift of +32 percentage points is the difference between those two pass rates over the 25 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 8%
Pass rate with the skill: 40%
Cases attempted: 25
Cases counted toward lift: 25
Cases that regressed: 1
Skill version measured: v1
Run completed: 8/1/2026, 01:52 UTC

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-01

Prompt

I need to migrate our legacy SOAP service defined at `http://internal/services/CustomerService?wsdl` into a modern REST architecture. Please analyze the WSDL and generate a JSON report detailing the conversion process. The output should include a unique tracking ID, execution timestamp, source WSDL details (WSDL location and operation count), target OpenAPI info (spec details and endpoint count), an array mapping each SOAP operation to its REST endpoint path, HTTP method, and notes, along with lists for data type conversions and items requiring manual review.

Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.

Show both answers

SkillScore blends 4 signals1 of 4 complete

BenchmarkPass rate WITH skill on a verified run40

Live evalNeeds ≥10 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Efficiency · separate axis (at equal correctness)+0% turns+12% tokens

Shown for transparency; not credited unless a verified run shows no correctness regression.

Backed by 1 of 4 signals — each added signal makes the score more robust.

Verified on gemini-3.6-flash · re-tested 55 days ago

Other measured skills in the registry, with their headline benchmark lift.