aks-builds
UserA curated, production-focused collection of 50 modern Quality Engineering skills for QA Engineers, SDETs, Automation Architects, and Test Automation Leads — covering the complete testing ecosystem from UI automation to performance engineering, DevOps-driven quality, and enterprise-scale test strategy.
Categories
Indexed Skills (86)
accessibility-testing
When the user wants to design, implement, or operate accessibility (a11y) testing — automated scans, manual audits, screen-reader testing, WCAG conformance, Section 508 / EAA compliance. Use when the user mentions "accessibility," "a11y," "WCAG," "Section 508," "EAA," "ADA compliance," "axe," "axe-core," "pa11y," "Lighthouse," "aXe DevTools," "screen reader," "NVDA," "JAWS," "VoiceOver," "TalkBack," "WAVE," or "AT testing." For visual diff see visual-regression. For overall test strategy see test-strategy.
ai-augmented-testing
When the user wants to evaluate, adopt, or operate AI-augmented testing tools and approaches — autonomous test generation, self-healing locators, AI-assisted authoring, vision-based testing, agentic test runners. Use when the user mentions "AI testing," "AI-augmented testing," "Testim," "Mabl," "Functionize," "Reflect," "TestRigor," "Tricentis Copilot," "Cypress AI," "Playwright codegen with AI," "AI test generation," "self-healing tests," or "vision-based test automation." For LLM-product evals see llm-eval-testing. For overall strategy see test-strategy.
appium
When the user wants to design, implement, debug, or scale Appium tests for iOS and Android mobile automation. Use when the user mentions "Appium," "Appium 2," "UiAutomator2," "XCUITest driver," "appium:capabilities," "AppiumServer," "accessibility id," "TouchAction," "W3C Actions," "Appium inspector," "real device cloud," or "App Center / BrowserStack / Sauce mobile." For Android-native frameworks see espresso. For iOS-native see xcuitest. For React Native specifically see detox. For YAML-driven mobile flows see maestro. For desktop web automation see selenium / playwright / webdriverio.
artillery
When the user wants to design, implement, debug, or operate Artillery load tests. Use when the user mentions "Artillery," "artillery.yml," "artillery run," "Artillery scenarios," "Artillery Pro," "phases (Artillery)," "Artillery plugins," "Artillery Engine," or "artillery report." For JS-tested perf with thresholds see k6. For JVM perf see gatling. For Python see locust. For JMeter see jmeter.
bdd-anti-patterns
When the user wants to audit, refactor, or rescue a Cucumber / Gherkin / SpecFlow / Reqnroll / behave BDD suite from common failure modes. Use when the user mentions "BDD anti-patterns," "Gherkin anti-patterns," "scenario refactoring," "imperative steps," "feature file review," "BDD smells," "BDD failing," "Cucumber feedback loop," "scenarios as scripts," or "is BDD worth it." For Cucumber/Gherkin basics see cucumber-gherkin. For .NET BDD see specflow-reqnroll. For Python BDD see behave.
behave
When the user wants to design, implement, debug, or operate BDD tests on Python using behave. Use when the user mentions "behave," "behave.ini," "@given/@when/@then," "context.x," "environment.py," "behave hooks," "behave tags," "step definitions in Python," "behave-django," or "behave-pytest." For language-agnostic Gherkin patterns see cucumber-gherkin. For .NET BDD see specflow-reqnroll. For BDD failure modes see bdd-anti-patterns. For non-BDD Python testing see pytest.
chaos-engineering
When the user wants to design, run, or operate chaos experiments to validate system resilience. Use when the user mentions "chaos engineering," "chaos testing," "fault injection," "Chaos Monkey," "Chaos Mesh," "Gremlin," "Litmus," "Steadybit," "Toxiproxy," "AWS FIS," "kill the database," "latency injection," "GameDay," "blast radius," or "principles of chaos." For security testing see security-testing. For fault simulation in unit tests see wiremock and mutation-testing. For perf testing see k6 / gatling.
ci-test-orchestration
When the user wants to design, audit, or optimize how tests run in CI — sharding, matrix builds, parallelism, retry policy, test selection, artifact handling, and gate strategy. Use when the user mentions "CI test orchestration," "test sharding," "matrix builds," "parallel tests in CI," "GitHub Actions matrix," "GitLab CI parallel," "Buildkite parallelism," "test selection," "test impact analysis," "CI retries," "test artifacts," or "speeding up CI." For environment specifics see test-environment-management. For cloud-grid mobile/browser see cloud-test-grids. For Grid see selenium-grid.
cloud-test-grids
When the user wants to design, integrate, or operate against a cloud-hosted browser / device test grid — BrowserStack, Sauce Labs, LambdaTest, AWS Device Farm, Firebase Test Lab, Perfecto, Kobiton. Use when the user mentions "BrowserStack," "Sauce Labs," "Sauce," "LambdaTest," "AWS Device Farm," "Firebase Test Lab," "cloud grid," "cloud-hosted devices," "real-device cloud," or "bstack:options / sauce:options / lt:options." For self-hosted grids see selenium-grid. For specific test tools see playwright / cypress / selenium / appium.
code-coverage
When the user wants to measure, interpret, or improve code coverage — line, branch, function, statement, condition, MC/DC coverage. Use when the user mentions "code coverage," "test coverage," "Istanbul," "c8," "JaCoCo," "coverage.py," "Coverlet," "lcov," "Codecov," "Coveralls," "branch coverage," "MC/DC," or "coverage threshold." For test-quality signal beyond coverage see mutation-testing. For strategy framing see test-strategy.
cucumber-gherkin
When the user wants to design, implement, debug, or evolve BDD scenarios using Cucumber and the Gherkin syntax across any language (Java, JS, Ruby, JVM, etc.). Use when the user mentions "Cucumber," "Gherkin," "Given/When/Then," ".feature file," "step definitions," "scenario outline," "data tables," "Cucumber hooks," "World," "Cucumber-JVM," "Cucumber.js," "Cucumber-Ruby," or "tag expressions." For .NET BDD see specflow-reqnroll. For Python BDD see behave. For Karate's BDD-flavored DSL see karate. For the catalog of what NOT to do in Gherkin see bdd-anti-patterns.
cypress
When the user wants to design, implement, debug, stabilize, or scale Cypress tests. Use when the user mentions "Cypress," "cypress.config.js," "cy.intercept," "cy.session," "cy.visit," "component testing in Cypress," "Cypress Cloud," "cypress run," "cypress open," "cy.task," "Mocha," or "Chai." For Playwright-specific questions see playwright. For Selenium-specific questions see selenium. For CI sharding see ci-test-orchestration. For screenshot diffing see visual-regression.
detox
When the user wants to design, implement, debug, or stabilize Detox tests for React Native E2E testing. Use when the user mentions "Detox," "by.id," "by.label," "element(by.id(...))," "device.launchApp," ".detoxrc.js," "detox test," "Detox config," "RNTester," "Detox Jest," or "Wix Detox." For Android-native see espresso. For iOS-native see xcuitest. For cross-platform Appium see appium. For YAML-driven see maestro. For unit testing React Native components see jest-vitest.
espresso
When the user wants to design, implement, debug, or stabilize Espresso tests for native Android UI automation. Use when the user mentions "Espresso," "onView," "ViewMatchers," "withId," "IdlingResource," "ActivityScenario," "ActivityScenarioRule," "AndroidJUnitRunner," "androidx.test," "instrumented tests," "Espresso Intents," "Espresso Web," or "@RunWith(AndroidJUnit4)." For cross-platform mobile see appium. For iOS-native see xcuitest. For React Native see detox. For YAML-driven flows see maestro.
feature-flag-testing
When the user wants to test code controlled by feature flags — variation coverage, flag combinations, canary / progressive rollout, A/B test correctness, kill-switch behavior. Use when the user mentions "feature flags," "feature toggles," "LaunchDarkly," "Split.io," "Unleash," "ConfigCat," "Flagsmith," "Optimizely," "Statsig," "canary," "progressive delivery," "ramp," "A/B test," "kill switch," "flag combinations," or "dark launch." For production-side verification see production-testing. For overall strategy see test-strategy.
gatling
When the user wants to design, implement, debug, or operate Gatling load tests. Use when the user mentions "Gatling," "Gatling Simulation," "scenario.exec," "injectOpen," "constantUsersPerSec," "rampUsersPerSec," "atOnceUsers," "Gatling DSL," "Karate-Gatling," "Gatling Enterprise," "Frontline," or "io.gatling." For JS-based perf see k6. For JMeter see jmeter. For Python see locust. For Node see artillery.
go-test
When the user wants to design, implement, debug, or optimize Go tests using the standard testing package, testify, and related Go ecosystem libraries. Use when the user mentions "go test," "table-driven tests," "t.Run," "subtests," "testify," "require / assert," "go test -race," "go test -bench," "go test -fuzz," "TestMain," "t.Cleanup," "httptest.Server," or "go-cmp." For JS/TS see jest-vitest. For Python see pytest. For Java see junit-testng. For .NET see xunit-nunit.
graphql-testing
When the user wants to design, implement, debug, or evolve tests for GraphQL APIs — queries, mutations, subscriptions, schema, resolvers, and clients. Use when the user mentions "GraphQL testing," "Apollo Server tests," "graphql-tools mockServer," "schema diff," "introspection," "fragments," "operations," "persisted queries," "Hasura," or "graphql-codegen." For REST API testing see rest-assured / supertest / pytest-api. For contract testing see pact-contract-testing. For service virtualization see wiremock.
grpc-testing
When the user wants to design, implement, debug, or load-test gRPC services. Use when the user mentions "gRPC testing," "protobuf," ".proto," "grpcurl," "ghz," "buf," "server reflection," "grpc-go test," "grpc Java test," "grpc Python test," "interceptors," "streaming RPC," or "TLS for gRPC." For REST API testing see rest-assured / supertest / pytest-api. For load testing strategy beyond gRPC see k6 / gatling. For contract testing see pact-contract-testing.
jest-vitest
When the user wants to design, implement, debug, or optimize Jest or Vitest unit / integration tests in JavaScript or TypeScript. Use when the user mentions "Jest," "Vitest," "describe/it/test," "expect," "jest.mock," "vi.mock," "vi.fn," "snapshot," "spyOn," "fake timers," "module mocks," "jest.config," "vitest.config," "test coverage," or "@swc/jest." For Node API integration testing see supertest. For Cypress component tests see cypress. For pytest see pytest. For Java unit testing see junit-testng.
jmeter
When the user wants to design, implement, debug, or operate Apache JMeter load tests. Use when the user mentions "JMeter," "Apache JMeter," ".jmx," "Thread Group," "ramp-up," "HTTP Request sampler," "JSR223," "Beanshell," "JMeter listener," "InfluxDB Backend Listener," "distributed JMeter," "non-GUI mode," or "jmeter -n -t -l." For modern JS-based perf see k6. For JVM perf see gatling. For Python see locust. For YAML/Node see artillery.
junit-testng
When the user wants to design, implement, debug, or optimize JUnit 5 (Jupiter) or TestNG tests on the JVM. Use when the user mentions "JUnit 5," "JUnit Jupiter," "@Test," "@ParameterizedTest," "@MethodSource," "@TestFactory," "TestNG," "@DataProvider," "@BeforeEach," "@BeforeMethod," "AssertJ," "Hamcrest," "Mockito," "MockK," "ArchUnit," or "Maven surefire / Gradle test." For JS/TS see jest-vitest. For Python see pytest. For .NET see xunit-nunit. For Java API testing see rest-assured.
k6
When the user wants to design, implement, debug, or operate k6 load tests. Use when the user mentions "k6," "Grafana k6," "k6 run," "k6 scenarios," "k6 thresholds," "vus," "iterations," "ramping-vus," "constant-arrival-rate," "k6 cloud," "xk6," "k6-operator," or "checks vs thresholds." For JMeter see jmeter. For Gatling see gatling. For Locust see locust. For Artillery see artillery. For overall perf testing strategy see test-strategy.
karate
When the user wants to design, implement, debug, or scale Karate tests for API testing (and optionally UI/mocking/perf). Use when the user mentions "Karate," "Karate DSL," ".feature file in Karate," "karate.callonce," "karate-config.js," "Karate UI," "Karate mocks," "Karate gatling," or "io.karatelabs / com.intuit.karate." For pure Gherkin BDD see cucumber-gherkin. For Java fluent API testing see rest-assured. For Postman see postman-newman.
llm-eval-testing
When the user wants to design, build, or operate evaluations (evals) for LLM-powered products — chatbots, RAG systems, agents, classification, summarization, structured output. Use when the user mentions "LLM evals," "evals," "RAG evaluation," "RAGAS," "DeepEval," "LangSmith," "LangFuse," "PromptLayer," "OpenAI evals," "judge model," "rubric eval," "LLM-as-judge," "Inspect AI," "AnthropicEvals," "Vertex evals," "Braintrust," or "regression tests for prompts." For AI testing tools see ai-augmented-testing. For chaos see chaos-engineering. For production monitoring see production-testing.
locust
When the user wants to design, implement, debug, or operate Locust load tests in Python. Use when the user mentions "Locust," "HttpUser," "@task," "TaskSet," "locustfile.py," "master/worker," "Locust web UI," "FastHttpUser," "constant_pacing," "wait_time," or "locust -f -u -r --headless." For k6 see k6. For JMeter see jmeter. For Gatling see gatling. For Node-based perf see artillery.
maestro
When the user wants to design, implement, debug, or operate Maestro mobile UI flows. Use when the user mentions "Maestro," "maestro.dev," "Maestro flow," "maestro test," "Maestro Cloud," "maestro studio," "tapOn," "assertVisible," "scrollUntilVisible," ".maestro/" flows, or "yaml mobile test." For React Native gray-box see detox. For Android-native see espresso. For iOS-native see xcuitest. For Appium see appium.
mutation-testing
When the user wants to measure or improve the *quality* of their existing test suite via mutation testing. Use when the user mentions "mutation testing," "mutation score," "Stryker," "PIT," "PITest," "mutmut," "go-mutesting," "Mutmut," "mutator," "killed mutant," "surviving mutant," "mutation coverage," or "is our coverage strong." For line coverage see code-coverage. For overall strategy see test-strategy.
pact-contract-testing
When the user wants to design, implement, or operate consumer-driven contract testing with Pact. Use when the user mentions "Pact," "contract testing," "consumer-driven contracts," "Pact Broker," "Pactflow," "pact_broker," "publish pacts," "verify pacts," "Pact matcher," "can-i-deploy," or "WIP pacts." For service virtualization see wiremock. For Postman-style API tests see postman-newman. For REST Assured / supertest / pytest-api see those skills. For schema-validation-only see graphql-testing / pytest-api schemathesis.
playwright
When the user wants to design, implement, debug, stabilize, or scale Playwright tests. Use when the user mentions "Playwright," "playwright.config.ts," "page.locator," "page.getByRole," "browser context," "fixtures," "test.beforeEach," "trace viewer," "codegen," "Playwright Test," "Playwright MCP," "PWT," "WebKit testing," or "cross-browser." For Cypress-specific questions see cypress. For Selenium-specific questions see selenium. For CI sharding and parallelism see ci-test-orchestration. For screenshot diffing see visual-regression.
postman-newman
When the user wants to design, organize, or run Postman collections — locally, in CI via Newman, or shared across a team. Use when the user mentions "Postman," "Postman collection," "Newman," "newman run," "pm.test," "pre-request script," "test script," "Postman environment," "collection variables," "Postman monitor," or "Postman flows." For language-native API testing (Node, Python, Java) see supertest, pytest-api, rest-assured. For service virtualization see wiremock. For contract testing see pact-contract-testing.
puppeteer
When the user wants to design, implement, debug, or scale Puppeteer scripts for browser automation, scraping, PDF generation, or screenshot capture. Use when the user mentions "Puppeteer," "puppeteer-core," "Chromium," "page.goto," "page.evaluate," "page.screenshot," "page.pdf," "browser.launch," or "headless Chrome." For test-runner-flavored E2E, see playwright (same Microsoft team, more test-focused). For Cypress see cypress. For Selenium see selenium.
pytest-api
When the user wants to design, implement, debug, or scale Python API tests using pytest + requests/httpx. Use when the user mentions "pytest API tests," "requests for API testing," "httpx," "pytest fixtures for API," "responses (mock library)," "respx," "vcr.py," "schemathesis," or "FastAPI TestClient." For Java API testing see rest-assured. For Node API testing see supertest. For Postman collections see postman-newman. For contract testing see pact-contract-testing.
pytest
When the user wants to design, implement, debug, or optimize pytest tests in Python. Use when the user mentions "pytest," "pytest fixtures," "conftest.py," "pytest.ini," "pyproject.toml pytest section," "@pytest.fixture," "@pytest.mark.parametrize," "pytest-xdist," "pytest-asyncio," "pytest-cov," "monkeypatch," "tmp_path," "capsys," or "pytest plugins." For pytest-based API testing see pytest-api. For JS/TS unit testing see jest-vitest. For Java see junit-testng. For .NET see xunit-nunit.
qa-context
When the user wants to create or update their QA context document, or whenever any other quality skill needs to understand the organization's stack, languages, CI provider, target browsers/devices/APIs, test environments, quality bar, and compliance scope. Read this file before answering any test automation question. Trigger phrases include "QA context," "quality context," "set up the project context," "what's our stack," "configure the test environment," "ramp up on the test setup," or when any other skill needs project-specific grounding.
rest-assured
When the user wants to design, implement, debug, or scale REST Assured tests for Java/JVM API testing. Use when the user mentions "REST Assured," "RestAssured," "given().when().then()," "RequestSpecification," "ResponseSpecification," "JsonPath," "XmlPath," "Hamcrest matchers," "MockMvc with REST Assured," or "Maven dependency io.rest-assured." For Node API testing see supertest. For Python see pytest-api. For Postman collections see postman-newman. For BDD-on-top see cucumber-gherkin.
rspec
When the user wants to design, implement, debug, or optimize RSpec tests in Ruby. Use when the user mentions "RSpec," "describe/context/it," "let," "subject," "shared_examples," "shared_context," "expect(...).to eq," "rspec-rails," "FactoryBot," "VCR," "WebMock," "Capybara," ".rspec," "rspec --tag," or "rspec spec_helper.rb." For Rails system tests see also accessibility-testing and visual-regression. For JS/TS see jest-vitest. For Python see pytest. For Java see junit-testng.
security-testing
When the user wants to design, integrate, or operate security testing in their pipeline — SAST, DAST, dependency scanning, secret scanning, container scanning, IaC scanning, fuzzing, authn/authz testing, OWASP coverage. Use when the user mentions "security testing," "SAST," "DAST," "OWASP Top 10," "OWASP ZAP," "Burp Suite," "semgrep," "Snyk," "dependency scanning," "SCA," "secret scanning," "Trivy," "Checkov," "tfsec," "Bandit," "ASVS," "Bearer," or "shift-left security." For chaos / fault injection see chaos-engineering. For Pact contract tests see pact-contract-testing.
selenium-grid
When the user wants to design, deploy, scale, or troubleshoot a self-hosted Selenium Grid 4 cluster — hub, nodes, distributors, sessions, K8s deployment, autoscaling. Use when the user mentions "Selenium Grid," "Selenium Grid 4," "grid hub," "grid node," "selenium docker-selenium," "session queue," "selenoid," "moon," "GridRouter," or "self-hosted grid." For Selenium tests themselves see selenium. For cloud-hosted grid see cloud-test-grids. For mobile see appium.
selenium
When the user wants to design, implement, debug, or migrate Selenium WebDriver tests. Use when the user mentions "Selenium," "Selenium 4," "WebDriver," "Selenium Grid," "Selenium Manager," "BiDi," "By.id," "By.cssSelector," "WebDriverWait," "ExpectedConditions," "RemoteWebDriver," "DesiredCapabilities," "W3C capabilities," "ChromeDriver," "geckodriver," or "page object model." For Cypress-specific questions see cypress. For Playwright-specific questions see playwright. For grid infrastructure see selenium-grid. For cloud-hosted grids see cloud-test-grids.
specflow-reqnroll
When the user wants to design, implement, debug, or migrate BDD tests on .NET using SpecFlow or its open-source successor Reqnroll. Use when the user mentions "SpecFlow," "Reqnroll," "[Binding]," "[Given]," "[When]," "[Then]," ".feature file in .NET," "SpecFlow+ LivingDoc," "SpecFlow.Tools.MsBuild.Generation," "Reqnroll migration," or ".NET BDD." For language-agnostic Gherkin patterns see cucumber-gherkin. For Java BDD see cucumber-gherkin (Cucumber-JVM). For Python BDD see behave. For BDD failure modes see bdd-anti-patterns.
supertest
When the user wants to design, implement, debug, or scale supertest-based API tests in Node.js. Use when the user mentions "supertest," "request(app)," "Express test," "Koa test," "Fastify test," "Jest + supertest," "Mocha + supertest," or "in-process HTTP testing." For Java API testing see rest-assured. For Python see pytest-api. For Postman collections see postman-newman. For contract testing see pact-contract-testing.
test-design-techniques
When the user wants to design test cases systematically — boundary value analysis, equivalence partitioning, pairwise / combinatorial, state-transition, decision tables, classification trees, error guessing. Use when the user mentions "test design," "boundary tests," "equivalence partitioning," "pairwise testing," "all-pairs," "state-transition testing," "decision table," "test case design," "what cases should we cover," or "we have 50 inputs how do we cover them." For higher-level strategy see test-strategy. For the data side see test-data-management.
test-reporting
When the user wants to design, integrate, or improve test reporting — JUnit XML aggregation, HTML dashboards, Allure, Cucumber Reports, screenshots / videos / traces, failure triage, and historical analytics. Use when the user mentions "test reports," "JUnit XML," "Allure," "mochawesome," "Cucumber Reports," "Datadog CI Visibility," "Buildkite Test Analytics," "test result aggregation," "trace / artifacts on failure," "test dashboard," or "trend analysis." For CI orchestration see ci-test-orchestration. For flake analytics see flaky-test-management.
test-strategy
When the user wants to design, audit, or evolve a test strategy — the shape of their test pyramid, the balance of unit / integration / E2E / contract / perf / accessibility tests, what shifts left vs right, what each layer is and isn't responsible for, and how to gate releases. Use when the user mentions "test strategy," "test pyramid," "test trophy," "test ice cream cone," "shift-left," "shift-right," "risk-based testing," "test gates," "balance our test suite," "where to draw the testing line," or "what tests should we write." For specific test-data approach see test-data-management. For environments see test-environment-management. For flake see flaky-test-management.
testcafe
When the user wants to design, implement, debug, or migrate TestCafe tests. Use when the user mentions "TestCafe," ".testcaferc.json," "Selector," "ClientFunction," "fixture," "Role," "t.click," "t.typeText," or "testcafe runner." TestCafe uses a Node-based proxy instead of WebDriver. For modern multi-browser test suites consider playwright. For WebDriver-protocol options see selenium or webdriverio. For Cypress see cypress.
21-cfr-part-11
When the user is building, validating, or auditing a computer system that creates, modifies, maintains, archives, retrieves, or transmits electronic records or applies electronic signatures in an FDA-regulated (GxP) context. Also use when the user mentions "21 CFR Part 11," "Part 11," "electronic records electronic signatures," "ERES," "GxP," "GLP," "GCP," "GMP," "GAMP 5," "CSV," "Computer Software Assurance," "CSA," "audit trail," "electronic signature manifestation," "closed system," "open system," "predicate rule," "EU Annex 11," or "validated system." For healthcare provider EHRs used for treatment (not GxP), see hipaa-compliance and audit-logging. For HITRUST or HIPAA generally, see hipaa-compliance.
accessibility-healthcare
When the user wants to design, build, audit, or remediate accessibility for healthcare apps and patient-facing systems. Also use when the user mentions "WCAG," "WCAG 2.2," "WCAG 3.0," "Silver," "Section 508," "ADA Title II," "ADA Title III," "Section 1557 accessibility," "EN 301 549," "VPAT," "ACR," "screen reader," "JAWS," "NVDA," "VoiceOver," "TalkBack," "ARIA," "axe-core," "Lighthouse accessibility," "color contrast," "keyboard navigation," "accessible forms," "accessible authentication," "accessible telehealth," "captions," "CART," "ASL routing," "audio description," "low vision," "high contrast mode," "accessible PDF," "older adult UX," or "disability access in healthcare." For plain language and reading level, see health-content-writing. For outreach orchestration, see patient-engagement.
billing-claims
When the user wants to design or build software that handles US healthcare claims — submission, adjudication, remittance, denials, or appeals. Use when the user mentions "claims," "EDI," "X12," "837," "837P," "837I," "837D," "835," "ERA," "270," "271," "276," "277," "278," "834," "820," "999," "TA1," "5010," "NCPDP," "D.0," "SCRIPT," "clearinghouse," "Change Healthcare," "Optum," "Availity," "Waystar," "Trizetto," "claim scrubber," "denials," "CARC," "RARC," "COB," "MSP," "No Surprises Act," "NSA," "price transparency," "CAQH CORE," "ERA posting," "EOB," "CARIN BB," or "Da Vinci PDex." For coding the claim, see medical-coding. For prior auth (278/Da Vinci PAS), see prior-authorization. For VBC contract economics, see value-based-care.
cda-ccda
When the user wants to author, parse, validate, or transform Clinical Document Architecture (CDA) or Consolidated CDA (C-CDA) documents. Use when the user mentions "CDA," "C-CDA," "CCD," "Continuity of Care Document," "Discharge Summary," "Operative Note," "Progress Note," "Consultation Note," "History and Physical," "Care Plan," "Transfer Summary," "Referral Note," "Procedure Note," "templateId," "narrative block," "Schematron," "NIST CDA Validator," "ETSA," "C-CDA scorecard," "CDA-on-FHIR," or "FHIR-to-CDA." For non-document FHIR data, see fhir-integration. For HL7 v2 documents transported via MDM, see hl7-v2.
clinical-ai-ml
When the user wants to build, evaluate, deploy, or monitor machine learning models for clinical or operational healthcare use cases. Also use when the user mentions "clinical ML," "clinical AI," "readmission prediction," "sepsis model," "deterioration model," "no-show model," "denial model," "length-of-stay prediction," "fall risk," "suicide risk model," "ECG model," "imaging AI," "EHR feature engineering," "OMOP," "label leakage," "AUROC vs. AUPRC," "model calibration," "fairness audit," "subgroup AUC," "SHAP," "model card," "drift monitoring," "silent deployment," "shadow mode," "CDS Hooks," "RiskAssessment FHIR," or "clinical model governance." For FDA SaMD pathway see fda-samd. For health chatbots / LLMs see health-chatbots. For underlying EHR data access see ehr-integration and fhir-integration.
clinical-decision-support
When the user wants to design, build, deploy, or evaluate a clinical decision support (CDS) tool. Also use when the user mentions "CDS," "CDS Hooks," "patient-view hook," "order-sign hook," "order-select hook," "encounter-start," "appointment-book," "CDS card," "alert fatigue," "interruptive alert," "5 rights of CDS," "order set," "clinical pathway," "CQL," "Clinical Quality Language," "BPA," "best practice advisory," "HHS CDS exemption," "Cures Act CDS criteria," or "FDA SaMD CDS." For SMART app OAuth, see smart-on-fhir. For order entry plumbing, see cpoe-orders. For SaMD regulatory pathway, see fda-samd.
clinical-documentation
When the user wants to design clinical documentation workflows, templates, or note ingestion. Also use when the user mentions "clinical note," "progress note," "H&P," "history and physical," "SOAP note," "APSO," "discharge summary," "consult note," "op note," "operative note," "SmartPhrase," "SmartForm," "dot phrase," "structured data capture," "clinical NLP," "cTAKES," "MedSpaCy," "Amazon Comprehend Medical," "HealthLake," "ambient scribe," "DAX," "Nuance DAX," "Suki," "Abridge," "Augmedix," "DeepScribe," or "AI scribe." For underlying FHIR resources, see fhir-integration. For order entry, see cpoe-orders. For HIPAA implications of recording encounters, see hipaa-compliance.
clinical-research
When the user wants to design, build, or operate clinical research informatics tools and workflows. Use when the user mentions "clinical trial," "clinical research," "RCT," "observational study," "registry study," "pragmatic trial," "real-world evidence," "RWE," "decentralized clinical trial," "DCT," "EDC," "REDCap," "Medidata Rave," "Veeva Vault EDC," "Castor," "OpenClinica," "CDISC," "CDASH," "SDTM," "ADaM," "Define-XML," "SEND," "eSource," "eCRF," "IRB," "single IRB," "sIRB," "Common Rule," "Belmont Report," "21 CFR Part 50," "21 CFR Part 56," "GCP," "ICH E6," "ICH E2B," "SAE," "SUSAR," "IWRS," "IRT," "randomization," "eConsent," "ePRO," "eCOA," "CTMS," "Veeva CTMS," "Florence eBinders," "ClinicalTrials.gov," or "FDAAA 801." For HIPAA Authorization vs. waiver mechanics, see hipaa-compliance. For 21 CFR Part 11 e-records / e-signatures, see 21-cfr-part-11. For trial-related FHIR integration with EHRs, see fhir-integration.
cpoe-orders
When the user wants to design, build, or integrate with computerized provider order entry (CPOE). Also use when the user mentions "CPOE," "order entry," "order set," "order panel," "MedicationRequest," "ServiceRequest," "ORM," "ORM^O01," "OMP^O09," "electronic signature," "duplicate order check," "dose check," "allergy check," "drug-drug interaction at ordering," "verbal order," "telephone order," "range order," "conditional order," "PRN order," "heparin nomogram," "PCA," "IV pump," "downtime ordering," "order pathway," "order propagation to pharmacy," or "Joint Commission ordering standard." For ambient scribe note write-back, see clinical-documentation. For CDS at the moment of ordering, see clinical-decision-support. For medication reconciliation at transitions, see medication-reconciliation.
dicom-imaging
When the user wants to design, integrate, or troubleshoot DICOM medical imaging systems. Use when the user mentions "DICOM," "PACS," "VNA," "modality," "C-STORE," "C-FIND," "C-MOVE," "C-ECHO," "DIMSE," "DICOMweb," "WADO," "QIDO," "STOW," "UPS-RS," "MWL," "Modality Worklist," "MPPS," "Structured Report," "SR," "SOP Class," "AE title," "transfer syntax," "DICOM anonymization," or specific modalities like CT/MR/CR/DX/US/NM/PT/MG. For non-imaging clinical data exchange, see fhir-integration or hl7-v2. For AI on imaging, see medical-imaging-ai.
ehr-integration
When the user wants to integrate with a specific EHR vendor's APIs, app program, or sandbox. Also use when the user mentions "Epic," "App Orchard," "Connection Hub," "Cerner," "Oracle Health," "Millennium," "CareAware," "Code Console," "Ignite APIs," "HealtheLife," "Athenahealth," "athenaOne," "MDP," "More Disruption Please," "Meditech," "Greenfield," "eClinicalWorks," "NextGen," "Allscripts," "Veradigm," "OpenEMR," "EHR sandbox," "vendor app review," "Care Everywhere," "Hyperdrive," "Chronicles," "Interconnect," "DocumentReference write-back," or "MDM message." For FHIR-resource-level work, see fhir-integration. For SMART OAuth specifics, see smart-on-fhir. For HL7 v2 messaging, see hl7-v2.
fda-samd
When the user wants to determine if their software is FDA-regulated, plan a submission pathway, design under quality systems, or maintain a regulated device post-market. Also use when the user mentions "SaMD," "Software as a Medical Device," "FDA," "510(k)," "De Novo," "PMA," "CDS exemption," "21st Century Cures," "Cures Act 3060," "Predetermined Change Control Plan," "PCCP," "Good Machine Learning Practice," "GMLP," "QSR," "QMSR," "21 CFR Part 820," "ISO 13485," "FDA cybersecurity," "premarket cybersecurity," "MDR reporting," "medical device reporting," "FDA software documentation," "IMDRF," or "ML-enabled device." For building the ML model itself see clinical-ai-ml. For chatbot regulatory framing see health-chatbots.
fhir-integration
When the user wants to design, implement, debug, or review FHIR integrations. Use when the user mentions "FHIR," "FHIR R4," "FHIR R5," "FHIR resource," "FHIR bundle," "FHIR search," "CapabilityStatement," "US Core," "USCDI," "CARIN BB," "Da Vinci," "mCODE," "IPS," "bulk data," "$export," "OperationOutcome," or names specific resources like Patient/Encounter/Observation/Condition/MedicationRequest. For SMART OAuth flows, see smart-on-fhir. For HL7 v2 pipe-delimited messages, see hl7-v2. For terminology services and code systems, see terminology-services. For CDA documents, see cda-ccda.
gdpr-health-data
When the user is processing health, genetic, or biometric data of people in the EU/EEA, UK, or other GDPR-aligned jurisdictions, or designing controls for special-category health data. Also use when the user mentions "GDPR," "Article 9," "special category data," "Article 6," "lawful basis," "explicit consent," "controller," "processor," "joint controller," "DPA," "data processing agreement," "DPIA," "DPO," "Article 30," "records of processing," "72 hour breach," "SCCs," "Standard Contractual Clauses," "Schrems II," "Transfer Impact Assessment," "TIA," "Recital 26," "UK GDPR," "EHDS," or "European Health Data Space." For US HIPAA, see hipaa-compliance. For operational PHI controls applicable globally, see phi-handling. For audit-log design, see audit-logging.
genomics-precision-medicine
When the user wants to design, build, or integrate genomics and precision-medicine informatics. Use when the user mentions "genomics," "precision medicine," "VCF," "gVCF," "BAM," "CRAM," "FASTQ," "variant calling," "variant annotation," "HGVS," "ACMG," "AMP/CAP/ASCO," "ClinGen," "ClinVar," "PharmGKB," "CPIC," "pharmacogenomics," "PGx," "GA4GH," "VRS," "Phenopackets," "FHIR Genomics," "mCODE," "molecular tumor board," "liquid biopsy," "ctDNA," "MRD," "polygenic risk score," "PRS," "incidental findings," "ACMG SF," "GINA," "GRCh38," or "T2T-CHM13." For broader clinical AI lifecycle, see clinical-ai-ml. For SaMD on genomic algorithms, see fda-samd. For the EHR integration of orders/results, see ehr-integration and fhir-integration.
health-chatbots
When the user wants to design, build, evaluate, or deploy a conversational AI / chatbot in a healthcare setting. Also use when the user mentions "health chatbot," "symptom checker," "triage bot," "mental health chatbot," "medication reminder bot," "appointment booking bot," "post-discharge follow-up bot," "AI scribe," "ambient scribe," "clinical conversational AI," "LLM in healthcare," "HIPAA-eligible LLM," "Azure OpenAI BAA," "Bedrock BAA," "Vertex AI BAA," "Anthropic BAA," "suicide safety classifier," "988," "self-harm detection in chat," "retrieval-grounded healthcare," or "patient-facing AI." For underlying ML modeling see clinical-ai-ml. For FDA pathway analysis see fda-samd.
health-content-writing
When the user wants to write, edit, or audit patient-facing health content. Also use when the user mentions "patient education," "after-visit summary," "AVS," "patient portal copy," "OpenNotes," "plain language," "health literacy," "readability," "Flesch-Kincaid," "SMOG," "FRY," "Dale-Chall," "teach-back," "condition page," "discharge instructions," "secure-message tone," "medication instructions," "informed-consent plain language," "CLAS standards," "Section 1557 language access," "translation," "transcreation," "back-translation," "icon array," or "numeracy in healthcare." For accessibility of the surrounding UI, see accessibility-healthcare. For program-level outreach orchestration, see patient-engagement. For clinical-documentation written for other clinicians (not patients), see clinical-documentation.
health-data-lake
When the user wants to design, build, or operate a clinical / healthcare data lake, lakehouse, or warehouse. Use when the user mentions "health data lake," "clinical data warehouse," "healthcare lakehouse," "OMOP," "PCORnet CDM," "Sentinel CDM," "i2b2," "CMS BCDA," "OHDSI," "ATLAS," "HADES," "Athena vocabulary," "FHIR Bulk Data," "$export," "flat FHIR," "SQL-on-FHIR," "Pathling," "Epic Clarity," "Caboodle," "Cerner Millennium ETL," "EMPI," "data quality dashboard," "Achilles," "tokenization vault," "Delta Lake," "Iceberg," "bronze/silver/gold," "Unity Catalog," "Lake Formation," "Snowflake healthcare," "Databricks Lakehouse for Healthcare," or "HIPAA-eligible warehouse." For analytics on top of curated data, see population-health-analytics or clinical-research. For raw FHIR API integration, see fhir-integration. For HL7 v2 ingestion specifics, see hl7-v2.
healthcare-context
When the user wants to create or update their healthcare context document, or whenever any other healthcare skill needs to understand the organization, patient population, regulatory jurisdiction, EHR/clinical systems, terminology in use, and security posture. Also use when the user mentions "healthcare context," "healthcare profile," "organization context," "covered entity," "business associate," "regulated jurisdiction," "EHR vendor," or "we are a [hospital/clinic/payer/digital health/etc]." Read this file first before any other healthcare skill — it controls assumptions every other skill makes (HIPAA vs. GDPR, FHIR vs. HL7 v2, Epic vs. Cerner, etc.).
healthcare-cybersecurity
When the user wants to design, assess, or harden a healthcare cybersecurity program — covering threat-aligned safeguards, medical device security, ransomware readiness, network segmentation, supply chain, and incident response. Also use when the user mentions "HHS 405(d)," "HICP," "Health Industry Cybersecurity Practices," "NIST CSF healthcare," "NIST SP 800-66," "medical device cybersecurity," "FDA premarket cybersecurity," "FDA postmarket cybersecurity," "SBOM," "SPDX," "CycloneDX," "MDS²," "IEC 80001," "IEC 62443," "zero trust healthcare," "network segmentation clinical," "ransomware playbook," "MFA healthcare," "PAM," or "phishing healthcare." For the regulatory basis, see hipaa-compliance. For operational PHI controls, see phi-handling. For audit-log design, see audit-logging.
hitrust-csf
When the user is preparing for, scoping, scoring, or maintaining a HITRUST CSF assessment or certification. Also use when the user mentions "HITRUST," "HITRUST CSF," "e1," "i1," "r2," "MyCSF," "PRISMA," "control maturity," "CAP," "corrective action plan," "validated assessment," "interim assessment," "readiness assessment," "inheritance," "CSP inheritance," "authoritative sources," or "HITRUST audit." For HIPAA itself, see hipaa-compliance. For cybersecurity program design, see healthcare-cybersecurity. For audit logs, see audit-logging.
hl7-v2
When the user wants to design, parse, generate, or troubleshoot HL7 v2.x pipe-delimited messages. Use when the user mentions "HL7 v2," "HL7 2.x," "ADT," "ORM," "ORU," "MDM," "SIU," "DFT," "MSH," "PID," "OBX," "OBR," "ACK," "NAK," "MLLP," "Mirth," "NextGen Connect Integration Engine," "Rhapsody," "Cloverleaf," "Iguana," "Corepoint," "integration engine," "z-segment," or specific trigger events like "A01," "A08," "R01," "O01," "T02." For modern REST/JSON exchange, see fhir-integration. For DICOM imaging messages, see dicom-imaging. For CDA clinical documents, see cda-ccda.
ihe-profiles
When the user wants to design, deploy, or troubleshoot IHE (Integrating the Healthcare Enterprise) integration profiles. Use when the user mentions "IHE," "XDS," "XDS.b," "XDR," "XDM," "XCA," "PIX," "PDQ," "ATNA," "BPPC," "CT (Consistent Time)," "DSUB," "MHD," "PIXm," "PDQm," "IUA," "MHDS," "mCSD," "Cross-Enterprise Document Sharing," "ITI Technical Framework," "PCC profile," "RAD profile (SWF, XDS-I.b)," or "actors and transactions." For FHIR-native exchange, see fhir-integration. For TEFCA-level policy and QHIN structure, see tefca-hie. For audit details, see audit-logging.
medical-coding
When the user wants to design or build software that touches medical coding — computer-assisted coding (CAC), autocoders, NLP for clinical coding, code-set validation, audit support, HCC/risk-adjustment capture, or revenue-cycle pipelines. Use when the user mentions "ICD-10," "ICD-10-CM," "ICD-10-PCS," "CPT," "HCPCS," "HCPCS Level II," "J-codes," "CDT," "NDC," "DRG," "MS-DRG," "APC," "modifiers," "NCCI edits," "MUE," "PTP," "LCD," "NCD," "E/M coding," "MDM," "computer-assisted coding," "CAC," "autocoding," "coding audit," "RAC," "ZPIC," "UPIC," "OIG audit," "problem list," "HCC capture," or "RAF coding." For end-to-end claim submission/remittance, see billing-claims. For HCC risk score modeling and VBC programs, see value-based-care. For prior auth, see prior-authorization. This skill is for engineers building coding systems — it does not assign codes for real patient encounters.
medical-imaging-ai
When the user wants to design, build, validate, deploy, or monitor AI/ML on medical images. Use when the user mentions "medical imaging AI," "radiology AI," "imaging ML," "DICOM AI," "PACS AI," "CAD," "computer-aided detection," "computer-aided diagnosis," "AI triage," "worklist prioritization," "U-Net," "nnU-Net," "MONAI," "MedSAM," "BiomedCLIP," "RadFM," "MIMIC-CXR," "CheXpert," "TCIA," "LIDC-IDRI," "ChestX-ray14," "DICOM SR for AI results," "AI orchestrator," "Nuance Precision Imaging Network," "Blackford," "Calantic," "DeepHealth," "GE Edison," "Philips ISP," or asks how to wire imaging AI into the reading workflow. For pure DICOM transport without AI, see dicom-imaging. For SaMD regulatory work, see fda-samd. For general clinical AI lifecycle, see clinical-ai-ml.
medication-reconciliation
When the user wants to design, build, or improve medication reconciliation workflows at transitions of care. Also use when the user mentions "med rec," "medication reconciliation," "BPMH," "best possible medication history," "admission med rec," "discharge med rec," "transfer med rec," "Surescripts medication history," "pharmacy fill history," "RxNorm," "RxCUI," "SCD," "SBD," "NDC," "DDI," "drug-drug interaction," "First Databank," "Medi-Span," "Multum," "RxNav DDI," "ISMP high-alert," "MedicationStatement vs MedicationRequest," "MedicationDispense," "MedicationAdministration," "NPSG 03.06.01," or "MIPS med rec measure." For order entry plumbing, see cpoe-orders. For RxNorm + ATC terminology depth, see terminology-services.
patient-engagement
When the user wants to design, build, or evaluate a patient engagement program. Also use when the user mentions "patient engagement," "patient outreach," "patient activation," "patient retention," "appointment reminders," "no-show reduction," "care gap closure," "preventive screening outreach," "chronic care management outreach," "post-discharge follow-up," "PAM," "patient activation measure," "CAHPS," "NPS," "omnichannel patient communication," "SMS healthcare," "TCPA," "HIPAA texting," "secure messaging," "behavior change," "stages of change," "Health Belief Model," "COM-B," "BJ Fogg," "Salesforce Health Cloud," "Twilio healthcare," "Innovaccer," "Notable," "Memora," "Conversa," "mPulse," "Unite Us," "Findhelp," "NowPow," or "closed-loop SDOH referral." For the content of messages, see health-content-writing. For accessibility of touchpoints, see accessibility-healthcare. For the underlying portal, see patient-portal.
patient-portal
When the user wants to design or build a patient portal, patient mobile app, or patient-facing API. Also use when the user mentions "patient portal," "MyChart," "FollowMyHealth," "NextMD," "Patient Gateway," "patient access," "CMS Patient Access Rule," "Information Blocking," "USCDI," "OpenNotes," "open notes," "proxy access," "caregiver access," "adolescent confidentiality," "minor portal," "secure messaging," "online scheduling," "results release," "patient identity proofing," "IAL2," "ID.me," "CLEAR," "Persona," "Stripe Identity," "Socure," or "patient mobile app." For provider-facing SMART apps see smart-on-fhir. For telehealth video flows see telehealth-platform.
phi-handling
When the user is designing or reviewing the operational controls around PHI — how to de-identify, anonymize, pseudonymize, encrypt, mask, minimize, or securely retain Protected Health Information across structured data, free text, images, audio, and biometrics. Also use when the user mentions "Safe Harbor de-identification," "Expert Determination," "limited data set," "DUA," "k-anonymity," "l-diversity," "t-closeness," "differential privacy," "encryption at rest," "TLS 1.2," "KMS," "HSM," "RBAC," "ABAC," "break the glass," "minimum necessary in practice," "DICOM PHI," "burned-in PHI," "audio PHI," "biometric PHI," "secure deletion," "retention schedule," or "cross-border PHI." For the regulatory backdrop, see hipaa-compliance. For audit-log design, see audit-logging. For EU rules, see gdpr-health-data.
population-health-analytics
When the user wants to design, build, or evaluate a population health analytics platform. Use when the user mentions "population health," "pop health," "risk stratification," "HCC," "CMS-HCC," "ACG," "DxCG," "LACE," "rising risk," "high cost members," "care gaps," "HEDIS," "eCQM," "attribution," "value-based care analytics," "SDOH," "Z-codes," "Gravity Project," "HRSN," "PRAPARE," "AHC-HRSN," "OMOP," "PCORnet," "registry," "patient registry," "FHIR Bulk Export," "longitudinal patient record," "patient master," "MPI for analytics," "network leakage," "outreach prioritization," "uplift modeling," "PAM," or "patient activation measure." For VBC contract design, see value-based-care. For FHIR Bulk Export mechanics, see fhir-integration. For the upstream clinical and claims feeds, see ehr-integration and billing-claims.
prior-authorization
When the user wants to design, build, integrate, or automate prior authorization workflows. Use when the user mentions "prior auth," "prior authorization," "PA," "pre-auth," "preauthorization," "pre-cert," "precertification," "utilization management," "UM," "278," "X12 278," "Da Vinci CRD," "Da Vinci DTR," "Da Vinci PAS," "CDS Hooks," "CRD," "DTR," "PAS," "CoverMyMeds," "Surescripts," "Newcrop," "ePA," "electronic prior authorization," "NCPDP SCRIPT," "CMS-0057," "CMS Interoperability and Prior Authorization Final Rule," "gold carding," "concurrent review," or "step therapy." For claim submission after PA is obtained, see billing-claims. For coding the service being authorized, see medical-coding. For VBC delegation of UM, see value-based-care.
public-health-reporting
When the user wants to design, build, or troubleshoot reporting from clinical systems to public health authorities. Use when the user mentions "public health reporting," "ELR," "Electronic Laboratory Reporting," "eCR," "electronic case reporting," "eICR," "Reportability Response," "RR," "immunization registry," "IIS," "VXU," "syndromic surveillance," "BioSense," "NSSP," "cancer reporting," "NAACCR," "NPCR," "SEER," "birth registry," "EBR," "death registry," "EDR," "EDRS," "reportable conditions," "RCKMS," "CSTE," "APHL AIMS," "NEDSS," "ONC g.10," "Promoting Interoperability public health," "state HIE submission," or "COVID case reporting." For the underlying HL7 v2 message mechanics, see hl7-v2. For FHIR resources used by these IGs, see fhir-integration. For terminology bindings (LOINC, SNOMED CT, ICD-10-CM, CVX), see terminology-services.
remote-patient-monitoring
When the user wants to design, build, or bill a remote patient monitoring (RPM) program. Also use when the user mentions "RPM," "remote patient monitoring," "RTM," "remote therapeutic monitoring," "CPT 99453," "99454," "99457," "99458," "99091," "98975," "98976," "98977," "98980," "98981," "16-day rule," "BP cuff integration," "glucometer integration," "CGM," "pulse oximeter," "weight scale," "ECG patch," "smart inhaler," "peak flow," "device telemetry," "FHIR Observation ingest," "cellular device," "BLE device," or "patient device pairing." For consumer wearables (Apple/Google/Fitbit/Garmin/Oura/Whoop) see wearables-integration. For video visits paired with RPM see telehealth-platform.
smart-on-fhir
When the user wants to build a SMART on FHIR app, configure OAuth against an EHR's FHIR API, or implement Backend Services. Also use when the user mentions "SMART," "SMART on FHIR," "SMART App Launch," "EHR launch," "standalone launch," "well-known/smart-configuration," "smart-configuration," "launch context," "launch/patient," "launch/encounter," "SMART scopes," "patient/*.read," "user/*.write," "system/*.read," "SMART v2 scopes," "fhirUser," "PKCE," "JWT assertion," "Backend Services," "client credentials FHIR," or "Bulk Data Access." For deeper FHIR resource work, see fhir-integration. For vendor-specific OAuth quirks, see ehr-integration. For CDS Hooks integration, see clinical-decision-support.
tefca-hie
When the user wants to plan, join, or build against TEFCA or other US health information exchange networks. Use when the user mentions "TEFCA," "Common Agreement," "QHIN," "QTF," "QHIN Technical Framework," "ONC TEFCA," "Carequality," "CommonWell," "eHealth Exchange," "Health Gorilla," "Epic Nexus," "KONZA," "MedAllies," "Velatura," "Direct messaging," "HISP," "IAS," "Individual Access Services," "Required Information for Coverage," "regional HIE," "query-based exchange," "treatment payment operations," or "patient matching across networks." For the underlying technical profiles, see ihe-profiles. For FHIR mechanics, see fhir-integration. For identity controls, see healthcare-cybersecurity.
telehealth-platform
When the user wants to design, build, or evaluate a telehealth platform. Also use when the user mentions "telehealth," "telemedicine," "virtual care," "video visit," "asynchronous care," "store-and-forward," "e-visit," "tele-ICU," "tele-stroke," "tele-behavioral," "tele-psychiatry," "WebRTC video," "SIP video," "Doxy.me," "Zoom for Healthcare," "Microsoft Teams EHR," "originating site," "distant site," "IMLC," "PsyPACT," "Nurse Licensure Compact," "telehealth parity," "Ryan Haight," "DEA telemedicine," "controlled substances by telemedicine," or "RPM video." For wearables/RPM device telemetry, see remote-patient-monitoring. For consent and PHI flow, see hipaa-compliance and phi-handling.
terminology-services
When the user wants to choose, map, validate, or serve healthcare code systems and value sets. Use when the user mentions "SNOMED CT," "ICD-10-CM," "ICD-10-PCS," "ICD-11," "CPT," "HCPCS," "LOINC," "RxNorm," "NDC," "UCUM," "CVX," "terminology server," "ValueSet," "ConceptMap," "$expand," "$lookup," "$validate-code," "$translate," "VSAC," "UMLS," "OMOP Athena," "RxNav," or "code mapping." For FHIR resource modeling generally, see fhir-integration. For coding for billing workflow, see medical-coding.
value-based-care
When the user wants to design or build software for value-based care (VBC) — risk adjustment, quality measurement, ACO/REACH analytics, capitation reconciliation, bundled payments, MIPS/QPP, HEDIS, Star Ratings, attribution, network performance. Use when the user mentions "value-based care," "VBC," "ACO," "MSSP," "REACH," "ACO REACH," "PCF," "AHEAD," "CKCC," "KCC," "OCM," "EOM," "CJR," "BPCI-A," "DCE," "DSO," "MIPS," "QPP," "APM," "HEDIS," "Star Ratings," "HCC," "CMS-HCC," "v28," "RAF," "RADV," "MEAT," "attribution," "shared savings," "capitation," "bundled payment," "eCQM," "CQL," "MIPS measure," "TIN/NPI hierarchy," "leakage," or "network steerage." For coding mechanics that feed risk adjustment, see medical-coding. For claims and remittance reconciliation, see billing-claims. For PA delegation under VBC, see prior-authorization.
wearables-integration
When the user wants to integrate consumer wearables or fitness devices into a clinical or health-app workflow. Also use when the user mentions "Apple HealthKit," "HKQuantityType," "HKSampleType," "Apple Health Records," "Health Connect," "Google Health Connect," "Google Fit," "Fitbit Web API," "Garmin Health API," "Oura," "Whoop," "Dexcom," "Abbott LibreView," "Medtronic CareLink," "Withings," "CGM integration," "BLE health profile," "GATT," "Heart Rate Profile," "Blood Pressure Profile," "Glucose Profile," "Body Composition Service," "Health Device Profile," "HDP," or "consumer wearable BAA." For clinical-grade RPM with billable CPT codes see remote-patient-monitoring. For FHIR Observation modeling see fhir-integration.
cliproof
Capture a real terminal command and its real output as a polished screenshot or animated GIF, then embed it into README.md as "proof it runs" evidence for GitHub visitors. Use when the user wants a terminal screenshot, CLI demo, README demo GIF, a styled (macOS/iOS or Windows) terminal image of a program/service/build, to "show the command output", or any visual proof that a product actually ships and works. Captures genuine output (never fabricated), redacts secrets, and inserts idempotently.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.