3tears-agent-skills
Procedural memory for 3tears-based agents. Stores per-agent / per-user
labeled markdown procedures (body) and tool-surface modifications
(tool_additions, tool_restrictions) plus a prompt_mode enum
controlling how the body interacts with the consumer's base system prompt.
This package provides the schema + Collection layer:
agent_skills-- one row per skill (partition columnagent_id).agent_skill_invocations-- one row per skill load with synchronous outcome tracking populated by the consumer's post-LLM hook (partition columnagent_id; composite FK CASCADE on parent skill).- Two
BaseEntitysubclasses (AgentSkillEntity,AgentSkillInvocationEntity). - Two
BaseCollectionsubclasses exposing the public skill-registry API. - A trigger-maintained
search_vector(FTS forskill_listquery-filter ranking; NOT auto-load).
Agent tools and the per-turn composition renderer do not live here.
Migration registration
from threetears.agent.skills import register as register_skills
from threetears.core.data.migrations import MigrationRunner
runner = MigrationRunner()
register_skills(runner)
Migrations are agent-scoped and depend on conversations (the
invocation rows carry conversation_id -- ordering on apply, not an
FK constraint).
SkillRegistryClient Protocol -- why this package takes no ACL / tools deps
agent-memory (a sibling package) takes direct dependencies on
3tears-agent-acl and 3tears-agent-tools because its memory tools
need first-class ACL evaluator + tool-registry types in their public
surface. agent-skills deliberately diverges. The tool factories take
a thin SkillRegistryClient Protocol (three async methods,
acl_permits / list_skill_eligible_tools / get_tool_introspect,
plus a ConversationIdResolver / ActiveSkillProbe /
ActiveSkillSetter callable triple wired by the consumer) instead of
importing the ACL evaluator or the tool registry types directly.
The trade-off: callers must implement a small adapter (~10 lines over
their existing NamespaceCollection + ACL cache + in-process tool
registry), but agent-skills ships with zero hard deps beyond core
and langchain-core. The consumer wires this; tests mock it. The
ACL-via-evaluator approach targets the composition renderer, not the
tools surface.
Future sibling packages should follow whichever pattern their public surface demands -- direct deps when types are part of the contract, Protocol when the contract is method-shaped and the deps are incidental.
1 maintainer
Metadata
1 maintainer
Release files for 3tears-agent-skills 0.72.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 | |
|---|---|---|---|---|
| 3tears_agent_skills-0.72.0.tar.gz | 114.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| 3tears_agent_skills-0.72.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 180.0 kB
Release files / 3tears_agent_skills-0.72.0.tar.gz
| Download URL | 3tears_agent_skills-0.72.0.tar.gz |
|---|---|
| Size | 114.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
59b46f8a8e5b1423d15e1c186ff00e92c84b76f2273db623f0c934ed5eed399b
|
|
BLAKE2b-256 checksum How to use checksums |
7825e8f8b6da647541c765cb1e5f12dc34bb027ad54e18a944a0b0d00fb00334
|
| 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 Oct 20, 2026.
Transparency logRelease files / 3tears_agent_skills-0.72.0-py3-none-any.whl
| Download URL | 3tears_agent_skills-0.72.0-py3-none-any.whl |
|---|---|
| Size | 65.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b8bad199eb4937d43d0d474630e0acc3e8220c8c8cfaabd376378bdcf7eafba1
|
|
BLAKE2b-256 checksum How to use checksums |
3ec1366fe64120836f20e517d26769cf359dbb5fa077bc54092c2c9ce2f69ee8
|
| 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 Oct 20, 2026.
Transparency logSecurity for 3tears-agent-skills 0.72.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 2 files in this release have been uploaded with provenance metadata.
Attestation for 3tears_agent_skills-0.72.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 Oct 20, 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.
