---
title: "skills vs statewave"
type: "comparison"
canonical_url: "https://www.graphcanon.com/compare/qdrant-skills-vs-smaramwbc-statewave"
tools: ["qdrant-skills", "smaramwbc-statewave"]
---

# skills vs statewave

*GraphCanon updated Aug 6, 2026*

## Verdict

Pick skills if skills for Qdrant vector search provide tools for scaling, performance tuning, model migration, and more; pick statewave if statewave focuses on reproducibility and provenance in memory management for AI agents, using Postgres plus pgvector for self-hosted operations rather than relying on query-time retrieval.

[skills](https://skills.qdrant.tech) reports 220 GitHub stars, 26 forks, and 17 open issues, last pushed Aug 5, 2026. [statewave](https://statewave.ai) has 289 stars, 22 forks, and 14 open issues, last pushed Jul 30, 2026. Figures are from public GitHub metadata via [skills's repository](https://github.com/qdrant/skills) and [statewave's repository](https://github.com/smaramwbc/statewave).

| | [skills](/tools/qdrant-skills.md) | [statewave](/tools/smaramwbc-statewave.md) |
| --- | --- | --- |
| Tagline | Agent skills for Qdrant vector search, including scaling, performance optimization, and model migration. | Open-source memory runtime for AI agents |
| Stars | 220 | 289 |
| Forks | 26 | 22 |
| Open issues | 17 | 14 |
| Language | Shell | Python |
| Adopt for | Skills for Qdrant vector search provide tools for scaling, performance tuning, model migration, and more. | Statewave focuses on reproducibility and provenance in memory management for AI agents, using Postgres plus pgvector for self-hosted operations rather than relying on query-time retrieval. |
| Persona | - | - |
| Runtime | - | - |
| License | Apache-2.0 | Apache-2.0 |
| Categories | AI Agents, Vector Databases | AI Agents, Vector Databases |

## Trust and health

_Sourced signals - not a safety guarantee. No winner column._

| | [skills](/tools/qdrant-skills.md) | [statewave](/tools/smaramwbc-statewave.md) |
| --- | --- | --- |
| Days since push | 0d | 1d |
| Open issues (now) | 17 | 14 |
| Owner type | Organization | User |
| Full report | [trust report](/tools/qdrant-skills/trust.md) | [trust report](/tools/smaramwbc-statewave/trust.md) |

## Decision facts: skills

- **Adopt for:** Skills for Qdrant vector search provide tools for scaling, performance tuning, model migration, and more.

## Decision facts: statewave

- **Adopt for:** Statewave focuses on reproducibility and provenance in memory management for AI agents, using Postgres plus pgvector for self-hosted operations rather than relying on query-time retrieval.

## Choose when

### Choose skills if…

- skills is primarily Shell; statewave is Python.
- Tags unique to skills: agent-skills, embeddings, hybrid-search, monitoring.
- Need help with optimizing or expanding your Qdrant deployment beyond millions of vectors

### Choose statewave if…

- statewave is primarily Python; skills is Shell.
- Tags unique to statewave: agent-memory, llm, memory, pgvector.
- statewave ships Docker support for self-hosted deployment.
- Use when needing reproducible and documented context bundles to ensure consistent agent performance over time, as Statewave's design specifically supports provenance tagging for each context bundle.

## When NOT to use skills

- Your Qdrant instance is performing well with fewer than a million vectors
- Looking for help beyond vector search, such as database type selection or general AI agent tasks
- Seeking advice on non-Qdrant-specific issues like cloud infrastructure setup outside of integration

## When NOT to use statewave

- Avoid if your application cannot leverage or benefit from a self-hosted memory runtime setup specifically using Postgres and pgvector.
- Not suitable for cases where query-time document retrieval is preferred over maintaining provenance-tagged, static context bundles.

## Common questions

### What is the difference between skills and statewave?

skills: Agent skills for Qdrant vector search, including scaling, performance optimization, and model migration.. statewave: Open-source memory runtime for AI agents. See the comparison table for live GitHub stats and shared categories.

### When should I choose skills over statewave?

Choose skills over statewave when skills is primarily Shell; statewave is Python; Tags unique to skills: agent-skills, embeddings, hybrid-search, monitoring; Need help with optimizing or expanding your Qdrant deployment beyond millions of vectors.

### When should I choose statewave over skills?

Choose statewave over skills when statewave is primarily Python; skills is Shell; Tags unique to statewave: agent-memory, llm, memory, pgvector; statewave ships Docker support for self-hosted deployment; Use when needing reproducible and documented context bundles to ensure consistent agent performance over time, as Statewave's design specifically supports provenance tagging for each context bundle.

### When should I avoid skills?

Your Qdrant instance is performing well with fewer than a million vectors Looking for help beyond vector search, such as database type selection or general AI agent tasks Seeking advice on non-Qdrant-specific issues like cloud infrastructure setup outside of integration

### When should I avoid statewave?

Avoid if your application cannot leverage or benefit from a self-hosted memory runtime setup specifically using Postgres and pgvector. Not suitable for cases where query-time document retrieval is preferred over maintaining provenance-tagged, static context bundles.

### Is skills or statewave more popular on GitHub?

statewave has more GitHub stars (289 vs 220). Stars measure visibility, not whether either tool fits your constraints.

### Are skills and statewave open source?

Yes - both are open-source projects on GitHub (skills: Apache-2.0, statewave: Apache-2.0).

### Where can I find alternatives to skills or statewave?

GraphCanon lists graph-backed alternatives at [skills alternatives](/tools/qdrant-skills/alternatives) and [statewave alternatives](/tools/smaramwbc-statewave/alternatives) ([skills markdown twin](/tools/qdrant-skills/alternatives.md), [statewave markdown twin](/tools/smaramwbc-statewave/alternatives.md)), ranked by typed relationship edges rather than popularity votes.

### Is there a machine-readable version of this comparison?

Yes. The markdown twin at [this comparison](/compare/qdrant-skills-vs-smaramwbc-statewave.md) mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.

### Which is better maintained, skills or statewave?

skills: Very active. statewave: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.

### Where are the full trust reports for skills and statewave?

GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: [skills trust report](/tools/qdrant-skills/trust); [statewave trust report](/tools/smaramwbc-statewave/trust).

---

**Machine-readable endpoints**

- JSON: [`/api/graphcanon/graph?tool=qdrant-skills`](/api/graphcanon/graph?tool=qdrant-skills)
- LLM index: [/llms.txt](/llms.txt)
- Full corpus: [/llms-full.txt](/llms-full.txt)

_GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_
