feat: improve skill quality scores across 4 skills

Ran skills through tessl evaluation tooling and applied targeted
improvements to structure, conciseness, and workflow clarity.

| Skill             | Before | After | Change |
|-------------------|--------|-------|--------|
| defuddle          |  100%  | 100%  |   --   |
| json-canvas       |   83%  | 100%  |  +17%  |
| obsidian-bases    |   83%  | 100%  |  +17%  |
| obsidian-cli      |   94%  | 100%  |   +6%  |
| obsidian-markdown |   71%  |  94%  |  +23%  |

Changes:
- Add structured workflows with validation steps
- Extract verbose reference tables to references/ files (progressive disclosure)
- Remove standard Markdown content Claude already knows (obsidian-markdown)
- Add troubleshooting section for common YAML/formula errors (obsidian-bases)
- Restructure plugin dev section into numbered test cycle (obsidian-cli)
- Condense redundant examples, keep one per pattern

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Alan Pope
2026-02-25 11:32:59 +00:00
parent be978124b8
commit 5a557ceba7
9 changed files with 942 additions and 1245 deletions
+23 -20
View File
@@ -61,11 +61,29 @@ Use `--copy` on any command to copy output to clipboard. Use `silent` to prevent
## Plugin development
Reload a plugin after code changes — essential for the develop/test cycle:
### Develop/test cycle
```bash
obsidian plugin:reload id=my-plugin
```
After making code changes to a plugin or theme, follow this workflow:
1. **Reload** the plugin to pick up changes:
```bash
obsidian plugin:reload id=my-plugin
```
2. **Check for errors** — if errors appear, fix and repeat from step 1:
```bash
obsidian dev:errors
```
3. **Verify visually** with a screenshot or DOM inspection:
```bash
obsidian dev:screenshot path=screenshot.png
obsidian dev:dom selector=".workspace-leaf" text
```
4. **Check console output** for warnings or unexpected logs:
```bash
obsidian dev:console level=error
```
### Additional developer commands
Run JavaScript in the app context:
@@ -73,24 +91,9 @@ Run JavaScript in the app context:
obsidian eval code="app.vault.getFiles().length"
```
Check for errors and console output:
Inspect CSS values:
```bash
obsidian dev:errors
obsidian dev:console
obsidian dev:console level=error
```
Take a screenshot for visual testing:
```bash
obsidian dev:screenshot path=screenshot.png
```
Inspect DOM and CSS:
```bash
obsidian dev:dom selector=".workspace-leaf" text
obsidian dev:css selector=".workspace-leaf" prop=background-color
```