author-response-templates

name: author-response-templates user-invocable: false description: Author and debug Handlebars response templates for WireMock stubs. Use when the user needs help writing or fixing response templates with formatJson, arrayJoin, state helpers, pagination, or brace collision issues. argument-hint: "" allowed-tools: - Read(../references/*) - mcp__wiremock__who_am_i - mcp__wiremock__search_my_mock_apis - mcp__wiremock__search_stub_mappings - mcp__wiremock__update_stub_mapping - mcp__wiremock__search_request_journal - mcp__wiremock__reset_request_journal - mcp__wiremock__make_http_request - mcp__wiremock__list_data_sources - mcp__wiremock__get_data_source - mcp__wiremock__get_data_source_data - mcp__wiremock__look_up_documentation

Prerequisites

This skill requires the WireMock Cloud MCP server to be configured and running. If it is unavailable, stop and inform the user before proceeding.

Reference Documentation

Read these references before authoring templates:

• Response Template Authoring - guidelines for Handlebars response templates, formatting, brace collision avoidance, and pagination metadata
• Stateful Stubbing - state helpers ({{state}}, {{listState}}, {{jsonMerge}}) and SET value templates
• Data-Driven Stubbing - data source iteration with data.items, {{arrayJoin}}, and SQL WHERE clauses

Instructions

The target mock API is: $ARGUMENTS

If $ARGUMENTS is empty, ask the user which mock API to work with.

1. Identify the target mock API using search_my_mock_apis.
2. Read the Response Template Authoring reference.
3. Understand the user's goal — are they writing a new template, debugging an existing one, or adding features like pagination?
4. If debugging, fetch the relevant stubs with search_stub_mappings and test them with make_http_request to reproduce the issue.
5. Author or fix the template following the guidelines:
   • Use {{#formatJson}} to wrap JSON output
   • Use {{~#arrayJoin}} with tilde whitespace trimming for arrays
   • Pretty-print JSON in templates to avoid triple-brace collisions
   • Avoid {{replace}} for generating structural JSON characters
   • For pagination, use LIMIT/OFFSET in data queries and compute metadata with {{val}} and {{math}}
6. Update the stub using update_stub_mapping.
7. Test the updated stub with make_http_request and check the request journal for errors.
8. Report the results to the user.