agentskills-testing
Conformance suite and test doubles for Agent Skills providers.
SkillProvider is an abstract base class, which enforces that five methods exist
and nothing whatsoever about what they do. The requirements that actually matter
are the ones an ABC cannot express: that an unknown skill ID raises
SkillNotFoundError rather than returning {}, that ../../etc/passwd is
refused rather than resolved, and that a provider advertising resource listing
can actually list. This package turns those into tests you inherit.
pip install agentskills-testing
Conformance suite
Subclass ProviderConformanceSuite, supply a provider fixture, and pytest
collects the entire provider contract against your implementation:
import pytest
from agentskills_testing import ProviderConformanceSuite
from my_package import MyProvider
class TestMyProvider(ProviderConformanceSuite):
@pytest.fixture
def provider(self):
return MyProvider(...)
Fixture contract
The provider fixture must expose exactly one skill:
| id | conformance-skill |
| metadata | name == "conformance-skill", plus a non-empty description |
| body | non-empty markdown |
references/ |
notes.md containing b"# Notes\n\nA reference document.\n" |
scripts/ |
run.sh containing b"#!/bin/sh\necho conformance\n" |
assets/ |
diagram.svg containing b"<svg></svg>\n" |
It must not define a skill called no-such-skill-anywhere, or any resource
called no-such-resource.txt.
Every name and byte string above is exported as a constant (SKILL_ID,
REFERENCE_NAME, REFERENCE_BYTES, and so on), so a fixture can be built from
them rather than from copied literals. CONTRACT holds the same description as
a string, and is what the default fixture prints when you forget to override it.
What it checks
- Metadata carries
nameand a non-emptydescription, and does not carry the body — a metadata call that includes the body has already spent the tokens progressive disclosure exists to save. - Metadata is not shared mutable state: one caller mutating the returned dict must not affect the next.
- Repeated reads agree. A provider that streams without buffering passes the first read and returns empty on the second; caching bugs look the same.
- Each resource getter returns exact
bytes, notstr. A resource may be a PNG, and decoding on the way out makes that unreachable. - Unknown skills raise
SkillNotFoundError; unknown resources raiseResourceNotFoundError. list_resources()agrees withsupports_resource_listing. Callers branch on that flag, so a provider whose flag and behaviour disagree breaks them whichever way it lies.discover()agrees withsupports_discovery, and everything it reports can actually be read.register_all()validates the whole list, so one phantom ID fails the entire registration.- Traversal identifiers are refused — parent traversal, absolute paths, Windows separators, percent-encoded traversal, and embedded NUL bytes, as both skill IDs and resource names. These are not opt-out.
- Concurrent reads through a single instance return consistent content, which
catches per-call state stored on
self.
Size limits
ContentLimitConformanceSuite is separate and opt-in. A size limit is not part
of the universal contract — an in-memory provider has no external source to
bound, and demanding one would assert a filesystem's constraints against a dict.
It is required of any provider that reads bytes it did not author: from
disk, from a network, from anywhere a caller can grow without asking.
from agentskills_testing import ContentLimitConformanceSuite
class TestMyProviderLimits(ContentLimitConformanceSuite):
@pytest.fixture
def limited_provider(self):
return MyProvider(..., max_bytes=8)
The fixture holds the same skill, with a limit small enough that the skill exceeds it.
Test doubles
InMemorySkillProvider is a real, spec-compliant provider backed by a dict — it
passes the conformance suite above. Prefer it to an AsyncMock: a mock agrees
with whatever the test asserts, including the assertions that are wrong.
from agentskills_core import SkillRegistry
from agentskills_testing import InMemorySkillProvider, build_skill
provider = InMemorySkillProvider(
{
"incident-response": build_skill(
"incident-response",
description="Diagnose and mitigate a production incident.",
body="# Incident Response\n\nPage the on-call engineer.\n",
references={"severity-levels.md": b"SEV1 is customer-visible.\n"},
)
}
)
registry = SkillRegistry()
await registry.register_all(provider)
A string value is taken as the body, for the common case where the content does not matter:
provider = InMemorySkillProvider({"a": "body of a", "b": "body of b"})
provider.add("c") # a default skill named "c"
build_skill() produces frontmatter that passes validate_skill(), so a test
that does not care about metadata does not have to invent any.
render_skill_md(skill) renders one back to SKILL.md text, which is how you
populate a temporary directory for the filesystem provider.
To emulate a backend that cannot enumerate — a static HTTP host without a
manifest, for instance — pass supports_resource_listing=False, or
supports_discovery=False, or both.
Fixtures
Installing the package registers a pytest plugin, so these are available with no
import and no conftest.py entry:
| Fixture | What you get |
|---|---|
sample_skill |
An InMemorySkill with one reference, one script, and one asset |
skill_provider |
An InMemorySkillProvider serving sample_skill |
skill_registry |
A SkillRegistry with that skill already registered |
async def test_my_agent(skill_registry):
catalog = await skill_registry.get_skills_catalog()
assert "incident-response" in catalog
License
MIT — see LICENSE.
Part of the Agent Skills SDK.
Metadata
Release files for agentskills-testing 0.6.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 |
|---|---|---|---|---|
| agentskills_testing-0.6.0.tar.gz | 10.9 kB | With provenance | Details for agentskills_testing-0.6.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agentskills_testing-0.6.0-py3-none-any.whl | Python 3 | none | any | Details for agentskills_testing-0.6.0-py3-none-any.whl |
Total release size: 23.4 kB
Release files / agentskills_testing-0.6.0.tar.gz
| Download URL | agentskills_testing-0.6.0.tar.gz |
|---|---|
| Size | 10.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
02b460e770cb8e8724de1566cc2c70a598acb10c42f5edbc053518bdf199e082
|
|
BLAKE2b-256 checksum How to use checksums |
868669e5b83656dcce503a12252cb38ab1e3b6822421ccd414cef1b33976d0a9
|
| 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 6, 2026.
Transparency logRelease files / agentskills_testing-0.6.0-py3-none-any.whl
| Download URL | agentskills_testing-0.6.0-py3-none-any.whl |
|---|---|
| Size | 12.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
befbc6100eafb035d764fdd3d06fad78e9a3858145da6c06b187acdce31198e0
|
|
BLAKE2b-256 checksum How to use checksums |
02c6bdbb516bf665dec74faebeab453d5d2982865c7098d5268d958d4f116a6c
|
| 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 6, 2026.
Transparency logSecurity for agentskills-testing 0.6.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 agentskills_testing-0.6.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 6, 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.