← Back to Skills Marketplace
robert0812

Maton browse plan — API Gateway

by Rui Zhao · GitHub ↗ · v1.3.1 · MIT-0
cross-platform ⚠ suspicious
85
Downloads
1
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install maton-browse-plan
Description
Guides the user through installing the Maton API Plan — browsing capture Chrome extension from the Chrome Web Store (or building from source), then combines...
Usage Guidance
This skill appears to do what it says: it helps you install a Chrome extension and use the exported matonPlan together with the Maton API. Before installing, verify you trust the Maton extension and the GitHub repo (prefer the Chrome Web Store install). Be aware that: 1) you will need to provide MATON_API_KEY to let the skill call Maton services — consider a scoped/limited API key; 2) if you enable the local relay/native messaging, you (or scripts you run) will write a native messaging manifest to your browser/system (this is normal for native hosts but requires care); 3) the SKILL.md references MATON_RELAY_TOKEN for relay auth but that variable isn't declared by the skill metadata — if you plan to use the relay, confirm how the token is set and protected. If you have sensitive data in your browser history, the extension may request history/tabs access — review its permissions before consenting.
Capability Analysis
Type: OpenClaw Skill Name: maton-browse-plan Version: 1.3.1 The skill guides users to install a Chrome extension and a local relay to analyze browsing history for API integration suggestions. It instructs the agent to proactively poll a local HTTP endpoint (127.0.0.1:37191) and directs users to execute shell commands in SKILL.md to install a native messaging host. While these capabilities are aligned with the stated purpose of the 'Maton API Plan,' the combination of local network access, system-level configuration changes, and the processing of sensitive browsing data represents a high-risk profile without explicit evidence of malicious intent.
Capability Tags
requires-oauth-token
Capability Assessment
Purpose & Capability
The skill is an API-Gateway extension that ingests a matonPlan exported by a browser extension and uses the Maton API (MATON_API_KEY) to propose connector hints — requiring MATON_API_KEY is consistent with that purpose.
Instruction Scope
SKILL.md stays within scope: it guides installing the Chrome extension (store or build), obtaining the matonPlan via download or a local relay (http://127.0.0.1:37191 GET /latest or POST /ingest), and pairing that data with the API Gateway. Two notes: 1) it describes installing a native messaging host (writes a browser host manifest) which is expected for native relay scenarios but touches browser/system config (the scripts are user-run, not automatically executed by the platform); 2) it references MATON_RELAY_TOKEN (Bearer token for the relay) but that env var is not declared in requires.env.
Install Mechanism
This is instruction-only with no install spec and no bundled binaries. Build instructions use npm and local Chrome developer workflow; no downloads from untrusted URLs or automatic extract/install steps are present in the skill metadata.
Credentials
Only MATON_API_KEY is declared as required (reasonable for calling the Maton API). SKILL.md additionally mentions MATON_RELAY_TOKEN for local relay bearer auth but does not declare it — a minor inconsistency. Other environment variables mentioned (e.g., EXTENSION_ID used during user-run native-host install) are operational and reasonable.
Persistence & Privilege
The skill does not request always:true and does not ask to modify other skills or system settings autonomously. Native-host installation is described but is a user-invoked build/install step (not an automatic persistence mechanic of the skill).
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install maton-browse-plan
  3. After installation, invoke the skill by name or use /maton-browse-plan
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.3.1
Add explicit Chrome Web Store URL block; require agents to surface link on onboarding.
v1.2.4
- Improved installation and setup instructions for the Maton browse-capture Chrome extension, including new build and relay options. - Added clear guidance for pairing the Chrome extension with the local relay and handling relay-based and manual JSON ingestion. - Expanded details on extension permissions, native messaging, and troubleshooting native host setup. - Clarified how the skill periodically checks for new browsing data and proactively suggests Maton connector actions. - Emphasized best practices for fetching new data from the relay and preventing redundant prompts.
Metadata
Slug maton-browse-plan
Version 1.3.1
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 2
Frequently Asked Questions

What is Maton browse plan — API Gateway?

Guides the user through installing the Maton API Plan — browsing capture Chrome extension from the Chrome Web Store (or building from source), then combines... It is an AI Agent Skill for Claude Code / OpenClaw, with 85 downloads so far.

How do I install Maton browse plan — API Gateway?

Run "/install maton-browse-plan" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Maton browse plan — API Gateway free?

Yes, Maton browse plan — API Gateway is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Maton browse plan — API Gateway support?

Maton browse plan — API Gateway is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Maton browse plan — API Gateway?

It is built and maintained by Rui Zhao (@robert0812); the current version is v1.3.1.

💬 Comments