mdkulkarni2005/osmos-marketing-mcp

mdkulkarni2005/osmos-marketing-mcp

Skill Claude CodeCodex

Generic, service-agnostic API test scenario design skill. Consumes an API contract from a Documentation MCP (or any authoritative contract source) and produces traceable, prioritized, coverage-reported test scenarios. Works for any REST/HTTP endpoint of any service/version — no hardcoded API knowledge.

mdkulkarni2005/osmos-marketing-mcp

Skill Claude CodeCodex

Wires this project's build/typecheck/fixture-test/dry-run/qa-review pipeline into CI (GitHub Actions, since this repo is hosted on GitHub) — safely, respecting the two-machine constraint from docs/local-execution.md. CI never runs real requests against a live API and never touches credentials.

mdkulkarni2005/osmos-marketing-mcp

Skill Claude CodeCodex

Formats scenarios produced by api-test-design into the company's real QA testcase conventions (spreadsheet columns, TCID scheme, Postman naming/scripting), learned from actual SDA V2 reference artifacts and kept service-agnostic — never copies SDA's API fields/values into another service's testcase sheet.

mdkulkarni2005/osmos-marketing-mcp

Skill Claude CodeCodex

Converts an approved company-format testcase workbook (from api-test-design + company-testcase-format) into one Postman collection and one Postman environment, using conventions learned from real company artifacts and this project's src/postman builders. Does not execute anything and does not decide what to test.

mdkulkarni2005/osmos-marketing-mcp

Skill Claude CodeCodex

Reviews a generated test scenario suite (from api-test-design, formatted by company-testcase-format) for completeness, traceability, and quality before human approval. Produces PASS/FAIL/NEEDSREVIEW with reasons.

mdkulkarni2005/osmos-marketing-mcp

Skill Claude CodeCodex

Generates concrete, deterministic, contract-grounded testdata values for scenarios produced by api-test-design — unique IDs, dates, realistic-looking strings for documented formats — without inventing business facts. Also defines seed-data and cleanup conventions for scenarios that need pre-existing resources.