5,814 agentes preconstruidos y 15,654 habilidades de biblioteca en 24 sectores y 12 roles por sector, instalables desde el catálogo, conectados a tus sistemas y ejecutados a través de la misma cadena de puertas de fallo cerrado que todo lo demás en Cortex.
21,511 plantillas de biblioteca en la matriz del catálogo
Suites creadas a mano para los trabajos que las empresas automatizan primero — cada colección se entrega gobernada, con políticas y auditoría incorporadas.
Busca entre 21,500+ habilidades y agentes gobernados, o filtra por sector y tipo: cada resultado se instala desde el catálogo y pasa por las mismas puertas.
648 resultados · Healthcare & Hospital Admin · Habilidades
Summarize a supplied record for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Record Review pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess possible risk for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Record Review pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Flag items for human review for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Record Review pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Run a parameterized read query for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Data Query & Summary pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize returned records for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Data Query & Summary pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a result-set overview for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Data Query & Summary pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Check supplied context against policy for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Compliance Checker pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Surface potential policy issues for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Compliance Checker pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend review items for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Compliance Checker pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess supplied risk context for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Risk Assessment pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Explain assessment drivers for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Risk Assessment pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend human review for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Risk Assessment pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Query supplied record data for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Reconciliation Brief pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize potential discrepancies for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Reconciliation Brief pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a reconciliation brief for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Reconciliation Brief pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess a supplied exception for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Exception Review pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize the assessment for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Exception Review pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend follow-up review for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Exception Review pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Run an on-demand read query for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the On-demand Reporting & Insights pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize query results for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the On-demand Reporting & Insights pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Highlight supplied exceptions for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the On-demand Reporting & Insights pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess supplied context for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Decision Support pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft a recommended response for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Decision Support pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare rationale for review for Clinical Documentation teams in Healthcare & Hospital Admin, delivered by the Decision Support pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Los agentes de la biblioteca no son scripts: son identidades gobernadas. Instalar uno lo registra con un propietario, un presupuesto, modelos y acciones permitidos y un lugar en el registro de auditoría.
Filtra por tu industria y tu rol; cada elemento indica los sistemas a los que se conecta y las habilidades que invoca.
Conectores, servidores MCP e importaciones OpenAPI — acotados por listas de permitidos y DLP en el gateway.
Identidad, presupuesto, guardrails, registro, Control Tower, ejecución, guarda de salida — y luego un recibo firmado en el Trust Ledger. En todos los planes.
El constructor visual de habilidades permite lanzar nuevas habilidades sin código — o dinos qué te falta y te señalaremos el patrón gobernado más cercano.