Skip to content

[new-skill]qdrant framework integrations support#36

Closed
lucifertrj wants to merge 1 commit into
qdrant:mainfrom
lucifertrj:integrations
Closed

[new-skill]qdrant framework integrations support#36
lucifertrj wants to merge 1 commit into
qdrant:mainfrom
lucifertrj:integrations

Conversation

@lucifertrj
Copy link
Copy Markdown

What this PR does

Add new qdrant-integrations skill with framework-specific setup guides

What’s new

  • Added a new skill: skills/qdrant-integrations/SKILL.md
  • Added framework integration command guides under skills/qdrant-integrations/commands/:
    • langchain.md
    • llamaindex.md
    • haystack.md
    • cognee.md
    • google-adk.md

Note-1: I have also ran the validate_scripts:

PASS  skills/qdrant-integrations/SKILL.md

Note-2: Code snippets are inside Command as per the AgentSkills level-3 resource syntax

Type

  • new skill
  • skill improvement
  • new command
  • bug fix
  • repo hygiene

Checklist

  • python3 scripts/validate_skills.py passes
  • description has Use when with 5+ trigger phrases
  • leaf skills omit allowed-tools, hub skills declare them
  • ends with ## What NOT to Do section
  • no code blocks in skills (code belongs in commands/)
  • all doc links go to qdrant.tech/documentation/
  • tested with a realistic prompt (paste below or link to eval)

Test prompt

Used Google Antigravity

Show me how to use Qdrant with LangChain in Python: initialize the Qdrant vector store, upsert a
  few sample documents, run a similarity search, and include a minimal end-to-end code example.
Screenshot 2026-03-31 at 21 52 43

@lucifertrj lucifertrj changed the title qdrant framework integrations support [new-skill]qdrant framework integrations support Mar 31, 2026
@lucifertrj
Copy link
Copy Markdown
Author

let me know if you refer the files inside the commands to be markdown or python @thierrypdamiba

@thierrypdamiba
Copy link
Copy Markdown
Contributor

Hey Taurin, appreciate you taking a look and seeing how you could improve the repo. We're deciding not to merge the PR and clarify the scope of the skills repo. You can see details here: #37

Apologies for the incorrect and vague prior template, given the pre-existing language, this would have fit right in.

Thank you for your PR. It sparked a good discussion and made us reconsider exactly where the boundary should be on skills.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants