tua-native-workflows

Route tasks through native apps, logged-in browser sessions, and existing user workflows.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/shalevamin/Tau_agent --skill tua-native-workflows-shalevamin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tua-native-workflows
Source: https://github.com/shalevamin/Tau_agent/tree/main/tau-agent-main/skills/tua-native-workflows
Command: npx skills add https://github.com/shalevamin/Tau_agent --skill tua-native-workflows-shalevamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the friction of setting up new API keys and integrations for every SaaS task by reusing the browser sessions, native apps, and authenticated state already present on the user's machine. ## Core Features & Use Cases - Session-First Routing: Prioritizes existing logged-in browser sessions and native integrations over requesting new vendor API keys. - Ordered Browser Automation: Applies a defined fallback chain of browser-use, computer-use, then extension relay for web tasks. - Document and SaaS Workflows: Routes docs, spreadsheets, and account-connected tasks through document skills and local apps like Word or Finder-managed files. - Use Case: A user asks to update a Google Doc proposal; the agent uses the already-authenticated browser session to edit the document directly instead of asking for a Google API key. ## Quick Start Use the tua-native-workflows skill to edit my open spreadsheet in the browser using my existing logged-in session.

Frequently Asked Questions about tua-native-workflows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate SaaS tasks without setting up API keys?

Reuse the authenticated browser sessions already present on the machine. The skill routes tasks through browser-use first, then computer-use, so existing logins handle authentication without requesting new vendor API keys.

How to automate browser tasks with an existing logged-in session?

Use the browser-use layer first, which operates on the current browser state. If that cannot complete the task, escalate to computer-use for real browser control, and only use extension relay when an already-open personal tab is required.

When should I use browser automation versus a service API?

Prefer browser or native automation when the machine is already logged into the target service. Request new API credentials only when the task genuinely requires an API-only capability that session-based automation cannot provide.

What is the fallback order for browser automation tools?

The default order is browser-use, then tua-computer-use, then extension relay or BrowserMCP-style session takeover. Extension relay is treated as a last resort for sessions the first two layers cannot complete.

Does this approach work for editing documents like Word or Google Docs?

Yes. Document tasks route through doc-coauthoring for structure, then document skills like docx or xlsx, then browser or local app automation via computer-use when the user's existing session is needed.