kb-links
The kb-links command repairs and strengthens existing wikilinks across canonical knowledge base notes in designated directories like Sources, Knowledge, and Experiments without creating unnecessary new notes. Use this when internal cross-references need fixing or linking before running downstream commands like kb-sync or kb-lint.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/Galaxy-Dawn/claude-scholar/HEAD/commands/kb-links.md -o ~/.claude/commands/kb-links.mdkb-links.md
# /kb-links Use `obsidian-kb-artifacts` for standalone wikilink repair. Default surfaces: - `Sources/` - `Knowledge/` - `Experiments/` - `Results/` - `Writing/` - `00-Hub.md` - `01-Plan.md` - `02-Index.md` Rules: - repair links inside existing canonical notes first - do not create new notes just to satisfy a weak connection - after substantial link repair, run `/kb-sync` or `/kb-lint` - only touch `Maps/` when the user explicitly wants artifact updates
Use when creating or configuring Claude Code agents and their frontmatter.
Run a blocker-first post-experiment workflow: validate evidence, produce strict statistical analysis when possible, and generate a decision-oriented results report only when the analysis bundle is sufficient. Uses results-analysis + results-report as a gated two-stage workflow.
Use only when creating new registrable ML components that require Factory or Registry patterns.
This skill should be used when the user asks to "debug this", "fix this error", "investigate this bug", "troubleshoot this issue", "find the problem", "something is broken", "this isn't working", "why is this failing", or reports errors/exceptions/bugs. Provides systematic debugging workflow and common error patterns.
This skill provides reference guidance for citation verification in academic writing. Use when the user asks about "citation verification best practices", "how to verify references", "preventing fake citations", or needs guidance on citation accuracy. This skill supports ml-paper-writing by providing detailed verification principles and common error patterns.
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or improve how a team performs code review.
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.