Brightdata Core Workflow BSAFE
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-08What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: brightdata-core-workflow-b description: 'Analyze and operate the Bright Data Web Scraper API async snapshot lifecycle with terminal-state and delivery controls. Use when collecting an approved batch, polling a snapshot, or downloading large structured results. Trigger with: "run a Bright Data dataset job", "poll a Bright Data snapshot", "download Web Scraper API results".' allowed-tools: Read, Grep, Write, Edit, Bash(curl:*) version: 2.0.0 argument-hint: "[dataset-run-manifest]" model: inherit effort: high license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - web-data - bright-data - core-workflow-b - operations compatibility: 'Requires an approved Bright Data account or offline fixtures, current Bright Data documentation, and an authorized public-data collection purpose' --- # Bright Data Async Snapshot Pipeline ## Overview Implement the documented trigger, progress, and download lifecycle as a state machine. Keep dataset identifiers and approved inputs separate from the API key; cap polling, validate terminal states, and stream results rather than loading arbitrary payloads into memory. ## Prerequisites - A reviewed dataset ID and approved public input manifest - A named-user Bright Data API key in the runtime secret manager - A retention, schema, maximum-record, and maximum-byte policy ## Instructions ### Step 1: Validate the manifest Read the requested dataset/inputs and Grep for disallowed target classes or fields. Hash the approved input manifest before submission. ### Step 2: Trigger once Use Bash(curl:*) only against the fixed Bright Data API origin with the API key as a Bearer header. ```bash curl --fail-with-body --request POST \ 'https://api.brightdata.com/datasets/v3/trigger?dataset_id=DATASET_ID' \ --header "Authorization: Bearer $BRIGHTDATA_API_KEY" \ --header 'Content-Type: application/json' \ --data-binary @approved-inputs.json ``` ### Step 3: Poll deliberately Persist the returned `snapshot_id`; poll `GET /datasets/v3/progress/SNAPSHOT_ID` with bounded attempts and provider-directed delay. Handle `ready`, `failed`, empty, expired, and still-building states explicitly. ### Step 4: Download and verify Stream `GET /datasets/v3/snapshot/SNAPSHOT_ID` in the approved format. Use parts for large results, hold format/compression parameters constant, enforce byte/record ceilings, and validate the schema before promotion. ## Tool Discipline Use Read and Grep for policy and schema checks. Use Write and Edit only for the manifest, state machine, tests, and redacted receipt. Use Bash(curl:*) for fixed-origin Bright Data API calls after authorization; never print the Bearer value or raw result data. ## Output - Input-manifest hash and snapshot identifier - Bounded state-transition log without target data or credentials - Schema/size validation and a promoted-or-quarantined result ## Examples Submit a small approved URL batch, record the returned snapshot ID, poll until `ready`, and stream JSON to quarantine. Reject a response whose schema, record count, or byte count exceeds the manifest even if the provider marks it ready. ## Error Handling | Failure | Meaning | Response | |---------|---------|----------| | 400 validation response | Dataset ID or input shape is invalid | Correct the manifest; do not retry unchanged input | | 429 or too many jobs | Tenant or dataset concurrency is exhausted | Pause new triggers and wait for owned jobs | | Snapshot expired or empty | Result cannot be promoted | Trigger a newly approved run or investigate inputs | ## Resources - [Web Scraper API asynchronous requests](https://docs.brightdata.com/api-reference/rest-api/scraper/asynchronous-requests) - [Download snapshot](https://docs.brightdata.com/api-reference/scrapers/delivery-apis/download-snapshot) - [Scraper async requests guide](https://docs.brightdata.com/products/scrapers/scrapers-library/async-requests) - [Authentication and API keys](https://docs.brightdata.com/api-reference/authentication)
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__brightdata-core-workflow-b.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 4f83675ca38a | SAFE | B | 89 | first audit |
Questions
What does the Brightdata Core Workflow B skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Brightdata Core Workflow B safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Brightdata Core Workflow B access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-08. The repository is watched, and a new audit runs when it changes — this is the first audit.