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
@@ -0,0 +1,58 @@
# Callouts Reference
## Basic Callout
```markdown
> [!note]
> This is a note callout.
> [!info] Custom Title
> This callout has a custom title.
> [!tip] Title Only
```
## Foldable Callouts
```markdown
> [!faq]- Collapsed by default
> This content is hidden until expanded.
> [!faq]+ Expanded by default
> This content is visible but can be collapsed.
```
## Nested Callouts
```markdown
> [!question] Outer callout
> > [!note] Inner callout
> > Nested content
```
## Supported Callout Types
| Type | Aliases | Color / Icon |
|------|---------|-------------|
| `note` | - | Blue, pencil |
| `abstract` | `summary`, `tldr` | Teal, clipboard |
| `info` | - | Blue, info |
| `todo` | - | Blue, checkbox |
| `tip` | `hint`, `important` | Cyan, flame |
| `success` | `check`, `done` | Green, checkmark |
| `question` | `help`, `faq` | Yellow, question mark |
| `warning` | `caution`, `attention` | Orange, warning |
| `failure` | `fail`, `missing` | Red, X |
| `danger` | `error` | Red, zap |
| `bug` | - | Red, bug |
| `example` | - | Purple, list |
| `quote` | `cite` | Gray, quote |
## Custom Callouts (CSS)
```css
.callout[data-callout="custom-type"] {
--callout-color: 255, 0, 0;
--callout-icon: lucide-alert-circle;
}
```
@@ -0,0 +1,63 @@
# Embeds Reference
## Embed Notes
```markdown
![[Note Name]]
![[Note Name#Heading]]
![[Note Name#^block-id]]
```
## Embed Images
```markdown
![[image.png]]
![[image.png|640x480]] Width x Height
![[image.png|300]] Width only (maintains aspect ratio)
```
## External Images
```markdown
![Alt text](https://example.com/image.png)
![Alt text|300](https://example.com/image.png)
```
## Embed Audio
```markdown
![[audio.mp3]]
![[audio.ogg]]
```
## Embed PDF
```markdown
![[document.pdf]]
![[document.pdf#page=3]]
![[document.pdf#height=400]]
```
## Embed Lists
```markdown
![[Note#^list-id]]
```
Where the list has a block ID:
```markdown
- Item 1
- Item 2
- Item 3
^list-id
```
## Embed Search Results
````markdown
```query
tag:#project status:done
```
````
@@ -0,0 +1,61 @@
# Properties (Frontmatter) Reference
Properties use YAML frontmatter at the start of a note:
```yaml
---
title: My Note Title
date: 2024-01-15
tags:
- project
- important
aliases:
- My Note
- Alternative Name
cssclasses:
- custom-class
status: in-progress
rating: 4.5
completed: false
due: 2024-02-01T14:30:00
---
```
## Property Types
| Type | Example |
|------|---------|
| Text | `title: My Title` |
| Number | `rating: 4.5` |
| Checkbox | `completed: true` |
| Date | `date: 2024-01-15` |
| Date & Time | `due: 2024-01-15T14:30:00` |
| List | `tags: [one, two]` or YAML list |
| Links | `related: "[[Other Note]]"` |
## Default Properties
- `tags` - Note tags (searchable, shown in graph view)
- `aliases` - Alternative names for the note (used in link suggestions)
- `cssclasses` - CSS classes applied to the note in reading/editing view
## Tags
```markdown
#tag
#nested/tag
#tag-with-dashes
#tag_with_underscores
```
Tags can contain: letters (any language), numbers (not first character), underscores `_`, hyphens `-`, forward slashes `/` (for nesting).
In frontmatter:
```yaml
---
tags:
- tag1
- nested/tag2
---
```