draft: add SkillStore abstraction

[tstadel]

Related Issues

• Very rough idea of adding a SkillStore abstraction that facilitates loading skills not only from disk (e.g. on platform we want to load it from rds)

Proposed Changes:

How did you test it?

Notes for the reviewer

Checklist

• I have read the contributors guidelines and the code of conduct.
• I have updated the related issue with new insights and changes.
• I have added unit tests and updated the docstrings.
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test: and added ! in case the PR includes breaking changes.
• I have documented my code.
• I have added a release note file, following the contributors guidelines.
• I have run pre-commit hooks and fixed any issue.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
haystack-docs	Ignored	Preview	Jun 3, 2026 3:29pm

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
haystack/dataclasses
skill_meta.py
haystack/skill_stores/file_system
__init__.py
skill_store.py					34, 82, 97, 107, 120
haystack/skill_stores/types
__init__.py
protocol.py
haystack/tools
__init__.py
haystack/tools/skills
__init__.py
skill_toolset.py					123-124
Project Total

This report was generated by python-coverage-comment-action

[sjrl]

Could you make a version of this SkillStore using a db (like the one to be used in platform) to make sure this protocol definition works for at least two different backends?

[sjrl]

Merging and finishing up in the target branch