メニュー
This skill should be used when the user asks to "add backlinks", "find related notes", "what should this link to", "update backlinks", "suggest connections", or needs to find appropriate wikilinks for a note.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | backlinks-a |
| type | action |
| description | This skill should be used when the user asks to "add backlinks", "find related notes", "what should this link to", "update backlinks", "suggest connections", or needs to find appropriate wikilinks for a note. |
| argument-hint | <filepath> |
Action skill — Backlink suggestion workflow: structural search, semantic search, cross-area scan, strength grouping.
Find and suggest appropriate [[wikilinks]] for a note using structural analysis and semantic search.
Given a file path:
Read the note's content. Identify its area/project, key concepts, tags, and existing links.
[[note-name]] to find all notes that already link TO this note.00_ file) to see what's linked and how sections are organized.Run qmd vsearch with the note's key sentences or title to find semantically similar notes across the vault.
qmd vsearch "the key concept from the note" --files
Use 2-3 queries with different phrasings for better coverage.
Check MOCs in related areas for potential cross-links. Read MOCs from areas that share concepts with the target note.
For example, if the note is in ai-dev-ecosystem and mentions statistical concepts, check 00_math-stats.md.
Look for notes with the same knowledge-role tags that might be conceptually related:
#thread notes in the same area → likely part of the same developing narrative#question notes → might pose questions this note answers (or vice versa)#tool notes → frameworks that apply to this note's topic#insight notes → crystallized understanding related to this note's seeds/threadsGroup suggestions by strength:
Strong matches — Same area, high semantic similarity, shared concepts:
- [[2025-01-21_agentic-primitives]] — shares agent architecture concepts
→ Add to note's ## Related section
Cross-area connections — Different area, meaningful overlap:
- [[00_modeling]] (modeling area) — note discusses model capabilities
→ Add cross-link in note's ## Related section
MOC links — MOCs that should reference this note:
- [[00_ai-dev-ecosystem]] — note not yet linked in area MOC
→ Add to MOC's appropriate section with annotation
For each accepted suggestion:
## Related section at the bottom. Create the section if it doesn't exist.## Related
- [[2025-01-21_agentic-primitives]] — agent building blocks
- [[00_modeling]] — model capabilities that enable agentic workflows
Keep annotations brief. One phrase describing why the link matters.
Write high-quality session prompts (SESSION_WORKER.md and SESSION_REVIEWER.md) for an agent loop. Reads repo context and follows the loop-author guide to produce targeted, effective prompts. Use when setting up a new loop or rewriting session prompts for an existing one.
Pre-flight checks and launch for agent loops. Validates branch state, session prompts, creates loop directory structure, and launches run.sh in a tmux session. Use when the user wants to start a new agent loop in the current repo.
Cross-repo visibility for agent loops. Lists running, completed, and crashed loops. Reads the registry and per-repo tracking logs. Shows tmux attach commands. Use when checking what loops are active, what ran recently, or loop details.
Capture feedback about wf, util, or vault plugins and file it as a GitHub issue for improvement. Use after any session where the tooling fell short — wrong agent behavior, missing skill coverage, misleading prompts, workflow friction, or convention gaps. Only for generic plugin improvements that would help ANY project, not repo-specific config. Files to JSai23/claude-tooling with the plugin-feedback label.
Write high-quality session prompts (SESSION_WORKER.md and SESSION_REVIEWER.md) for an agent loop. Reads repo context and follows the loop-author guide to produce targeted, effective prompts. Use when setting up a new loop or rewriting session prompts for an existing one.
Pre-flight checks and launch for agent loops. Validates branch state, session prompts, creates loop directory structure, and launches run.sh in a tmux session. Use when the user wants to start a new agent loop in the current repo.