agentdb-hyperedge
Search and manage hyperedges — n-ary relationships between memories. Use for swarm membership, multi-cause incidents, or any "this involves all of (A, B, C, D)" relationship that doesn't fit a binary edge.
소스 정보
- 저장소
- ruvnet/agentdb
- 최근 소스 활동
- 2026년 5월 6일 15:22
- 감지된 SKILL.md 언어
- 영어
- 스타
- 89
- 포크
- 14
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- agentdb-hyperedge
- description
- Search and manage hyperedges — n-ary relationships between memories. Use for swarm membership, multi-cause incidents, or any "this involves all of (A, B, C, D)" relationship that doesn't fit a binary edge.
# Hyperedge
Hyperedges connect more than two nodes — useful when a single relationship genuinely involves many participants.
## When to use
- **Swarm membership** — "agents A, B, C, D worked together on task T"
- **Multi-cause incidents** — "outage was caused by (deploy, traffic spike, cache miss, retry storm)"
- **Group decisions** — "ADR-046 was approved by reviewers (alice, bob, carol, dan)"
- Anything where binary edges would lose information by splitting the relationship
## API
```
agentdb_hyperedge_create(
nodes: [<id>, <id>, ...]
description: <one-liner>
embedding?: Float32Array
confidence?: 0..1
metadata?: { ... }
)
agentdb_hyperedge_search(
query: <semantic | nodeId>
topK?: 10
)
agentdb_hyperedge_delete(
id: <hyperedge id>
)
```
The `agentdb_hyperedge_delete` tool was added in agentdb 3.0.0-alpha.13.
## Semantic search over hyperedges
Hyperedges are searchable by their description embedding — useful for "find all multi-agent collaborations on auth-related work" without enumerating every binary edge.
## Don't
- Don't use a hyperedge when a binary edge fits. Two-node "caused" links are cheaper to reason about.
- Don't put more than ~10 nodes in one hyperedge. After that, the relationship is too broad to mean anything specific.
GitHub에서 보기