autopilot-data-seller

Conversational seller-authoring policy for DS-first Data Market listings in OpenAgents.

390 stars

Best use case

autopilot-data-seller is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Conversational seller-authoring policy for DS-first Data Market listings in OpenAgents.

Teams using autopilot-data-seller should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/autopilot-data-seller/SKILL.md --create-dirs "https://raw.githubusercontent.com/OpenAgentsInc/openagents/main/skills/autopilot-data-seller/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/autopilot-data-seller/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How autopilot-data-seller Compares

Feature / Agentautopilot-data-sellerStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Conversational seller-authoring policy for DS-first Data Market listings in OpenAgents.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Autopilot Data Seller

Use this skill for turns coming from the dedicated `Data Seller` pane.

## Objective

- Gather only the missing facts required to describe a saleable data asset.
- Normalize conversational seller intent into structured draft fields.
- Keep truth aligned with the local draft, preview posture, and published kernel state.
- Keep DS listing/offer publication truth distinct from later DS-DVM fulfillment truth.
- Never imply a listing is live until preview and explicit confirmation have happened.

## Required Tools

Prefer only these tools for seller flows:

- `openagents.data_market.seller_status`
- `openagents.data_market.draft_asset`
- `openagents.data_market.preview_asset`
- `openagents.data_market.publish_asset`
- `openagents.data_market.draft_grant`
- `openagents.data_market.preview_grant`
- `openagents.data_market.publish_grant`
- `openagents.data_market.prepare_delivery`
- `openagents.data_market.issue_delivery`
- `openagents.data_market.revoke_grant`
- `openagents.data_market.snapshot`

Use generic `openagents.pane.*` tools only for inspection or recovery when a
typed data-market tool cannot provide the needed truth.

## Operating Contract

1. Start from seller truth, not prose confidence.
2. Ask only for missing or contradictory listing facts.
3. Normalize what the seller says into concrete draft fields.
4. Surface readiness blockers clearly and concisely.
5. Preview before publish every time.
6. Require explicit seller confirmation before publish.
7. Read back published state after mutation.
8. For paid targeted DS-DVM requests, prepare delivery explicitly, then issue delivery so kernel truth exists before the DS-DVM result is published.
9. Revoke or expire access only through the typed revocation tool, and only after the seller has stated the intended reason and explicitly confirmed the mutation.

## Safety Rules

- Do not claim a listing is live unless publish succeeded and the published id is visible.
- Do not invent provenance, digest, price, policy, or delivery posture.
- Do not silently widen permissions beyond what the seller confirmed.
- Do not skip preview because the request "sounds obvious."
- Do not claim delivery succeeded unless the `DeliveryBundle` exists and the linked DS-DVM result publish completed.
- Do not claim access has been revoked or expired unless the `RevocationReceipt` exists and the grant/delivery read-back reflects the resulting terminal state.

Related Skills

autopilot-pane-control

390
from OpenAgentsInc/openagents

OpenAgents desktop pane and CAD control for Codex via openagents.* tool calls.

autopilot-data-seller-cli

390
from OpenAgentsInc/openagents

Shell-first OpenAgents DS-first Data Market packaging and publication workflow using the deterministic packaging helper, autopilotctl, and the no-window headless runtime.

autopilot-data-market-control

390
from OpenAgentsInc/openagents

Typed OpenAgents DS-first Data Market tool contract for seller publication and market read-back.

autopilot-cad-builder

390
from OpenAgentsInc/openagents

Deterministic CAD build orchestration for Autopilot Chat using openagents CAD and pane tools, including week-1 gripper flow.

neutronpay

390
from OpenAgentsInc/openagents

Neutronpay MCP and SDK workflows for Lightning, stablecoin, and fiat payments.

moneydevkit

390
from OpenAgentsInc/openagents

Money Dev Kit workflows for Lightning checkout and agent wallets.

mezo

390
from OpenAgentsInc/openagents

Mezo integration workflows for apps, autonomous agents, and Mezo Earn operations.

maestro

390
from OpenAgentsInc/openagents

Maestro Symphony blockchain query operations for OpenAgents agents, including tip freshness checks, address/UTXO/runes queries, and production-safe troubleshooting against deployed Symphony API endpoints.

l402

390
from OpenAgentsInc/openagents

L402 agent commerce workflows with lnd, lnget, scoped macaroons, aperture, and MCP.

charms

390
from OpenAgentsInc/openagents

Charms workflows for Bitcoin app contracts, spell proving, and UTXO asset operations.

cast

390
from OpenAgentsInc/openagents

Charms CAST DEX workflows for order creation, cancellation/replacement, partial fulfillment, signing, and Bitcoin transaction verification.

blink

390
from OpenAgentsInc/openagents

Bitcoin Lightning wallet for agents — balances, invoices, payments, BTC/USD swaps, QR codes, price conversion, and transaction history via the Blink API. All output is JSON.