Find agent skills by outcome

| `[!example]` | Code examples

demonstrations |

| `[!question]` | Rhetorical questions

things to think about |

| `[!abstract]` | Summaries

TL;DR |

- No casual filler (let's look at...

so basically...)

- Use status values other than: `TODO`

`WIP`

- Use consistent heading hierarchy (H2 for sections

H3 for subsections)

- Capture all explanations

examples

- Notes must be scannable

rereadable

- Professional

clear

You are running inside AI Blaze

a browser extension. Your input is:

transcript_to_notes

---

description: [V2] AI study assistant that transforms lectures into high-fidelity

structured notes. Optimized for AI Blaze with strict YAML schema

## Listener-First

Time-Optimized

costume: Patchwork leather vest

welding goggles around neck

subject_expression: Squinting against the sun

gritted teeth showing exertion.

subject_expression: Alert and scanning the horizon

eyes wide with intense focus.

subject_action: Pointing towards a distant gap in the scrap heaps

signaling a safe path forward.

costume: Layers of desert linen wraps

makeshift shoulder armor made from a rusted license plate

Harsh

directional desert sunlight

camera_angle: Low-angle medium close-up

emphasizing the scale of the junk piles behind them.

environmental_elements: Tumbleweeds made of wire

shimmering heat haze distorting the background

*If all checks pass

proceed to generate the requested prompt immediately.*

Writing

- Is Markdown used for content hierarchy (H2

H3)?

- Are XML tags used for containers (`<context>`

`<rules>`)?