Ckeditor5 Testing
TriliumNext/Trilium
Testing CKEditor 5 plugins in the Trilium monorepo. An agent skill from TriliumNext/Trilium.
Set up a fast Obsidian plugin development loop with hot reload.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill obsidian-local-dev-loop -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace obsidian-local-dev-loop --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/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/obsidian-local-dev-loop .claude/skills/obsidian-local-dev-loop && 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 "obsidian-local-dev-loop" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/obsidian-local-dev-loop into .claude/skills/obsidian-local-dev-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-local-dev-loop", 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/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/obsidian-local-dev-loopType 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 jeremylongshore/tons-of-skills-marketplace --skill obsidian-local-dev-loop -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace obsidian-local-dev-loop --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/obsidian-local-dev-loop .agents/skills/obsidian-local-dev-loop && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "obsidian-local-dev-loop" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/obsidian-local-dev-loop into .agents/skills/obsidian-local-dev-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-local-dev-loop", 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 jeremylongshore/tons-of-skills-marketplace --skill obsidian-local-dev-loop -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace obsidian-local-dev-loop --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/obsidian-local-dev-loop .cursor/skills/obsidian-local-dev-loop && 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 "obsidian-local-dev-loop" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/obsidian-local-dev-loop into .cursor/skills/obsidian-local-dev-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-local-dev-loop", 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/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/obsidian-local-dev-loop--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 jeremylongshore/tons-of-skills-marketplace --skill obsidian-local-dev-loop -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace obsidian-local-dev-loop --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/obsidian-local-dev-loop .gemini/skills/obsidian-local-dev-loop && 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 "obsidian-local-dev-loop" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/obsidian-local-dev-loop into .gemini/skills/obsidian-local-dev-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-local-dev-loop", 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 jeremylongshore/tons-of-skills-marketplace obsidian-local-dev-loopInstalls 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 jeremylongshore/tons-of-skills-marketplace --skill obsidian-local-dev-loop -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/obsidian-local-dev-loop .github/skills/obsidian-local-dev-loop && 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 "obsidian-local-dev-loop" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/obsidian-local-dev-loop into .github/skills/obsidian-local-dev-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-local-dev-loop", 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 jeremylongshore/tons-of-skills-marketplace --skill obsidian-local-dev-loop -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace obsidian-local-dev-loop --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/obsidian-local-dev-loop .opencode/skills/obsidian-local-dev-loop && 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 "obsidian-local-dev-loop" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/obsidian-local-dev-loop into .opencode/skills/obsidian-local-dev-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-local-dev-loop", 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.
obsidian-local-dev-loopSet up a fast Obsidian plugin development loop with hot reload.
Obsidian Local Dev Loop is an agent skill from jeremylongshore/tons-of-skills-marketplace. Set up a fast Obsidian plugin development loop with hot reload. Covers cloning the sample plugin, esbuild watch mode, symlinking into a vault, Ctrl+R hot reload, Chrome DevTools debugging, and testing with vitest. Use when starting plugin development or configuring a dev environment. Trigger with "obsidian dev loop", "obsidian hot reload", "obsidian development setup", "develop obsidian plugin".
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/implementation-guide.md`). Compatibility notes: Designed for Claude Code
It sits in Testing & QA, covering Browser testing, Unit testing and Hooks and plugins. It works with Obsidian, Chrome DevTools and Vitest. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 80f86df. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBash(npm:*)Bash(pnpm:*)Bash(mkdir:*)Bash(ln:*)Bash(ls:*)GrepFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
npmnpxgitnodeFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comAlso links to:
docs.obsidian.mdesbuild.github.iovitest.devFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Obsidian Local Dev Loop loads about 2.4k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 106 tokens; SKILL.md has 638 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.
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.
The full file from jeremylongshore/tons-of-skills-marketplace at commit 80f86df, republished under its MIT licence (© jeremylongshore). 638 words, ~2,441 tokens.
.claude/skills/obsidian-local-dev-loop/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Establish a fast edit-build-test cycle for Obsidian plugins. Clone the official sample plugin, run esbuild in watch mode, symlink into a dev vault, hot-reload with Ctrl+R, debug with Chrome DevTools, and run tests with vitest. Aimed at sub-second feedback from save to reload.
Start from the maintained template rather than from scratch:
set -euo pipefail
git clone https://github.com/obsidianmd/obsidian-sample-plugin.git my-plugin
cd my-plugin
rm -rf .git
git init
npm installThe sample includes esbuild.config.mjs, tsconfig.json, manifest.json, and
a working src/main.ts.
Keep a vault just for testing. Pre-populate it with sample notes.
set -euo pipefail
DEV_VAULT="$HOME/ObsidianDev"
mkdir -p "$DEV_VAULT/.obsidian/plugins"
mkdir -p "$DEV_VAULT/Test Notes"
cat > "$DEV_VAULT/Test Notes/Sample.md" << 'EOF'
---
tags: [test, sample]
---
# Sample Note
This note exists for plugin development testing.
## Section A
Some content with a [[link]] and a #tag.
## Section B
- Item 1
- Item 2
- Item 3
EOF
echo "Dev vault ready at $DEV_VAULT"Open this vault in Obsidian: File > Open vault > select ~/ObsidianDev.
Instead of copying files after every build, symlink the entire project directory.
The build outputs main.js at the project root, right where Obsidian expects it.
set -euo pipefail
DEV_VAULT="$HOME/ObsidianDev"
PLUGIN_DIR="$(pwd)"
PLUGIN_ID=$(node -e "console.log(require('./manifest.json').id)")
# Symlink project root into vault plugins folder
ln -sfn "$PLUGIN_DIR" "$DEV_VAULT/.obsidian/plugins/$PLUGIN_ID"
# Verify
ls -la "$DEV_VAULT/.obsidian/plugins/$PLUGIN_ID/manifest.json"
echo "Symlinked $PLUGIN_ID into dev vault."On Windows, use an admin terminal:
mklink /D "%USERPROFILE%\ObsidianDev\.obsidian\plugins\my-plugin" "%cd%"Watch mode rebuilds main.js on every source file change (typically <50ms).
npm run dev
# esbuild watches src/ and rebuilds main.js on save
# Output: "build finished" messages in the terminalThe esbuild.config.mjs from the sample plugin already supports this.
Inline source maps are enabled in dev mode for accurate stack traces.
After esbuild rebuilds, reload the plugin in Obsidian:
Method A -- Keyboard (fastest):
Press Ctrl+R (or Cmd+R on macOS) to reload the app. This unloads all plugins
and reloads them, picking up the new main.js.
Method B -- Hot Reload plugin (automatic):
Install the Hot Reload community plugin.
It watches for main.js changes in plugin directories and auto-reloads only the
changed plugin. No manual refresh needed.
.hotreload file in your plugin directory: touch .hotreloadMethod C -- Command palette:
Press Ctrl+P, type "Reload app without saving", Enter.
Obsidian is an Electron app, so full Chrome DevTools are available.
Ctrl+Shift+I (or Cmd+Option+I on macOS) to open DevToolsconsole.log output from your pluginTips:
src/main.tsdebugger; statements in code for precise breakpointsconsole.log('[MyPlugin]', ...) prefix makes filtering easy// Add to onload() for development:
if (process.env.NODE_ENV !== "production") {
console.log("[MyPlugin] Dev mode active. Use Ctrl+Shift+I for DevTools.");
}Obsidian plugins can be unit-tested by mocking the obsidian module.
set -euo pipefail
npm install --save-dev vitestCreate vitest.config.ts:
import { defineConfig } from "vitest/config";
export default defineConfig({
test: {
globals: true,
environment: "node",
},
});Create a mock for the obsidian module at __mocks__/obsidian.ts:
export class Plugin {
app = {};
loadData = vi.fn().mockResolvedValue({});
saveData = vi.fn().mockResolvedValue(undefined);
addCommand = vi.fn();
addRibbonIcon = vi.fn();
addSettingTab = vi.fn();
addStatusBarItem = vi.fn().mockReturnValue({ setText: vi.fn() });
registerEvent = vi.fn();
registerInterval = vi.fn();
}
export class Notice {
constructor(public message: string) {}
}
export class PluginSettingTab {
containerEl = { empty: vi.fn(), createEl: vi.fn() };
constructor(public app: any, public plugin: any) {}
display() {}
}
export class Setting {
constructor(el: any) {}
setName = vi.fn().mockReturnThis();
setDesc = vi.fn().mockReturnThis();
addText = vi.fn().mockReturnThis();
addToggle = vi.fn().mockReturnThis();
}
export class Modal {
app: any;
contentEl = { createEl: vi.fn(), empty: vi.fn() };
constructor(app: any) { this.app = app; }
open = vi.fn();
close = vi.fn();
onOpen() {}
onClose() {}
}Write a test:
// src/__tests__/main.test.ts
import { describe, it, expect, vi } from "vitest";
vi.mock("obsidian");
describe("Plugin settings", () => {
it("merges defaults with saved data", async () => {
const { Plugin } = await import("obsidian");
const { default: MyPlugin } = await import("../main");
const plugin = new MyPlugin() as any;
plugin.loadData = vi.fn().mockResolvedValue({ greeting: "Custom" });
plugin.saveData = vi.fn();
await plugin.loadSettings();
expect(plugin.settings.greeting).toBe("Custom");
expect(plugin.settings.showRibbon).toBe(true); // default preserved
});
});Run tests:
npx vitest run # single run
npx vitest --watch # watch mode alongside npm run devAdd to package.json:
{
"scripts": {
"dev": "node esbuild.config.mjs",
"build": "node esbuild.config.mjs production",
"test": "vitest run",
"test:watch": "vitest --watch"
}
}After completing all steps:
~/ObsidianDev with test notesnpm run dev for sub-second rebuilds on savenpm run dev, terminal 2 runs npx vitest --watch| Error | Cause | Fix |
|---|---|---|
| Symlink not working | Permission denied (Windows) | Run terminal as Administrator |
| Plugin not in list | Symlink target wrong | Verify ls -la shows correct target |
| Hot Reload not triggering | Missing .hotreload file | touch .hotreload in plugin dir |
| Source maps not showing | sourcemap: false in config | Set sourcemap: "inline" for dev |
| Build not watching | Used build instead of dev | Run npm run dev (watch mode) |
| Tests fail with import errors | Missing vitest mock | Create __mocks__/obsidian.ts |
| DevTools won't open | Keyboard shortcut conflict | Use menu: View > Toggle Developer Tools |
Quick dev startup script (dev.sh):
#!/usr/bin/env bash
set -euo pipefail
# Terminal 1: esbuild watch
npm run dev &
ESBUILD_PID=$!
# Terminal 2: vitest watch
npx vitest --watch &
VITEST_PID=$!
echo "Dev servers running. Ctrl+C to stop."
trap "kill $ESBUILD_PID $VITEST_PID" EXIT
waitVSCode task for integrated dev:
{
"version": "2.0.0",
"tasks": [{
"label": "Obsidian Dev",
"type": "npm",
"script": "dev",
"isBackground": true,
"problemMatcher": {
"pattern": { "regexp": "^x]$" },
"background": {
"activeOnStart": true,
"beginsPattern": ".",
"endsPattern": "build finished"
}
}
}]
}obsidian-core-workflow-bobsidian-sdk-patterns© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (references) in skills/.curated/obsidian-local-dev-loop of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit 80f86df
Obsidian Local Dev Loop 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 |
|---|---|---|---|---|---|---|
| Obsidian Local Dev Loop this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Ckeditor5 TestingTriliumNext/Trilium | 38k | — | ~3.3k | Automated safety check: Pass | AGPL-3.0 | |
| Chrome Devtools MCPmanagedcode/dotnet-skills | 486 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Control UI E2Eopenclaw/openclaw | 392k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Check Visual Changesigrlk/storybook-addon-test-codegen | 154 | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Svelte Testingspences10/sveltest | 113 | — | ~579 | Automated safety check: Pass | MIT |
TriliumNext/Trilium
Testing CKEditor 5 plugins in the Trilium monorepo. An agent skill from TriliumNext/Trilium.
managedcode/dotnet-skills
Use Chrome DevTools MCP from .NET agents and .NET-focused repos to inspect, debug, and automate Chrome through an MCP client.
openclaw/openclaw
A skill your agent uses when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks…
igrlk/storybook-addon-test-codegen
Check the visual impact of an edit mid-task with uiverify check — render just the components you're touching on the UI Verify fleet and diff them against the real CI baseline, without opening a PR…
spences10/sveltest
Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright.
chongdashu/vibejam-starter-pack
Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Works with
Categories
Set up a fast Obsidian plugin development loop with hot reload. Obsidian Local Dev Loop is an agent skill from jeremylongshore/tons-of-skills-marketplace. Set up a fast Obsidian plugin development loop with hot reload.
Obsidian Local Dev Loop fits situations like: starting plugin development; configuring a dev environment; with obsidian dev loop; obsidian hot reload.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill obsidian-local-dev-loop -a claude-code`. Or copy the skill folder (skills/.curated/obsidian-local-dev-loop in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/obsidian-local-dev-loop in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill obsidian-local-dev-loop -a codex`. Or copy the skill folder (skills/.curated/obsidian-local-dev-loop in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/obsidian-local-dev-loop in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill obsidian-local-dev-loop -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/obsidian-local-dev-loop, .gemini/skills/obsidian-local-dev-loop, .github/skills/obsidian-local-dev-loop and .opencode/skills/obsidian-local-dev-loop in your project.
Going by SKILL.md and its folder, Obsidian Local Dev Loop needs the command-line tools its instructions call (npm, npx, git and node). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(npm:*), Bash(pnpm:*), Bash(mkdir:*), Bash(ln:*), Bash(ls:*), Grep. Compatibility (from SKILL.md): Designed for Claude Code.
SKILL.md names 4 domains. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. As links in the text: docs.obsidian.md, esbuild.github.io and vitest.dev. This is read from the text; nothing was executed.
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.
Obsidian Local Dev Loop is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.4k tokens (SKILL.md is roughly 9.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 876 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Obsidian Local Dev Loop: Ckeditor5 Testing (TriliumNext/Trilium, 38k stars), Chrome Devtools MCP (managedcode/dotnet-skills, 486 stars), Control UI E2E (openclaw/openclaw, 392k stars) and Check Visual Changes (igrlk/storybook-addon-test-codegen, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,825 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 9, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.