# Build a Crypto Business Development Agent

Crypto exchange teams need a consistent way to identify and qualify token listing prospects. This skill structures discovery, scoring, wallet review, and approval-based outreach.

## Install

```bash
npx skillstore add sickn33/crypto-bd-agent
```

## Metadata

- Status: approved
- Slug: sickn33-crypto-bd-agent
- Skillstore revision: r2
- Version status: missing
- Tree hash: d0fccc9d24e567c0c94fcaf700029f952f2a32d9912b217c0942be698c5e8036
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/crypto-bd-agent
- Ref: f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
- 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: external\_commands, network
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-crypto-bd-agent
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-crypto-bd-agent/manifest

## Capabilities

- Guides multi-source token discovery across market, social, contract safety, and on-chain data.
- Defines a 100-point prospect score with weighted criteria and catalyst adjustments.
- Structures deployer wallet checks for funding sources, balances, transfers, identity, and risk flags.
- Maps prospects through a 10-stage listing pipeline with human approval before outreach.
- Explains model routing, source cost tracking, x402 payments, and ERC-8004 agent registration.
- Provides qualification thresholds for outreach, monitoring, wallet review, and rejection.

## Use Cases

- Standardize Listing Qualification: Create repeatable discovery, scoring, verification, and outreach stages for a cryptocurrency exchange.
- Design a Multi-Source Agent: Plan an agent that combines free and paid intelligence with cost-aware model routing.
- Review Token Risk: Assess contract signals and deployer wallet history before a listing prospect advances.

## Prompt Templates

### Create a Scoring Rubric

```
Create a 100-point token scoring rubric for [exchange type] using liquidity, market cap, volume, social activity, token age, and team transparency. Include score bands and actions.
```

### Evaluate a Token Prospect

```
Evaluate [token] on [chain] using these inputs: [metrics and sources]. Show the weighted score, catalyst adjustments, missing evidence, wallet checks, and recommended pipeline stage.
```

### Design the Listing Pipeline

```
Design a 10-stage listing pipeline for [exchange]. Define entry requirements, review owners, human approval gates, monitoring rules, and success metrics for every stage.
```

### Architect the Full Agent

```
Architect a multi-chain crypto business development agent for [exchange]. Include source selection, scoring, wallet forensics, model routing, x402 controls, ERC-8004 identity, audit logs, and approval boundaries.
```

## Limitations

- The skill provides patterns and criteria, not an executable scanner or complete integration.
- Data providers, protocol details, prices, and registration claims can change after publication.
- Token scores depend on accurate external data and do not guarantee project safety or listing success.
- The guidance does not replace legal, compliance, financial, or independent security review.

## Best Practices

- Verify contract addresses and require confirmation from at least two independent sources.
- Run wallet forensics on qualified prospects and require human approval before outreach or payments.
- Test model routing with representative cases and track the return from every paid data source.

## Anti Patterns

- Do not identify tokens by name alone or qualify prospects from a single source.
- Do not automate outreach or payments without explicit approval, verified endpoints, and spending controls.
- Do not treat token scores as trading advice, guaranteed safety, or a substitute for compliance review.

## Security Audit

- Audited at: 2026-07-23T22:00:11.472\+00:00
- Summary: All 11 static findings are false positives caused by Markdown fences, public reference links, safety guidance, and business analysis prose. No executable commands, credential collection, host reconnaissance, prompt injection, or malicious intent were found.

## Stats

- Views: 95
- Downloads: 10
- Favorites: 0
- Popularity score: 0