force-graph
Render an interactive force-directed graph from a simple node/link DSL or JSON. Use to visualise relationships, dependencies, knowledge graphs, mind maps.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- force-graph
- description
- Render an interactive force-directed graph from a simple node/link DSL or JSON. Use to visualise relationships, dependencies, knowledge graphs, mind maps.
03 SKILL.md 正文
Force graph
Renders an interactive, draggable, zoomable force-directed graph. Two input formats are supported: a concise arrow-based DSL and a more explicit JSON form.
Arrow DSL
```force-graph
User --> System
System --> Database
Database --> Backup
```
Labelled edges:
```force-graph
User -- logs in --> System
System -- authenticates --> Database
```
JSON form
```force-graph
{
"nodes": [
{ "id": "user", "name": "User", "val": 5 },
{ "id": "api", "name": "API", "val": 8 }
],
"links": [
{ "source": "user", "target": "api", "label": "calls" }
]
}
```
Node and link fields
id— unique node id (required).name— display label.val— relative size weight.color,group— optional styling/grouping.source/target— link endpoints (must match node ids).label— optional edge label.
Tips
- Keep graphs under ~50 nodes for readability.
- The graph is interactive — users can drag nodes and zoom; nothing extra needed.
- For diagrams with strict layout (sequence, flowchart, gantt, ER), prefer
mermaid. Force-graph is best for unstructured relationship maps.
04 同仓库更多 Skills
youtube
Embed a YouTube video by pasting its URL on its own line. Neko auto-detects watch/youtu.be/embed forms and honours timestamp, autoplay, loop, and mute parameters.
workflow
Render a workflow diagram from a node-and-arrows DSL — labelled boxes with icons and optional badges, auto-arranged in columns. Use for pipelines, data flows, sign-off chains, ETL diagrams.
video
Author a video as a single Markdown file (`video:` front matter) — scenes separated by horizontal rules, every block animating in on its own, video components (lockup, swap, typewriter, scramble, counter, stats, chart, code, terminal, browser/window/phone, cursor, lower-third, captions, quote, steps, checklist, grid/card, cta, logo, media), scene transitions and camera moves, and a synthesized voice-over (`--- {narration}` parts, `narration:` voice, `neko voiceover`) — preview it in the browser and render it to MP4 with `neko render` (Playwright + ffmpeg). Also covers the `[!video]` component that embeds the rendered file in a page. Use when asked for a video, an animated explainer, a product or release teaser, a changelog video, a motion graphic, a narrated walkthrough, or an MP4 from docs content.
update-documentation
Workflow for updating Neko documentation — base every page on the real source code, never invent APIs, warn loudly when the source isn't available, and check that the page (and any changed `tesserae` sample) renders correctly with Playwright / snapframe / a visual check. Use whenever you add or edit docs that describe code, APIs, components, or live samples.
tesserae
Render a live Tesserae C# UI block — Neko compiles and executes the C# at build time and shows both the code and a working preview side-by-side. Use only when the project documents Tesserae or runs live C# samples.
table
Render a Markdown table with alignment, compact mode, and no-wrap option. Use for any tabular comparison, reference matrix, option list.