Buildertrend

This skill is broadly coherent with its stated purpose (automating Buildertrend via OpenClaw's Browser Relay), but review the following before installing: - Review playbooks that handle financial operations (POs, invoices, change orders). Ensure the UI/agent interaction includes explicit user approvals as claimed, and test on a non-production Buildertrend account first. - The skill runs JavaScript in your browser context (evaluate steps). That is necessary for UI automation but also means the agent can read or manipulate page contents — only attach the Browser Relay tab when you explicitly trust the agent and the skill files. Do not attach tabs with other sensitive sites while testing. - README has some contradictory statements (e.g., 'no data extraction' vs many playbooks that extract budget/client data). Expect data extraction for reporting/playbook outputs — confirm where that extracted data is stored or sent (memory, other agents, Google Drive) and that downstream integrations require their own credentials. - Verify how integrations to QuickBooks/Google Drive are configured. The skill does not request QBO or Drive credentials, so ensure any necessary OAuth tokens are provided securely via the platform or separate agent, not implicitly by this skill. - Because JS snippets use broad selectors in places, run the playbooks in a sandbox/test job first to validate they interact with the intended elements and to avoid accidental clicks on unrelated UI elements. If you want higher assurance, ask the author for: (1) a clear description of where extracted data is stored/transmitted, (2) proof that every financial action includes an explicit user confirmation step, and (3) sanitized examples of the browser-evaluate payloads the agent will execute during key playbooks.