windy-drops (Python SDK)

Python SDK + CLI for authoring and publishing Windy Drops.

Not published yet. This package is not on PyPI as of 2026-08-10; the command below is what the install will be once it ships. Until then, run the CLI from a checkout of sneakyfree/windy-drops.

pip install windy-drops
windy-drops --help

Commands

Commands marked future-strand exit code 2 with a clear message until that strand lands.

Scaffold

windy-drops new --type control-panel-template ./my-dashboard
# ✓ scaffolded control-panel-template drop at /.../my-dashboard
# Next steps:
#   1. Edit /.../my-dashboard/SKILL.md (set author + id)
#   2. windy-drops validate /.../my-dashboard
#   3. windy-drops publish /.../my-dashboard

The 6 v1 reserved drop types each ship a starter scaffold:

• control-panel-template
• skill
• tool
• theme
• voice-pack
• workflow

Library API

from windy_drops import scaffold

result = scaffold(type="skill", path="./my-skill")
print(result.target_dir, result.files_copied)

Parity with the TypeScript SDK

The TypeScript sibling (windy-drops-sdk, also unpublished) has the same CLI surface. A drop scaffolded by one is byte-identical to one scaffolded by the other; a drop published by one is indistinguishable to the registry. Cross-SDK byte-identity is enforced by the WD-11 conformance harness.

Strand reference

This package is owned by strands WD-4..WD-10 in docs/DNA_STRAND_MASTER_PLAN.md. Each strand owns one subcommand (or related set).

License

MIT

Getting a token

new, validate, sign and bundle need nothing. publish and withdraw need a token, and this is where most first-time authors stop.

The registry accepts either identity:

Pass it per-command or export it:

windy-drops publish ./my-drop --token <jwt>
# or
export WINDY_REGISTRY_TOKEN=<jwt>

There is no windy-drops login yet, and nothing reads a token out of ~/.windy/credentials.json — that file is only consulted for the signing key (eternitas.private_key), which is a different thing. Publishing a drop whose manifest declares an author passport additionally requires that the token carry that same passport; you cannot publish as someone else.