connectors

Connect to graph databases and query via Gremlin, openCypher, or SPARQL.

476|102|Updated Oct 26, 2022
One-click install
npx skills add https://github.com/aws/graph-explorer --skill connectors
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: connectors
Source: https://github.com/aws/graph-explorer/tree/main/.kiro/skills/connectors
Command: npx skills add https://github.com/aws/graph-explorer --skill connectors

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized way to connect to and query various graph databases, abstracting away the complexities of different query languages.

Core Features & Use Cases

  • Database Connectivity: Supports Gremlin, openCypher, and SPARQL query languages.
  • Query Abstraction: Offers a unified interface for database interactions through "Explorers".
  • Consistent API: Ensures common interfaces for all database connectors.
  • Use Case: Seamlessly query your Amazon Neptune database using openCypher or explore data in a Gremlin-enabled graph database without needing to learn multiple query syntaxes.

Quick Start

Use the connectors skill to query the attached database using Gremlin.

Frequently Asked Questions about connectors

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I query a graph database using Gremlin, openCypher, or SPARQL?

You can query a graph database by using abstract Explorers that provide a unified interface, ensuring consistent API implementation across Gremlin, openCypher, and SPARQL query languages.

What is the best way to connect to Amazon Neptune using openCypher?

Connecting to Amazon Neptune is facilitated through standardized database connectors that abstract query complexities, allowing you to seamlessly explore data using the openCypher query language.

Do I need to learn multiple query syntaxes to explore different graph databases?

No, you do not need to learn multiple query syntaxes because the Skill provides a standardized query abstraction through Explorers, facilitating database interactions across different query languages.

How do I ensure consistent API implementation when switching between SPARQL and Gremlin?

Consistent API implementation is ensured by using common interfaces for all database connectors, which standardizes interactions regardless of whether you are querying with SPARQL or Gremlin.

Are there specific string escaping utilities required for Gremlin database queries?

Yes, querying Gremlin-enabled graph databases requires adherence to specific query templating and string escaping utilities designed to ensure proper syntax and execution within the Gremlin query language.