obsidian-check

Validate Obsidian plugin code against quality and style rules.

6|2|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/acaprino/anvil-toolset --skill obsidian-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-check
Source: https://github.com/acaprino/anvil-toolset/tree/main/plugins/obsidian-development/skills/obsidian-check
Command: npx skills add https://github.com/acaprino/anvil-toolset --skill obsidian-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires eslint, eslint-plugin-obsidianmd, @typescript-eslint/parser, @eslint/js, typescript, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the rigorous code review process for Obsidian plugins, ensuring adherence to best practices and preventing common errors before submission or deployment.

Core Features & Use Cases

  • Automated Linting: Enforces ObsidianReviewBot rules, checks TypeScript, and runs ESLint.
  • Manifest & License Validation: Verifies manifest.json and LICENSE file integrity.
  • Proactive Quality Assurance: Catches issues related to type assertions, promise handling, and code style.
  • Use Case: Before pushing a new feature to your Obsidian plugin's repository, run /obsidian-check to catch potential bugs and style violations, ensuring a smoother review process.

Quick Start

Run the obsidian-check skill to scan the current Obsidian plugin project for all bot violations.

Frequently Asked Questions about obsidian-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Obsidian plugin code review and linting before submission?

You can automate Obsidian plugin code review by running a validation skill that checks project structure, TypeScript compilation, ESLint rules, and manifest.json compliance to catch common pitfalls before submission.

What does ESLint check for in Obsidian plugin development?

ESLint checks in Obsidian plugin development enforce code style, verify TypeScript compilation, and catch promise handling or type assertion issues using eslint-plugin-obsidianmd to ensure manifest.json and LICENSE compliance.

Do I need TypeScript and ESLint to validate my Obsidian plugin?

Yes, TypeScript and ESLint are required dependencies to validate an Obsidian plugin. The validation process uses @typescript-eslint/parser and eslint-plugin-obsidianmd to enforce quality rules and verify code compiles correctly.

How do I validate manifest.json and LICENSE files for an Obsidian plugin?

To validate manifest.json and LICENSE files for an Obsidian plugin, run an automated quality assurance check that verifies file integrity and ensures compliance with required submission standards.

What is the best way to catch common Obsidian plugin code violations?

The best way to catch common Obsidian plugin code violations is to run an automated linting and manual inspection process that proactively identifies type assertion issues, promise handling errors, and style violations.

Why does my Obsidian plugin fail the ObsidianReviewBot checks?

Your Obsidian plugin fails ObsidianReviewBot checks when it contains TypeScript compilation errors, ESLint violations, improper promise handling, incorrect type assertions, or a non-compliant manifest.json file.