Google News Api
PassAudited by ClawScan on May 10, 2026.
Overview
The skill appears to be a straightforward BrowserAct-based Google News scraper, with the main caveat that it needs a BrowserAct API key and sends search queries to BrowserAct.
This skill is reasonable to install if you are comfortable using BrowserAct for news scraping. Set the BrowserAct API key through your environment when possible, avoid sharing sensitive search terms, and manually stop the script if a request appears to hang.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
You may be asked to provide a BrowserAct API key so the skill can run the news workflow under your BrowserAct account.
The skill requires a BrowserAct credential even though the registry metadata declares no primary credential or required environment variable. This is purpose-aligned for the BrowserAct integration, but users should treat the key as sensitive.
Before running, check the `BROWSERACT_API_KEY` environment variable. If not set, do not proceed with script execution; instead, request the API key from the user.
Prefer setting the key as an environment variable rather than pasting it into chat, and ensure the BrowserAct key has only the permissions you are comfortable granting.
BrowserAct will receive your news search terms and process the workflow request.
The script sends the search keywords, date range, result limit, and BrowserAct authorization header to BrowserAct's hosted workflow API. This is disclosed and aligned with the skill purpose, but it is still a third-party data flow.
API_BASE_URL = "https://api.browseract.com/v2/workflow" ... requests.post(f"{API_BASE_URL}/run-task-by-template", json=payload, headers=headers)Avoid using confidential or sensitive search terms unless you are comfortable sharing them with BrowserAct, and review BrowserAct's terms and privacy practices.
If the remote task never reaches a final state, the command could keep running until manually stopped.
The script polls the BrowserAct task status in an unbounded loop until the remote service reports finished, failed, or canceled. This is typical for async workflows but lacks an explicit timeout.
while True: ... status_res = requests.get(f"{API_BASE_URL}/get-task-status?task_id={task_id}", headers=headers).json() ... time.sleep(3)Stop the command if it runs longer than expected; the maintainer could add a maximum polling time or attempt limit.