{"skills":[{"name":"contextqa-platform","description":"How ContextQA actually works — tenancy and workspace scoping, the test-case object graph, the variable token grammar, how runs really execute, where results and evidence live, and the integrations/PR-impact surface. Read this first if you are driving the ContextQA MCP and do not already know the platform; it is the orientation skill every other ContextQA skill assumes.","estimated_tokens":6280,"attachments":[]},{"name":"cqa-authoring-tests","description":"Author ContextQA test cases that actually RUN — typed NLP steps with correct wire format, real locators (from an existing case, a browser, or an AI bootstrap), data-driven and environment binding, then execute-and-fix. Hand-authoring is the goal (so you can edit); AI steps are a bootstrap and a fallback, never a replace-the-whole-case shortcut.","estimated_tokens":2953,"attachments":[]},{"name":"cqa-bug-fix","description":"ContextQA Bug Fix Workflow","estimated_tokens":646,"attachments":[]},{"name":"cqa-copy-test-case","description":"Faithfully copy a ContextQA test case (with its full prerequisite tree, step groups, elements, test-data profiles, variables and environment bindings) from one environment to another, using only MCP primitives. This is also the completeness acceptance test for the authoring tool surface.","estimated_tokens":3359,"attachments":[]},{"name":"cqa-export-playwright","description":"Turn ContextQA test cases into a runnable Playwright TypeScript project. The MCP tool returns a file MANIFEST; this skill writes it to disk, installs, and validates. Typed steps become real Playwright; AI steps become clearly-marked manual checkpoints; credentials are exported in plain text — all per the export contract.","estimated_tokens":908,"attachments":[]},{"name":"cqa-pr-impact","description":"Drive ContextQA's PR impact pipeline — enrol a repository, connect GitHub/GitLab, read an analysis without misreading it, review items, and run the impacted tests pre- or post-merge. Covers the four result shapes that look like success and are not, and the settings PUT that silently blanks an org's configuration.","estimated_tokens":2310,"attachments":[]},{"name":"n8n-testing","description":"Generate and push ContextQA test cases from an n8n workflow (JSON, URL, or workflow ID)","estimated_tokens":9114,"attachments":[]}],"usage":{"mcp_tools":["list_contextqa_skills","get_contextqa_skill"],"http":"GET /skills/<name>  → the skill body as Markdown","resource_uri":"skill://<name>/SKILL.md","install":"GET /skills/<name>/SKILL.md  → the whole file, for a skills directory"}}