Create Module
cartography-cncf/cartography
Author a new Cartography intel module end-to-end (entry point, sync GET/TRANSFORM/LOAD/CLEANUP, declarative data model, integration test, schema docs).
Skill for testing Obsidian plugin features in this repository.
Install Plugin Testing
$ npx skills add polyipseity/obsidian-terminal --skill plugin-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install polyipseity/obsidian-terminal plugin-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/polyipseity/obsidian-terminal.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/plugin-testing .claude/skills/plugin-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "plugin-testing" agent skill from https://github.com/polyipseity/obsidian-terminal/tree/main/.agents/skills/plugin-testing into .claude/skills/plugin-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/polyipseity/obsidian-terminal/tree/main/.agents/skills/plugin-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add polyipseity/obsidian-terminal --skill plugin-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install polyipseity/obsidian-terminal plugin-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/polyipseity/obsidian-terminal.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/plugin-testing .agents/skills/plugin-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "plugin-testing" agent skill from https://github.com/polyipseity/obsidian-terminal/tree/main/.agents/skills/plugin-testing into .agents/skills/plugin-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add polyipseity/obsidian-terminal --skill plugin-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install polyipseity/obsidian-terminal plugin-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/polyipseity/obsidian-terminal.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/plugin-testing .cursor/skills/plugin-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "plugin-testing" agent skill from https://github.com/polyipseity/obsidian-terminal/tree/main/.agents/skills/plugin-testing into .cursor/skills/plugin-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/polyipseity/obsidian-terminal.git --path .agents/skills/plugin-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add polyipseity/obsidian-terminal --skill plugin-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install polyipseity/obsidian-terminal plugin-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/polyipseity/obsidian-terminal.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/plugin-testing .gemini/skills/plugin-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "plugin-testing" agent skill from https://github.com/polyipseity/obsidian-terminal/tree/main/.agents/skills/plugin-testing into .gemini/skills/plugin-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install polyipseity/obsidian-terminal plugin-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add polyipseity/obsidian-terminal --skill plugin-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/polyipseity/obsidian-terminal.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/plugin-testing .github/skills/plugin-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "plugin-testing" agent skill from https://github.com/polyipseity/obsidian-terminal/tree/main/.agents/skills/plugin-testing into .github/skills/plugin-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add polyipseity/obsidian-terminal --skill plugin-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install polyipseity/obsidian-terminal plugin-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/polyipseity/obsidian-terminal.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/plugin-testing .opencode/skills/plugin-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "plugin-testing" agent skill from https://github.com/polyipseity/obsidian-terminal/tree/main/.agents/skills/plugin-testing into .opencode/skills/plugin-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plugin-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
plugin-testing- GitHub stars
- 948
- Token cost
- ~828 tokens
- SKILL.md length
- 406 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Skill for testing Obsidian plugin features in this repository.
- Works in 5 steps: Build → Install → Settings UI → …
- Integration test workflows specific to Obsidian plugins
- SKILL.md covers Key Testing Principles, Test File Conventions, Test File Structure and Example Test Workflow, plus 1 more section
- Calls bun
What it does
Plugin Testing is an agent skill from polyipseity/obsidian-terminal. Skill for testing Obsidian plugin features in this repository. Use for automated, manual, and integration test workflows specific to Obsidian plugins.
Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Integration testing. It works with Obsidian. The repository describes itself as: Integrate consoles, shells, and terminals. The licence is AGPL-3.0.
When your agent uses it
- Integration test workflows specific to Obsidian plugins
- Tasks that involve Integration testing
Example prompts
- “/plugin-testing”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Build
- Install
- Settings UI
- Localization
- Lifecycle
What it can do on your machine
Read from SKILL.md and the folder at commit 8cbff89. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bun
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Plugin Testing loads about 828 tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 406 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from polyipseity/obsidian-terminal at commit 8cbff89, republished under its AGPL-3.0 licence (© polyipseity). 406 words, ~828 tokens.
Download SKILL.mdSave it as
.claude/skills/plugin-testing/SKILL.md (or your agent's skills folder).- name
- plugin-testing
- description
- Skill for testing Obsidian plugin features in this repository. Use for automated, manual, and integration test workflows specific to Obsidian plugins.
Plugin Testing Skill
Note: Always prefer
bunover other package managers if possible. Usebunfor all commands unless you have a specific reason to use another package manager.
Use this skill to guide both automated and manual testing of Obsidian plugin features. Ensure all tests reflect real plugin usage and production-like conditions.
Key Testing Principles
- Always build the plugin before testing (
bun run build). - Use the install script to deploy to a test vault (
bun run obsidian:install <vault>preferred). - Helpful scripts for testing:
bun run build— build before running tests or manual testingbun run obsidian:install <vault>— install the built plugin into a test vaultbun run format— format code before testing if neededbun run check— run lint & formatting checks
- Test settings UI for load, save, and persistence.
- Validate localization for all supported languages.
- Confirm plugin lifecycle events (load/unload) work as expected.
Test File Conventions
*.spec.{ts,js,mjs}— Unit tests (BDD-style): focus on behaviour and small, isolated units. Prefer tests that are fast and hermetic.*.test.{ts,js,mjs}— Integration tests (TDD-style): focus on integration between components or with the environment; keep them well documented and isolated.
Run unit-only suites with the Vitest CLI:
bun x vitest run "tests/**/*.spec.{js,ts,mjs}" --coverageAnd integration-only suites with:
bun x vitest run "tests/**/*.test.{js,ts,mjs}" --coverageShow full SKILL.md (211 more words)Show less
Test File Structure
- Follow a one test file per source file rule: mirrors the source directory tree under
tests/(for both*.spec.*and*.test.*). Prefer a single test file per source (either a*.spec.*unit test or a*.test.*integration test). If a source requires both unit and integration coverage, having both a*.spec.*and a*.test.*file is acceptable — treat them together as the logical "one test file" for that source and keep their locations aligned for discoverability. - Keep names aligned with source files for discoverability:
src/path/to/module.js->tests/unit/path/to/module.spec.js. - If a test file would become unreasonably large, splitting is allowed but should be a rare exception; include a brief header comment explaining the reason and the mapping across split files.
For the full list and usage of scripts, see the Scripts (package.json) section in AGENTS.md.
Example Test Workflow
- Build:
- Run:
bun run build
- Run:
- Install:
- Run:
bun run obsidian:install <vault directory>.
- Run:
- Settings UI:
- Open plugin settings in Obsidian
- Change and save settings; reload plugin and verify persistence
- Localization:
- Switch Obsidian language; verify all UI text updates accordingly
- Lifecycle:
- Reload or disable/enable the plugin; ensure all managers register/unload cleanly
References
- See src/main.ts for plugin entry and lifecycle
- For integration, ensure settings and localization are loaded as in production
© polyipseity, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/plugin-testing of polyipseity/obsidian-terminal.
Open the folder on GitHubat commit 8cbff89
Used in 2 other repositories
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in polyipseity/obsidian-terminal, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Plugin Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Plugin Testing this skillpolyipseity/obsidian-terminal | 948 | — | ~828 | Automated safety check: Pass | AGPL-3.0 | |
| Create Modulecartography-cncf/cartography | 4.1k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| Td Integration Testmarcus/td | 250 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Integration E2E Testingshinpr/claude-code-workflows | 690 | — | ~3.5k | Automated safety check: Pass | MIT | |
| JS-in-HTML Testingliaohch3/claude-tap | 3.3k | — | ~924 | Automated safety check: Pass | MIT | |
| Crosvm Testinggoogle/crosvm | 1.3k | — | ~847 | Automated safety check: Pass | BSD-3-Clause |
Similar skills
Td Integration Test
marcus/td
Write integration tests for the td-sync admin API using the TestHarness in internal/api/testharnesstest.go.
Integration E2E Testing
shinpr/claude-code-workflows
Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria.
JS-in-HTML Testing
liaohch3/claude-tap
Tests JavaScript embedded in an HTML file in two layers: pytest checks of the logic ported to Python, and Playwright runs in a real browser for the DOM.
- Official
Crosvm Testing
google/crosvm
Skill to assist with running tests and managing test VMs in the crosvm repository.
Add Acceptance Test
talkincode/toughradius
Write CI-executable acceptance/integration tests for protocol or end-to-end changes (TR-F022).
More from polyipseity/obsidian-terminal
Code Review
polyipseity/obsidian-terminal
A skill your agent uses when reviewing PRs, code changes, or conducting code audits in obsidian-terminal.
Related
Works with
Categories
Questions about Plugin Testing
What does Plugin Testing do?
Skill for testing Obsidian plugin features in this repository. Plugin Testing is an agent skill from polyipseity/obsidian-terminal. Skill for testing Obsidian plugin features in this repository.
When should I use Plugin Testing?
Plugin Testing fits situations like: integration test workflows specific to Obsidian plugins; tasks that involve Integration testing.
How do I install Plugin Testing in Claude Code?
Run `npx skills add polyipseity/obsidian-terminal --skill plugin-testing -a claude-code`. Or copy the skill folder (.agents/skills/plugin-testing in polyipseity/obsidian-terminal) into .claude/skills/plugin-testing in your project. Claude Code loads it when a task matches its description.
How do I install Plugin Testing in Codex?
Run `npx skills add polyipseity/obsidian-terminal --skill plugin-testing -a codex`. Or copy the skill folder (.agents/skills/plugin-testing in polyipseity/obsidian-terminal) into .agents/skills/plugin-testing in your project. Codex loads it when a task matches its description.
Can I use Plugin Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add polyipseity/obsidian-terminal --skill plugin-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plugin-testing, .gemini/skills/plugin-testing, .github/skills/plugin-testing and .opencode/skills/plugin-testing in your project.
What does Plugin Testing need to run?
Going by SKILL.md and its folder, Plugin Testing needs the command-line tools its instructions call (bun).
Does Plugin Testing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Plugin Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Plugin Testing use?
Plugin Testing is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Plugin Testing use?
About 828 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Plugin Testing?
Skills that share tags, products or a category with Plugin Testing: Create Module (cartography-cncf/cartography, 4.1k stars), Td Integration Test (marcus/td, 250 stars), Integration E2E Testing (shinpr/claude-code-workflows, 690 stars) and JS-in-HTML Testing (liaohch3/claude-tap, 3.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Plugin Testing?
polyipseity (a GitHub user) maintains it in polyipseity/obsidian-terminal, which has 948 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 3, 2026.
Source: polyipseity/obsidian-terminal on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.