obsidian-kb-artifacts
The obsidian-kb-artifacts skill handles formatting and structural concerns for Obsidian knowledge bases, including Markdown syntax, wikilinks, registry tables, canvas files, and link repair operations. Use this skill when creating or maintaining Obsidian-native artifacts and technical formatting requirements, but not for deciding where knowledge should be routed or organized.
git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar /tmp/obsidian-kb-artifacts && cp -r /tmp/obsidian-kb-artifacts/skills/obsidian-kb-artifacts ~/.claude/skills/obsidian-kb-artifactsSKILL.md
# Obsidian KB Artifacts This skill handles format and artifact concerns only. ## Responsibilities - Obsidian Markdown formatting - wikilinks and embeds - registry table formatting - canvas generation and validation - optional Bases generation - Obsidian CLI operations - link repair in canonical notes - lint-report formatting ## Rules - this skill does not decide where knowledge belongs - `.base` is explicit-only - `Maps/` contains derived artifacts only - link repair should strengthen existing canonical notes, not create note sprawl - literature canvas edges must preserve evidence strength when the source notes provide it - do not create stable-looking claim edges from abstract-only, webpage-placeholder, or unsupported notes ## Read next - `references/OBSIDIAN-MARKDOWN.md` - `references/CANVAS.md` - `references/BASES.md` - `references/REGISTRY-TABLES.md` - `references/LINK-REPAIR.md` - `references/CLI.md`
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.