obsidian-plugin-dev
v1.0.0Comprehensive skill for Obsidian plugin development with TypeScript. Covers plugin lifecycle, CodeMirror 6 editor extensions, React/Svelte integration, Vault...
⭐ 0· 77·0 current·0 all-time
by@yungho
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description match the provided content: the SKILL.md and reference docs are focused on Obsidian plugin development (lifecycle, CM6, React/Svelte, settings, testing, CI/CD, submission). There are no unrelated environment variables, binaries, or install steps requested that would be disproportionate to this purpose.
Instruction Scope
All runtime instructions are documentation and code patterns for plugin authors. The skill does not instruct the agent to read system files, export credentials, or call arbitrary external endpoints at runtime. Examples that mention network requests, SecretStorage, or CI secrets are contextual (how to implement or configure) and appropriate for the stated scope.
Install Mechanism
This is an instruction-only skill with no install spec and no code files executed by the agent. No external downloads or archive extraction are specified, minimizing install-time risk.
Credentials
The skill declares no required environment variables, credentials, or config paths. Reference material mentions common CI secrets (e.g., CODECOV_TOKEN) and SecretStorage API usage as part of guidance, but it does not request those secrets from the agent or user.
Persistence & Privilege
Flags are default (always:false, user-invocable:true). The skill does not request permanent presence or elevated agent configuration changes. Autonomous invocation is allowed by default but is not combined with any other concerning privileges.
Assessment
This skill is a large, local reference (docs and code examples) for building Obsidian plugins — its files and rules are coherent with that goal. Before installing: (1) prefer obtaining skills from a trusted source or repository (the metadata lists an unknown owner and no homepage), (2) review the README/license and any code examples you plan to run (these are only examples and should be reviewed before copy/paste), and (3) be aware that the docs show how to use SecretStorage and CI tokens in examples — those are implementation notes, not requests for your secrets. If you plan to let an agent run code it generates from this skill, audit the produced code (particularly any network calls, telemetry, or release scripts) before executing. If you want higher assurance, ask the skill author for source hosting (GitHub) or a verifiable checksum.Like a lobster shell, security has layers — review code before you run it.
latestvk97465qx0y4cg9afpz16mv68xd83n59q
License
MIT-0
Free to use, modify, and redistribute. No attribution required.