# Deploy GenLayer Oracle Markets

Creating an oracle market requires strict fields, source rules, and contract calls. This skill drafts, deploys, verifies, and monitors GenLayer Intelligent Oracle markets.

## Install

```bash
npx skillstore add internet-court/intelligent-oracle
```

## Metadata

- Status: approved
- Slug: internet-court-intelligent-oracle
- Skillstore revision: r1
- Version status: missing
- Tree hash: 9f945f15c3e0ffd85f049efab602fbbee1cb81599b5185e42fc0957005f761a4
- Author: internet-court
- GitHub username: internet-court
- License: MIT
- Repository: https://github.com/internet-court/internet-court-skill/tree/main/vendored/intelligent-oracle/intelligent-oracle
- Ref: 3f6e026a3363e0954ede7bef0cfe88d4475de137
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, env\_access
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/internet-court-intelligent-oracle
- Manifest: https://skillstore.pages.dev/api/skills/internet-court-intelligent-oracle/manifest

## Capabilities

- Drafts binary prediction market configurations with two outcomes.
- Validates required oracle fields and source-domain rules.
- Fetches the current factory pointer and RPC endpoint guidance.
- Shows how to deploy a market with genlayer-js.
- Verifies deployed oracle fields after creation.
- Monitors oracle status and explains resolution states.

## Use Cases

- Launch a Market Draft: Create a valid Yes or No market configuration from a plain-language event idea.
- Deploy a Test Oracle: Use Studionet deployment steps to create and verify a GenLayer oracle contract.
- Monitor Resolution Status: Check an oracle after launch and understand whether it is active, resolved, or in error.

## Prompt Templates

### Draft a Basic Market

```
Draft a Yes or No oracle market about [event]. Use a reliable public source and choose a future resolution date.
```

### Refine Market Rules

```
Tighten the resolution rules for this market: [market summary]. Keep exactly two outcomes and explain the source choice.
```

### Prepare for Deployment

```
Review this oracle market for deployment readiness. Check fields, source domains, and the earliest resolution date.
```

### Monitor and Resolve

```
Given oracle address [address], outline the checks to verify deployment, monitor status, and trigger resolution after the eligible date.
```

## Limitations

- Markets must resolve to exactly two outcomes.
- Resolution depends on public web evidence and validator consensus.
- Deployment requires network access and may require a wallet or key.
- The skill cannot guarantee the final oracle outcome.

## Best Practices

- Confirm every deployment or resolution write before executing it.
- Use fixed URLs only when the user provides stable pages.
- Log only transaction hashes, oracle addresses, and essential state fields.

## Anti Patterns

- Do not create markets with more than two possible outcomes.
- Do not mix resolution URLs and source domains in one config.
- Do not read private keys unless the user explicitly approves.

## Security Audit

- Audited at: 2026-07-21T03:21:21.545\+00:00
- Summary: Most external-command alerts are false positives caused by Markdown code delimiters and TypeScript syntax. The skill genuinely performs network access, handles private keys, can run a deployment command, and trusts remotely hosted configuration and source-policy data. Remote factory metadata can redirect a signed deployment unless the returned address and transaction are independently verified.

## Stats

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