- Ingresos de jubilación y estrategia de retiradas
- Fiscalidad: Roth/RRSP, cosecha de pérdidas, cambios normativos
- Planificación patrimonial, de seguros y transfronteriza
- Herramientas del asesor: preparación de reuniones, prefiltro de cumplimiento
21.500+ skills y agentes. Todos gobernados.
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
Empieza por una colección curada.
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.
- Atención, ventas y customer success
- Service desk de TI, RR. HH. y operaciones financieras
- Recepción legal, compras y operaciones de campo
- Riesgo y cumplimiento
- Triaje de bandeja de entrada y redacción de correos
- Preparación de reuniones, notas y seguimiento
- Agenda inteligente y resumen diario
- Orquestación de asistente ejecutivo
- Siniestros inteligentes, actuarial y AML
- Auditoría, GRC e informes ESG
- ITAM / ITSM y operaciones de seguridad
- Entornos de datos y analítica
Encuentra la habilidad que tu equipo necesita.
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.
864 resultados · Telecommunications
Summarize supplied work — NOC Engineer, Telecommunications
Summarize supplied work for NOC Engineer teams in Telecommunications, delivered by the Routing Advisor pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess priority and risk — NOC Engineer, Telecommunications
Assess priority and risk for NOC Engineer teams in Telecommunications, delivered by the Routing Advisor pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend a routing decision — NOC Engineer, Telecommunications
Recommend a routing decision for NOC Engineer teams in Telecommunications, delivered by the Routing Advisor pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Query supplied historical data — NOC Engineer, Telecommunications
Query supplied historical data for NOC Engineer teams in Telecommunications, delivered by the Trend Briefing pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize observed trends — NOC Engineer, Telecommunications
Summarize observed trends for NOC Engineer teams in Telecommunications, delivered by the Trend Briefing pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare questions for forecast review — NOC Engineer, Telecommunications
Prepare questions for forecast review for NOC Engineer teams in Telecommunications, delivered by the Trend Briefing pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Search approved onboarding knowledge — NOC Engineer, Telecommunications
Search approved onboarding knowledge for NOC Engineer teams in Telecommunications, delivered by the Onboarding Guide pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft step-by-step guidance — NOC Engineer, Telecommunications
Draft step-by-step guidance for NOC Engineer teams in Telecommunications, delivered by the Onboarding Guide pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a review checklist — NOC Engineer, Telecommunications
Prepare a review checklist for NOC Engineer teams in Telecommunications, delivered by the Onboarding Guide pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize supplied feedback — NOC Engineer, Telecommunications
Summarize supplied feedback for NOC Engineer teams in Telecommunications, delivered by the Feedback Summary pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Surface recurring points — NOC Engineer, Telecommunications
Surface recurring points for NOC Engineer teams in Telecommunications, delivered by the Feedback Summary pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare follow-up questions — NOC Engineer, Telecommunications
Prepare follow-up questions for NOC Engineer teams in Telecommunications, delivered by the Feedback Summary pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Search approved knowledge — NOC Engineer, Telecommunications
Search approved knowledge for NOC Engineer teams in Telecommunications, delivered by the Research & Discovery pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize supplied findings — NOC Engineer, Telecommunications
Summarize supplied findings for NOC Engineer teams in Telecommunications, delivered by the Research & Discovery pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft a research brief — NOC Engineer, Telecommunications
Draft a research brief for NOC Engineer teams in Telecommunications, delivered by the Research & Discovery pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Search approved process knowledge — NOC Engineer, Telecommunications
Search approved process knowledge for NOC Engineer teams in Telecommunications, delivered by the Process Guidance pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize supplied process context — NOC Engineer, Telecommunications
Summarize supplied process context for NOC Engineer teams in Telecommunications, delivered by the Process Guidance pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft next-step guidance — NOC Engineer, Telecommunications
Draft next-step guidance for NOC Engineer teams in Telecommunications, delivered by the Process Guidance pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize supplied request context — Churn Analyst, Telecommunications
Summarize supplied request context for Churn Analyst teams in Telecommunications, delivered by the Intake Review & Triage pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess urgency and risk — Churn Analyst, Telecommunications
Assess urgency and risk for Churn Analyst teams in Telecommunications, delivered by the Intake Review & Triage pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend a review priority — Churn Analyst, Telecommunications
Recommend a review priority for Churn Analyst teams in Telecommunications, delivered by the Intake Review & Triage pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Condense supplied content — Churn Analyst, Telecommunications
Condense supplied content for Churn Analyst teams in Telecommunications, delivered by the Document Summarizer pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Surface key points — Churn Analyst, Telecommunications
Surface key points for Churn Analyst teams in Telecommunications, delivered by the Document Summarizer pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Produce a concise brief — Churn Analyst, Telecommunications
Produce a concise brief for Churn Analyst teams in Telecommunications, delivered by the Document Summarizer pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Instalar es lo fácil. La gobernanza viene incluida.
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.
Elige en el catálogo
Filtra por tu industria y tu rol; cada elemento indica los sistemas a los que se conecta y las habilidades que invoca.
Conéctalo a tu stack
Conectores, servidores MCP e importaciones OpenAPI — acotados por listas de permitidos y DLP en el gateway.
Cada ejecución pasa por los controles
Identidad, presupuesto, guardrails, registro, Control Tower, ejecución, guarda de salida — y luego un recibo firmado en el Trust Ledger. En todos los planes.
¿No encuentras la habilidad que necesitas?
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.