This release is a pre-release and may not be stable for production use.
Smartera AgentKit — CLI starter / MVP prototype
A new starter implementation, reconstructed from PROJECT_BRIEF_ORIGINAL.md (the original Oct 7 brief). The original deliverable was a spec, not working source. This starter is not a released PyPI package and does not claim to finish all 12 Codex tasks.
Requirements
Python 3.10+ with no runtime dependencies; for isolated execution use uv.
The optional npx launcher also requires Node.js 18+ with npm, and uvx on
PATH. It delegates to the same Python CLI without installing dependencies in
the target project or downloading uv automatically.
PyPI release setup and the pending development-preview publishing steps are in docs/PUBLISHING.md. Public installation remains pending.
Local install / build
# From this directory (an online index or populated dependency cache may be needed):
uvx --from . smartera-agentkit --help
uvx --from . smartera-agentkit init /path/to/my-project --dry-run
uvx --from . smartera-agentkit init /path/to/my-project --profile local-ai --project-name MyProject
uvx --from . smartera-agentkit doctor /path/to/my-project
uvx --from . smartera-agentkit list
The equivalent local npx commands use the built wheel (npm pack also builds it):
uv build --wheel
npx --yes --package . smartera-agentkit --help
npx --yes --package . smartera-agentkit init /path/to/my-project --dry-run
npx --yes --package . smartera-agentkit init /path/to/my-project --profile local-ai
npx --yes --package . smartera-agentkit doctor /path/to/my-project
Run these from this checkout. From another directory, replace . after
--from or --package with the absolute path to this checkout. Relative CLI
targets still resolve against the directory you run the command from. On
Windows PowerShell, use npx.cmd if execution policy blocks npx.ps1.
The npm package is private to prevent accidental publication. Neither the bare
npx smartera-agentkit nor the bare uvx smartera-agentkit is a verified public
installation path. First execution may need network access for build tooling;
offline execution requires a populated cache. The npm launcher follows
npm exec's local package support
and delegates isolation to uvx.
Windows PowerShell:
uvx --from . smartera-agentkit init "D:\Projects\My AI Project" --profile local-ai
To rebuild and verify both local artifacts from a disposable directory:
npm pack --pack-destination dist
python scripts/smoke_launchers.py
The smoke script removes PYTHONPATH and enables UTF-8 for redirected Python
output. For Unicode target paths in other redirected Windows sessions, set
$env:PYTHONUTF8 = '1' before launching. See docs/DEV_NOTES.md for measured
results and platform limitations.
Or, if testing locally with installed dependencies:
PYTHONPATH=src python -m smartera_agentkit init /tmp/try-agentkit --dry-run
PYTHONPATH=src python -m smartera_agentkit init /tmp/try-agentkit
python -m pytest -q
Implemented in this starter
init,add profile local-ai,add skill NAME,list,doctorand--dry-run/--json.- Bundled base templates, narrow skills, and a
local-aiprofile;AGENTS.mdkeeps all user text outside an owned marker block. - Preflight checking of conflicting existing files, explicit ownership manifest, hashes, no-op repeat init.
- Symlink-file and symlink-parent refusal for managed file paths.
- Individual same-directory atomic file replacement and simple best-effort rollback on normal exceptions.
- A limited frontmatter checker for bundled skills; full safe-YAML validation is still to be implemented.
Known gaps / roadmap
Not production hardened. The initial implementation is a starting point for Codex tasks T01–T08. It lacks a durable crash-recovery journal, OS-specific junction checks on Windows, durable lock across concurrent processes, full malicious-path testing, multi-platform CI, and verified uvx wheel smoke tests across platforms. It intentionally refuses unsupported update (T09, v0.2). Do not treat its preservation behavior as fully transactional in cases of power loss, concurrent processes, or abrupt termination. The master specification and acceptance criteria remain in PROJECT_BRIEF_ORIGINAL.md.
uvx smartera-agentkit ... by itself will work only after an authorized real package release to PyPI. Use uvx --from . smartera-agentkit ... until then. The target project does not need any AgentKit dependencies installed.
Metadata
Release files for smartera-agentkit 0.1.0.dev1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| smartera_agentkit-0.1.0.dev1.tar.gz | 18.6 kB | Without provenance | Details for smartera_agentkit-0.1.0.dev1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| smartera_agentkit-0.1.0.dev1-py3-none-any.whl | Python 3 | none | any | Details for smartera_agentkit-0.1.0.dev1-py3-none-any.whl |
Total release size: 40.4 kB
Release files / smartera_agentkit-0.1.0.dev1.tar.gz
| Download URL | smartera_agentkit-0.1.0.dev1.tar.gz |
|---|---|
| Size | 18.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c8b383d1ec1483be8ec0614e0cc58344d017ea4ad21c92b92beecf4acf485824
|
|
BLAKE2b-256 checksum How to use checksums |
b15678dc5ecd6e825bba0888154c3eb583dbaac4129f89132059909b2d605445
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / smartera_agentkit-0.1.0.dev1-py3-none-any.whl
| Download URL | smartera_agentkit-0.1.0.dev1-py3-none-any.whl |
|---|---|
| Size | 21.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4a083bb0837b08677d3371cabaf75d5dc0dbea49798b45465adfa5cb2c67fb91
|
|
BLAKE2b-256 checksum How to use checksums |
8e3a47c295730add9e7a0749c7862f0b4f6bf4367b83147725e901efa58df6db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for smartera-agentkit 0.1.0.dev1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.