8dazo/versioned-sample-uses
.cursor/skills/versioned-sample-uses/SKILL.md
When publishing a new elix-db version or making version changes, run versioned sample use cases, collect memory/time/latency, compare to the previous version report, and update reports. Remember this workflow for releases.
$ install --global
skillsauthnpx skillsauth add 8dazo/elix-db versioned-sample-usesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 9:00 PM1.8s1 file scanned
SKILL.md
- name:
- versioned-sample-uses
- description:
- When publishing a new elix-db version or making version changes, run versioned sample use cases, collect memory/time/latency, compare to the previous version report, and update reports. Remember this workflow for releases.
Versioned Sample Uses and Release Benchmark
Apply when publishing a new version, cutting a release, or making version-related changes to elix-db.
When to Use
- Before or after publishing a new elix-db version (e.g. v0.2.0, v0.3.0)
- When the user says "publish", "release", "version change", or "new version"
- When adding or changing versioned sample use cases
What to Remember
Sample uses are organized by version: sample_uses/v0.1.0/, sample_uses/v0.2.0/, etc. Inside each version folder are the same use cases: 01_simple_search, 02_semantic_faq, 03_similar_items, 04_persistence. Each use case pins elix_db to that version in its mix.exs.
On a new version release:
- Ensure
sample_useshas a version folder for the new version (e.g.v0.2.0) with the same four use cases andelix_dbpinned to that version. - Run the benchmark runner for the new version (e.g. from repo root: run the script that executes each use case in
sample_uses/<version>/, collects metrics). - Compare to the previous version: load the previous version’s report from
sample_uses/reports/, generate a comparison report (how the new version is better or worse on memory, time, latency, throughput). - Update or add report files under
sample_uses/reports/(e.g.<version>.json,<version>_vs_<prev>.md). - Optionally update CHANGELOG or README with a one-line pointer to the comparison report.
Metrics that matter for the vector DB: memory (e.g. :erlang.memory()), wall time per use case, latency (mean/p50/p99 for search and upsert), throughput (inserts/s, searches/s). The comparison report should answer: how is this version compared to the previous one?
Workflow Summary
- Add or update version folder under
sample_uses/<vX.Y.Z>/with use cases pointing to that elix_db version. - Run benchmark for the new version; write
sample_uses/reports/<version>.json(and optional.md). - Load previous version report; produce comparison report (e.g.
reports/<version>_vs_<prev>.md). - Remember: this workflow should be run whenever we publish or make version changes so we track memory, time, latency, and other important factors across versions.
Related
- debug-verify-benchmark – for day-to-day changes to vector/store/API (tests, IEx, industry comparison).
- versioned-sample-uses – for release/version workflow (sample use cases, version comparison, reports).
Related Skills
8dazo/vector-db-storage
development
VerifiedTrustedCommunity
Storage backends and indexing for vector databases in Elixir. Use when choosing persistence, implementing exact vs approximate k-NN, or integrating pgvector, file, or ETS for vector storage.
3SKILL.mdUpdated Apr 17, 2026
8dazo/vector-db-elixir
development
VerifiedTrustedCommunity
Design and implement a vector database in Elixir. Use when building embedding storage, similarity search, k-NN retrieval, or when the user mentions vector DB, embeddings, or semantic search in Elixir.
3SKILL.mdUpdated Apr 17, 2026
8dazo/elixir-vector-patterns
data-ai
VerifiedTrustedCommunity
Elixir patterns for vector storage and similarity search. Use when implementing GenServer-based vector store, ETS index, Nx/Scholar distance math, or supervision for a vector DB in Elixir.
3SKILL.mdUpdated Apr 17, 2026
8dazo/debug-verify-benchmark
development
VerifiedTrustedCommunity
Debug, verify, and compare elix-db to industry after each plan step. Use after implementing any plan step or changing vector/store/API logic; run tests, IEx checks, and document efficiency vs Qdrant/Milvus/pgvector.
3SKILL.mdUpdated Apr 17, 2026