spring-data-neo4j
Spring Data Neo4j for graph database operations. Covers node/relationship entities, Cypher queries, and Neo4jTemplate. USE WHEN: user mentions "spring data neo4j", "Neo4jRepository", "@Node", "@Relationship", "Cypher Spring", "graph database Spring Boot" DO NOT USE FOR: raw Cypher queries - consult Neo4j documentation, relational databases - use `spring-data-jpa` instead
What this skill does
# Spring Data Neo4j - Quick Reference
> **Deep Knowledge**: Use `mcp__documentation__fetch_docs` with technology: `spring-data-neo4j` for comprehensive documentation.
## Dependencies
```xml
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-data-neo4j</artifactId>
</dependency>
```
## Configuration
### application.yml
```yaml
spring:
neo4j:
uri: bolt://localhost:7687
authentication:
username: neo4j
password: ${NEO4J_PASSWORD}
data:
neo4j:
database: mydb # Neo4j 4.0+
```
## Graph Concepts
```
┌─────────────────────────────────────────────────────────────┐
│ Graph Model │
│ │
│ ┌─────────┐ ┌─────────┐ │
│ │ Person │─────FOLLOWS────────▶│ Person │ │
│ │ (John) │ │ (Jane) │ │
│ └────┬────┘ └────┬────┘ │
│ │ │ │
│ WORKS_AT WORKS_AT │
│ │ │ │
│ ▼ ▼ │
│ ┌─────────┐ ┌─────────┐ │
│ │ Company │◀─────KNOWS───────────│ Person │ │
│ │ (Acme) │ │ (Bob) │ │
│ └─────────┘ └─────────┘ │
│ │
│ Nodes: Person, Company │
│ Relationships: FOLLOWS, WORKS_AT, KNOWS │
└─────────────────────────────────────────────────────────────┘
```
## Node Entities
```java
@Node("Person")
public class Person {
@Id
@GeneratedValue
private Long id;
private String name;
private String email;
private LocalDate birthDate;
// Outgoing relationship
@Relationship(type = "FOLLOWS", direction = Direction.OUTGOING)
private Set<Person> following = new HashSet<>();
// Incoming relationship
@Relationship(type = "FOLLOWS", direction = Direction.INCOMING)
private Set<Person> followers = new HashSet<>();
// Relationship with properties
@Relationship(type = "WORKS_AT")
private WorksAt employment;
// Multiple relationships of same type
@Relationship(type = "KNOWS")
private List<Knows> connections = new ArrayList<>();
}
@Node("Company")
public class Company {
@Id
@GeneratedValue
private Long id;
private String name;
private String industry;
@Relationship(type = "WORKS_AT", direction = Direction.INCOMING)
private Set<Person> employees = new HashSet<>();
}
```
## Relationship Entities
```java
@RelationshipProperties
public class WorksAt {
@Id
@GeneratedValue
private Long id;
@TargetNode
private Company company;
private String position;
private LocalDate startDate;
private LocalDate endDate;
private BigDecimal salary;
}
@RelationshipProperties
public class Knows {
@Id
@GeneratedValue
private Long id;
@TargetNode
private Person person;
private String context; // "work", "school", "family"
private LocalDate since;
private Integer trustLevel;
}
```
## Repository Pattern
```java
public interface PersonRepository extends Neo4jRepository<Person, Long> {
// Derived queries
Optional<Person> findByEmail(String email);
List<Person> findByNameContaining(String name);
// Custom Cypher queries
@Query("MATCH (p:Person)-[:FOLLOWS]->(f:Person) WHERE p.id = $personId RETURN f")
List<Person> findFollowing(Long personId);
@Query("MATCH (p:Person)<-[:FOLLOWS]-(f:Person) WHERE p.id = $personId RETURN f")
List<Person> findFollowers(Long personId);
@Query("""
MATCH (p:Person {id: $personId})-[:FOLLOWS*2..3]->(fof:Person)
WHERE NOT (p)-[:FOLLOWS]->(fof) AND p <> fof
RETURN DISTINCT fof
LIMIT $limit
""")
List<Person> findFriendsOfFriends(Long personId, int limit);
@Query("""
MATCH (p1:Person {id: $person1Id}), (p2:Person {id: $person2Id}),
path = shortestPath((p1)-[:KNOWS*]-(p2))
RETURN path
""")
List<Person> findShortestPath(Long person1Id, Long person2Id);
// Aggregations
@Query("""
MATCH (p:Person)-[:WORKS_AT]->(c:Company)
RETURN c.name as company, count(p) as employeeCount
ORDER BY employeeCount DESC
""")
List<CompanyStats> getCompanyStats();
// With relationship properties
@Query("""
MATCH (p:Person)-[w:WORKS_AT]->(c:Company)
WHERE p.id = $personId
RETURN p, w, c
""")
Person findWithEmployment(Long personId);
}
public interface CompanyRepository extends Neo4jRepository<Company, Long> {
@Query("""
MATCH (c:Company)<-[:WORKS_AT]-(p:Person)
WHERE c.id = $companyId
RETURN p
""")
List<Person> findEmployees(Long companyId);
}
```
## Neo4jTemplate Operations
```java
@Service
@RequiredArgsConstructor
public class GraphService {
private final Neo4jTemplate neo4jTemplate;
private final Neo4jClient neo4jClient;
// Save operations
public Person savePerson(Person person) {
return neo4jTemplate.save(person);
}
// Find by ID
public Optional<Person> findById(Long id) {
return neo4jTemplate.findById(id, Person.class);
}
// Custom queries with Neo4jClient
public List<Map<String, Object>> findMutualConnections(Long person1Id, Long person2Id) {
return neo4jClient.query("""
MATCH (p1:Person {id: $person1Id})-[:KNOWS]-(mutual:Person)-[:KNOWS]-(p2:Person {id: $person2Id})
RETURN mutual.name as name, mutual.email as email
""")
.bind(person1Id).to("person1Id")
.bind(person2Id).to("person2Id")
.fetch()
.all()
.stream()
.toList();
}
// Create relationship
public void createFollowRelationship(Long followerId, Long followeeId) {
neo4jClient.query("""
MATCH (a:Person {id: $followerId}), (b:Person {id: $followeeId})
MERGE (a)-[:FOLLOWS]->(b)
""")
.bind(followerId).to("followerId")
.bind(followeeId).to("followeeId")
.run();
}
// Delete relationship
public void removeFollowRelationship(Long followerId, Long followeeId) {
neo4jClient.query("""
MATCH (a:Person {id: $followerId})-[r:FOLLOWS]->(b:Person {id: $followeeId})
DELETE r
""")
.bind(followerId).to("followerId")
.bind(followeeId).to("followeeId")
.run();
}
// Complex graph traversal
public List<Person> findInfluencers(int minFollowers) {
return neo4jClient.query("""
MATCH (p:Person)<-[:FOLLOWS]-(follower:Person)
WITH p, count(follower) as followerCount
WHERE followerCount >= $minFollowers
RETURN p
ORDER BY followerCount DESC
""")
.bind(minFollowers).to("minFollowers")
.fetchAs(Person.class)
.mappedBy((typeSystem, record) -> {
// Custom mapping if needed
return neo4jTemplate.findById(
record.get("p").asNode().id(),
Person.class
).orElse(null);
})
.all()
.stream()
.filter(Objects::nonNull)
.toList();
}
}
```
## Projections
```java
// Interface projection
public interface PersonSummary {
String getName();
String getEmail();
int getFollowerCount();
}
// DTO projection
public record PersonDto(
Long id,
String name,
String email,
List<StringRelated in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.