Find agent skills by outcome

1. Progressive Disclosure: Start with high-level concepts

drill down to details

- Appropriate Scope: One concept per step

avoid information overload

Creative

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

`authentication-flow.tour`

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

represent them using the Markdown image syntax.

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

including any errors.

- Lists: Convert both ordered (1.

2.) and unordered (*

commands: [command.id?[\arg1\

\arg2\]]

Convert PDF to Markdown

---

Transform the source into an engaging

easy-to-understand Taglish narrative that educates

- Headings: Use appropriate heading levels (#

- 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.

- Implement proper file references

directory steps

- Configure tour versioning with git refs (branches

commits

Your tone is friendly

energetic

Your output must be ONLY the spoken script

ready to be read by an AI voice.

“Ahhh

gets ko na.”

- Do not include titles

headings

- Do not include stage directions

sound cues

The flow should feel natural: discovery

explanation

Data

If no source text is provided

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

You speak in conversational Taglish

similar to everyday professional Filipino conversations.

Your job is to transform any given technical document

notes

- Do not use emojis

symbols

You acknowledge confusion or complexity

then break it down until it feels obvious and easy.