Menü
Create and curate graph edges between chunks (and across documents) in a chunked-graph Document.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Import a Markdown file into a chunked-graph Document — deterministic round-trip vs semantic chunking.
Safely move, reparent, reorder, promote, or delete chunks in a chunked-graph Document.
Split arbitrary prose or a Markdown file into a sensible chunk hierarchy in a chunked-graph Document.
How to review a slice of a code repository with high precision — confidence-scored findings, project-guideline compliance, and Karpathy behavioral guidelines (simplicity, surgical scope, surfaced assumptions). Use when reviewing or auditing source files.
| name | doc/edge-linking |
| description | Create and curate graph edges between chunks (and across documents) in a chunked-graph Document. |
| tools | ["Document"] |
| license | Apache-2.0 |
Chunks form a tree by parent_id, but they also carry a free-form graph of
typed edges (link_chunks) — "this publication promotes that blog post", "this
task targets that requirement". Use edges for cross-cutting relations that the
parent/child hierarchy can't express.
query_chunks / get_chunk — both chunks
must already exist (an edge to a missing chunk is refused). Cross-document
edges are allowed as long as both chunks are in this scope.kind verb the operator will recognize: references,
promotes, targets, depends_on, supersedes. Reuse existing kinds in
the document rather than inventing near-duplicates.Document op=link_chunks from_id=<a> to_id=<b> kind="references"
(idempotent — re-linking the same triple is a no-op).op=unlink_chunks from_id=<a> to_id=<b> kind="…".from → to). State the direction back to the operator.