simcon-toolkit
Put a working SIMCON example project on your machine: a workflow you run, read and change, with instruction files your own AI coding assistant already knows how to find.
uvx simcon-toolkit@latest init
It asks three questions: which template, what to call the folder, and whether you install with uv or pip. Press Enter through all three for the defaults. Or answer them up front and nothing is asked — only the template is required:
uvx simcon-toolkit@latest init my-study --template gate-study --package-manager uv
@latest is not decoration: without it uvx reuses whichever version it cached first.
See the templates, one line each:
uvx simcon-toolkit@latest init --list
Run it in a folder that already has files and it adds the project beside them. If a file it
would write already exists with different content, it stops and names the file before
changing anything; --force overwrites exactly those files and nothing else.
The installer needs no account. The project it writes does: it declares the licensed
cadmould SDK, and running it takes three browser sign-ins — one to install the SDK from
SIMCON's private index, one for your Cadmould licence, and one for the cloud. The project's
README walks through each, for the installer you chose.
Metadata
Release files for simcon-toolkit 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| simcon_toolkit-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / simcon_toolkit-0.1.0-py3-none-any.whl
| Download URL | simcon_toolkit-0.1.0-py3-none-any.whl |
|---|---|
| Size | 582.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0176e99a222a95ecea539f6b7c202edbf5062eed9f32ae361d02ddd45a56057c
|
|
BLAKE2b-256 checksum How to use checksums |
50f58f72b521418e1b2170d9484b125ec626ae190a57df27277a37c0ffb37a3d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.
Transparency logSecurity for simcon-toolkit 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for simcon_toolkit-0.1.0-py3-none-any.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.