obsidian
CheckedComprehensive guidelines for Obsidian.md plugin development including all 27 ESLint rules from eslint-plugin-obsidianmd v0.1.9, TypeScript best practices, memory management, API usage (requestUrl vs f
Install on your platform
Showing OpenClaw.
- 1
Run this in your terminal
terminal$
What we know about this skill
Publisher
gapmiss
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned gapmiss/obsidian-plugin-skill at ff97cb0e2a.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- ff97cb0e2a
- Manifest
- .agents/skills/obsidian/SKILL.md
- Scanned
- 11 files, 3,388 lines
About this skill
What it does
This skill provides detailed guidance and resources for developing plugins for Obsidian.md, a popular note-taking application. It covers the full spectrum of plugin development, including adhering to 27 ESLint rules from eslint-plugin-obsidianmd, implementing TypeScript best practices, managing memory effectively, and understanding nuances in API usage such as differentiating between requestUrl and other request methods. The skill aims to ensure robust and maintainable Obsidian plugins.
When to use it
- You're starting a new Obsidian plugin project and need guidance on structure and coding standards.
- You want to understand how to correctly implement specific Obsidian API functions, like
requestUrl. - Your existing Obsidian plugin is failing ESLint checks and you need help resolving the issues.
- You’re experiencing memory leaks or performance problems in your plugin and require advice on optimization techniques.
Key capabilities
- Adherence to 27 ESLint rules for Obsidian plugins (from
eslint-plugin-obsidianmd v0.1.9). - TypeScript best practices for plugin development.
- Memory management strategies within the Obsidian environment.
- Guidance on using Obsidian APIs, including distinctions between request methods.
Example prompts
- "Explain how to use
requestUrlin an Obsidian plugin." - "What are the most common ESLint errors when developing Obsidian plugins?"
- "How can I optimize memory usage in my Obsidian plugin?"
Tips & gotchas
This skill assumes a basic understanding of JavaScript and TypeScript. Successfully utilizing this skill requires familiarity with the Obsidian API documentation as it provides guidelines for development, not direct code execution.