link-event-directory

Inspect, create, or repair Digital SZTU event relationships and Obsidian-style backlinks across event, person, organization, place, institution, topic…

Skill by Shuang-su

IndexedApache-2.0★ 3

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/shuang-su-link-event-directory

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Inspect, create, or repair Digital SZTU event relationships and Obsidian-style backlinks across event, person, organization, place, institution, topic, source, and collection indexes. Use for linking, backlinks, related directories, aliases, or dangling references; not for inventing evidence.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/link-event-directory

What's inside

Skill name: link-event-directory
Description: Inspect, create, or repair Digital SZTU event relationships and Obsidian-style backlinks across event, person, organization, place, institution, topic, source, and collection indexes. Use for linking, backlinks, related directories, aliases, or dangling references; not for inventing evidence.
License: Apache-2.0
Instructions: 11 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# Link events and directories

1. Work in a user-selected Digital SZTU clone with the pinned local CLI installed as described in `README.md`. Load the Event, its Claims and Sources, then search existing Nodes by ID, name, and alias.
2. Treat fuzzy name matches as candidates, not identity. If identity cannot be established, keep separate Nodes and report the ambiguity.
3. Store each evidence-bearing relationship once in the originating Event `links[]`. Every Link requires at least one `claim_id` and one `source_id`, and each Source must be cited by one of those Claims. Use a Markdown wikilink for navigation-only associations.
4. Use a short kebab-case relation that describes the direction from Event to target, such as `involves`, `held-by`, `occurs-at`, `changes`, `about`, `follows`, `corrects`, or `related-to`.
5. Use Markdown `[[id|label]]` only for navigation or prose references; do not use it to bypass Claim/Citation evidence.
6. Run `digital-sztu build --json`. Confirm the target has an incoming entry in `data/generated/backlinks.json` and the Event appears in each applicable `data/generated/directories/*.json` file.
7. Never hand-edit `data/generated/`, and never write reciprocal Event lists into Node files.

From Shuang-su/digital-sztu, Apache-2.0.

Signals

Stars: 3
Forks: 0
Open issues: 5
Last commit (this folder): Sep 5, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License: Apache-2.0
Repository: github.com/Shuang-su/digital-sztu
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from Shuang-su

Cite this page

link-event-directory skill. Agent Mart. https://agentmart.dev/skills/shuang-su-link-event-directory (last updated 2026-10-24)