# Structure Compliant Data Brokerage Deals

Data brokerage teams need structured methods to match parties, verify eligibility, and protect fees. This skill provides workflows, checklists, and document outlines for each stage.

## Install

```bash
npx skillstore add 图灵数盟/dhturing-data-broker-expert
```

## Metadata

- Status: approved
- Slug: dhturing-data-broker-expert
- Skillstore revision: r1
- Version status: missing
- Tree hash: 6edc22828773314f34bd275cad48775ae0c281b0fe8015c1ffb78f5e52b388c4
- Author: 图灵数盟
- GitHub username: dhturing
- License: MIT
- Repository: https://github.com/dhturing/turing-data-experts/tree/9c58ffa97ec5b760befef6f910eb23107cdcdbf4/skills/data-broker-expert
- Ref: 50b73f83991cf073cbdf3f5afad2bbac71dd3bae
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem, external\_commands, network
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/dhturing-data-broker-expert
- Manifest: https://skillstore.pages.dev/api/skills/dhturing-data-broker-expert/manifest

## Capabilities

- Compares matching, agency, and sponsorship brokerage models by responsibilities, fees, and risk.
- Structures seller resource pools and buyer requirement lists.
- Creates bilateral verification checklists covering ownership, quality, compliance, eligibility, payment capacity, and intended use.
- Drafts transaction plans, intermediary agreement outlines, sponsorship letter outlines, and commission records.
- Applies a ten-stage workflow from brokerage positioning through ecosystem maintenance.
- Reviews engagements against qualification, documentation, delivery, commission, and role-boundary controls.

## Use Cases

- Select a Brokerage Model: Compare matching, agency, and sponsorship roles, then define responsibilities, services, fees, and required qualifications.
- Verify a Proposed Transaction: Build separate evidence checklists for the seller, buyer, data product, intended use, and payment readiness.
- Protect Brokerage Revenue: Outline commission terms, participation records, anti-circumvention clauses, delivery checkpoints, and settlement controls.

## Prompt Templates

### Choose My Brokerage Role

```
We serve [industry] clients in [region]. Compare matching, agency, and sponsorship models for us. Recommend one role with responsibilities, qualifications, fees, and risks.
```

### Create a Verification Checklist

```
Prepare a bilateral verification checklist for this transaction: [details]. Separate seller evidence, buyer evidence, data quality, ownership, compliance, intended use, and payment checks.
```

### Design a Brokerage Plan

```
Design a brokerage plan for [transaction]. Include matching logic, responsibilities, milestones, negotiation points, delivery controls, commission terms, anti-circumvention protections, and unresolved risks.
```

### Audit the Full Operating Process

```
Review our brokerage process and documents: [materials]. Map gaps against the ten-stage workflow, prioritize risks, assign owners, and propose measurable acceptance criteria.
```

## Limitations

- It cannot independently verify ownership, identity, payment capacity, data quality, or regulatory status.
- It does not replace legal counsel, regulators, licensed exchanges, or qualified sponsorship institutions.
- Its policy references and fee ranges require confirmation for the relevant date and jurisdiction.
- Generated agreements and sponsorship materials are drafts and require authorized professional review.

## Best Practices

- Confirm current laws, exchange rules, qualifications, and fee assumptions before using any recommendation.
- Keep dated evidence for seller claims, buyer eligibility, intended use, negotiations, delivery, acceptance, and commission triggers.
- Separate advisory drafts from official opinions and obtain authorized legal, compliance, and sponsorship approval.

## Anti Patterns

- Do not treat a supplier statement as proof of ownership, quality, legality, or authorization.
- Do not issue guarantees, legal conclusions, or sponsorship opinions without authority and documented review.
- Do not begin delivery while buyer purpose, contract terms, security controls, or payment conditions remain unclear.

## Security Audit

- Audited at: 2026-09-27T03:14:02.295\+00:00
- Summary: All 12 static findings are false positives caused by installation documentation, Markdown formatting, public links, and multilingual text entropy. The reviewed files contain guidance and reference material without executable commands, hidden-file operations, obfuscated payloads, or prompt injection.

## Stats

- Views: 0
- Downloads: 1
- Favorites: 0
- Popularity score: 0