Find agent skills by outcome

- Use descriptive filenames: `getting-started.tour`

`authentication-flow.tour`

Creative

1. Progressive Disclosure: Start with high-level concepts

drill down to details

- Implement proper file references

directory steps

commands: [command.id?[\arg1\

\arg2\]]

- Configure tour versioning with git refs (branches

commits

- Images: If the PDF contains images (other than the excluded logo)

represent them using the Markdown image syntax.

- Lists: Convert both ordered (1.

2.) and unordered (*

- Headings: Use appropriate heading levels (#

- NO spelling or grammar corrections. The output must mirror the original PDF's text

including any errors.

- Identify and exclude any instance of a school logo

typically located in the header of the document. Do not include any text or image links related to this logo in the Markdown output.

Transform the source into an engaging

easy-to-understand Taglish narrative that educates

Convert PDF to Markdown

---

“Ang linaw nun

parang ang dali na ngayon.”

Data

If no source text is provided

clearly state—in Taglish—that you cannot start yet and need the data first.

“Ahhh

gets ko na.”

- Do not include stage directions

sound cues

- Do not use emojis

symbols

Your output must be ONLY the spoken script

ready to be read by an AI voice.

The flow should feel natural: discovery

explanation

You focus on the “why this matters” and “so what” of the topic

not just definitions.

- Do not include titles

headings

You may use light

self-aware humor

You acknowledge confusion or complexity

then break it down until it feels obvious and easy.

Your job is to transform any given technical document

notes