Repository navigation
Add qdrant-cloud-quickstart skill - #189
Conversation
✅ Deploy Preview for qdrant-skills ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
szabosteve
left a comment
There was a problem hiding this comment.
LGTM, thank you!
Do you mind adding the skill to the list in AGENTS.md, too?
|
Thanks @szabosteve for the review! I added the skill to the list in AGENTS.md. |
|
@chadha-sridi some feedback from the engineering team:
|
|
Thanks @kanungle for the feedback. I will update the PR accordingly. |
|
@kanungle, thanks for the feedback! Here's how I handled each point. Applied
Evals Walkthrough Results for the two new prompts |
What this PR does
Adds
qdrant-managed-cloud-quickstart, a leaf skill for getting a first Managed Cloud cluster created, connected, and safe to rely on. It covers the Cloud traps no other skill does: the two key types, strict mode on new collections, free-tier suspension, and choices that can't be reversed. Linked fromqdrant-deployment-options, the README, and the skills index.Also adds a test prompt for the skill:
evals/test-prompts/qdrant-managed-cloud-quickstart.jsonType
Checklist
python3 scripts/validate_skills.pypassesUse whenwith 5+ trigger phrasesallowed-tools, hub skills declare them## What NOT to Dosectionskills.qdrant.tech/md/documentation/Test prompt
All new test prompts now live in #191
Prompt 1
Moving from local Docker to a free cluster. A team moved to a free cluster for a demo in five weeks. Their client gets 401s using a key made under Access Management, and a filter on
categorythat worked locally now errors. They plan a 3-node production setup next.With the skill: PASS, 4/4 musts. Identified the wrong key type, fixed the
filter with a payload index, and warned that the free cluster would be deleted before the five-week demo.
Without the skill: 3/4 musts. Missed the free-cluster deletion risk entirely, and claimed shard count is fixed at creation, which is wrong on Cloud.
Prompt 2
EU inference + restoring into a live cluster. A Frankfurt team plans to switch to free all-MiniLM via Cloud Inference and to restore a week-old backup into production after scaling to 3 nodes and upgrading. The prompt
only asks how to do both.
Prompt 3
Offboarding + Marketplace billing. CI gets 401s from a key created by a contractor who left; finance wants AWS Marketplace billing; another team needs a GCP cluster.
create:api_keysinstead ofwrite:api_keys.Conclusion: the skill passes all three prompts. On correctness, the clear wins are prompt 1, where the agent without the skill missed the free-tier deletion risk, and the restore downtime in prompt 2. On the rest, an agent
with web search finds the same facts, and the skill's value is getting there about 30-40% faster and cheaper, from Qdrant's docs rather than third-party sources.