mastro-hq/mastro-connect / skills/mastro
mastro
VerifiedCore conventions for the mastro CLI — connectors that let agents drive web apps through the apps' own APIs, replayed with the user's own browser session. Read this before using any mastro provider command, or when the user mentions mastro, asks to log in to a connector, or a mastro command fails with an auth error.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.9 KB |
SKILL.md
View on GitHub---
name: mastro
description: Core conventions for the mastro CLI — connectors that let agents drive web apps through the apps' own APIs, replayed with the user's own browser session. Read this before using any mastro provider command, or when the user mentions mastro, asks to log in to a connector, or a mastro command fails with an auth error.
---
# mastro — connectors for web apps
`mastro` replays a captured browser session against a web app's own API, so
you can search/read/act on apps for the user without driving a browser UI.
Each app is
a **provider** (e.g. `hackernews`) and each provider exposes subcommands
generated from its spec.
If `mastro` is not on PATH, invoke every command as `npx -y mastro-connect`
instead (e.g. `npx -y mastro-connect hackernews top --json`).
## The session model
- Credentials are captured **once** from the user's own browser via the
mastro extension: `mastro login <provider>`. This is interactive — the user
must be logged in to the site. Never type credentials yourself.
- Check state before calling a provider:
```bash
mastro status --json # { "<provider>": { "state": "active" | ... } }
```
If the provider is missing or not `active`, ask the user to run
`mastro login <provider>`, then retry.
- `mastro logout <provider>` forgets a stored session.
## Conventions
- `mastro providers --json` lists installed connectors.
- `mastro <provider> --help` lists that provider's commands;
`mastro <provider> <command> --help` lists flags. Both are generated from
the provider's spec — trust `--help` over any memorized flag list.
- **Always pass `--json`** when you consume output; the default output is for
humans.
- Exit code 2 means you misused a flag (read the message); 1 is a runtime
failure. An auth error usually means the session expired — re-login.
- Providers carry rate limits. If a command reports throttling, slow down;
don't loop-retry.
- Commands that change real-world state (orders, listings) support
`--dry-run`. Dry-run first and confirm with the user before anything that
spends money or posts publicly.
## Per-provider skills
Detailed playbooks ship with each provider. Install them next to this skill:
```bash
mastro skills add <provider> # all of a provider's skills
mastro skills add <provider>/<skill> # one skill
```
## Missing a connector?
- Connectors from the community catalog install themselves the first time
you call them (a one-line "installed …" notice — on stderr under `--json`,
so the JSON stays clean). `mastro providers --json`
shows what's installed; `mastro providers available --json` shows the
catalog. Other repos:
`--repo <owner>/<repo>` (private repos use `GITHUB_TOKEN` or the user's
`gh` login).
- No connector exists for the app? The `mastro-author` skill builds one
(`mastro skills add mastro-author`). Ask the user before starting — it needs
them logged in and clicking through the app once.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |