ageri-sdk
Skill contract for the Ageri personal-AI platform.
Ageri is a self-hosted "chief of staff" agent system that runs 24/7, remembers across sessions, and coordinates specialist skills across every domain of your work. This package is the stable boundary every skill imports from — the abstract base classes, dataclasses, and helpers that define what a skill looks like to the Ageri runtime.
If you want to author an Ageri skill, install this package. If you want to run Ageri itself, see docs.ageri.ai/install.
Install
pip install ageri-sdk
Python 3.11+ required. No runtime dependencies — the SDK is pure ABCs +
dataclasses. Skills declare their own deps in their bundle's requirements.txt.
Minimal skill
from ageri_sdk import SkillBase, SkillResult, Task, OrchestratorContext
class HelloSkill(SkillBase):
name = "Hello"
description = "Greets the user."
version = "0.1.0"
intent_domain = "general"
async def handle(self, task: Task, ctx: OrchestratorContext) -> SkillResult:
return SkillResult(
status="done",
response=f"Hello, {ctx.user.display_name}!",
)
That's the whole contract. The runtime injects an OrchestratorContext with
proxies for memory, agents (LLMs), reply, browser/screen/input automation,
and so on. Your handle() does the work and returns a SkillResult.
What's in the package
SkillBase— abstract base every skill subclasses.Task— what the user asked for + routing metadata.SkillResult— what the skill produced (response + declared memory writes).OrchestratorContext— the only interface skills have to the outside world. Memory, agents, reply, user, agent identity, tools.- Proxy ABCs —
MemoryProxy,AgentProxy,ReplyProxy,BrowserProxy,ScreenProxy,InputProxy,FsProxy,NetworkProxy,ClipboardProxy,ProcessProxy. Skills code against these; the runtime supplies concrete implementations. - Helpers —
SkillCommand(slash-command metadata),ConfigField(declarable config schema),MessagingSkillBase(Slack/Telegram/Zalo-OA adapter base), vision-click + browser-automation primitives, and more.
Full API reference: https://docs.ageri.ai/sdk/.
Versioning
ageri-sdk follows semver. The major version bumps if the contract breaks
(adding a required method to SkillBase, changing a dataclass field that
already-shipped skills rely on, etc.). Minor versions add new capabilities;
patch versions are bugfixes.
Skill bundles declare their compatible SDK range via manifest_compat in
skill.json:
{
"manifest_compat": ">=0.5.0,<1.0.0"
}
The Ageri runtime refuses to load a skill whose manifest_compat doesn't
include the running SDK version.
License
MIT. See LICENSE.
The Ageri platform that consumes this SDK has its own license (see the main Ageri repo). The SDK is MIT so skill authors can freely build on it, publish skills under whatever license they choose, and integrate against Ageri without IP friction.
Metadata
Release files for ageri-sdk 0.5.0
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 |
|---|---|---|---|---|
| ageri_sdk-0.5.0.tar.gz | 35.1 kB | With provenance | Details for ageri_sdk-0.5.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ageri_sdk-0.5.0-py3-none-any.whl | Python 3 | none | any | Details for ageri_sdk-0.5.0-py3-none-any.whl |
Total release size: 68.8 kB
Release files / ageri_sdk-0.5.0.tar.gz
| Download URL | ageri_sdk-0.5.0.tar.gz |
|---|---|
| Size | 35.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
16efe827d1ec4c7fdcccf80d6d140190e678d23ab0b87f70ecde06cc739d98c3
|
|
BLAKE2b-256 checksum How to use checksums |
816f750a2e9242688e292aa3119e875bbb5dbc65ee89ca84ba8bb1f455a3bbbe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 15, 2026.
Transparency logRelease files / ageri_sdk-0.5.0-py3-none-any.whl
| Download URL | ageri_sdk-0.5.0-py3-none-any.whl |
|---|---|
| Size | 33.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fb7334eecfbbdffda909e56f99b3cde97dbe7de0a7402280fb8bf6aa669f2155
|
|
BLAKE2b-256 checksum How to use checksums |
1d1f3da9608205433c812316da0935a90addf753897d8dbcb7b0ffcc7f73e47a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 15, 2026.
Transparency logSecurity for ageri-sdk 0.5.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
Both files in this release have been uploaded with provenance metadata.
Attestation for ageri_sdk-0.5.0.tar.gz
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 May 15, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.