More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    OutSystems Review: Architecture, Performance & Test Plans

    1

    Review OutSystems 11 / ODC apps: aggregate and performance anti-patterns, security, architecture, plus a ready test plan.

    $12

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    OutSystems Review: Architecture, Performance & Test Plans

    OutSystems Review: Architecture, Performance & Test Plans

    Example session with this skill installed

    Our Orders screen takes 8 seconds. Preparation loads orders, then for each order calls GetCustomer inside a For Each. Review it.

    • Read your context and instructions
    • Compiled the outsystems review

    CRITICAL - Orders screen / Preparation: Aggregate GetCustomer is called inside a For Each over GetOrders (N+1 queries).
    Fix: replace both with one Aggregate on Order with a join to Customer and "Only necessary columns" (Id, Number, Total, Customer.Name). Add pagination (Max Records 20 + Start Index).
    Measure first: check the screen preparation time in the platform logs before and after the change.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A senior OutSystems reviewer on call. Paste your module logic, describe your screens or share screenshots of your aggregates and flows, and get a prioritized review written in Service Studio / ODC Studio terms, so you know exactly where to click and what to change.

    What it checks

    • Architecture: layering (Architecture Canvas for OS11, app/library boundaries in ODC), circular dependencies, reuse with Blocks and public actions
    • Data and performance: aggregates inside loops, fetching all columns, missing pagination, missing indexes, heavy screen preparation, client round trips, timers and batch processing
    • Security: server-side permission checks, record-level access, exposed REST APIs, secrets in site properties
    • Quality: naming, dead code, exception handling, logging, documentation
    • Test plan: roles matrix, test cases per screen and action, data states, integration cases, regression list and what to automate with a BDD framework

    Every finding comes as Critical / Important / Minor with where it lives, why it matters and how to fix it. Includes a measure-first approach so you never optimize blindly.

    Built for low-code developers, tech leads and teams preparing code reviews, go-lives or certification.

    Uses only public best practices; it never asks for company data or credentials.

    En español: revisa tu app OutSystems (arquitectura, rendimiento, seguridad) y genera un plan de pruebas. Responde en tu idioma.

    Cannot open .oml or ODC files directly: it works from pasted logic, descriptions, screenshots or analysis-tool output. Does not claim performance numbers; it shows how to measure. Platform features should be verified against your version.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 6 days ago

    Permissions

    No special permissions declared or detected

    Listed6 days ago

    What's inside

    Frequently Asked Questions

    No. Paste the logic step by step, describe the screens or share screenshots of aggregates and flows. It tells you which parts are evidence and which are assumptions.

    Both. It asks which one you use and adapts the architecture and terminology.

    Share only what you are allowed to share. The skill asks for descriptions and tells you to remove names, data and secrets; it never requests credentials.

    No. It explains how to measure first and what change to make, so you can verify the improvement yourself.