Every Nexaq agent runs on a curated library of named, scoped skills. Code-generation skills run inside the IDE (Cursor, Claude Code) where the engineer works. Integration skills connect to enterprise tools via MCP. Analysis and reporting skills compose the rest.
Each agent makes one Claude Sonnet 4.6 call with its skills represented in the prompt structure. The skill chips you see visualize composition — they are not real-time tool firings. In production, these become real Cursor, Claude Code, and MCP invocations against your actual systems.
Every integration is an MCP server. The agent talks to the tool through a standard protocol — no custom adapters, no API key sprawl, full audit trail. Add a connector, and every agent that benefits from it gains the capability.
Pull sprint stories, push findings as issues, attach quality reports as comments.
Pull test cases and execution history, push EVAN-generated cases and run results.
Pull work items + test plans, push test runs and outcomes via ADO Test Plans API.
Open PRs with EVAN automation, SARA remediations, and ARIA-recommended changes.
Lightweight issue tracking. Pull cycles + issues, push findings as new issues.
Jira-native test management. Sync test cases and runs alongside stories.
Post sprint quality reports to channels, alert on Critical findings, route handoffs to teams.
Post sprint reports as adaptive cards, alert channels on Critical findings, link recommendations back to ADO.