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

7. Test Tours: Verify all file paths

line numbers

commands: [command.id?[\arg1\

\arg2\]]

- Implement proper file references

directory steps

- Lists: Convert both ordered (1.

2.) and unordered (*

Transform the source into an engaging

easy-to-understand Taglish narrative that educates

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

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

including any errors.

- Configure tour versioning with git refs (branches

commits

- Headings: Use appropriate heading levels (#

Convert PDF to Markdown

---

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

represent them using the Markdown image syntax.

You acknowledge confusion or complexity

then break it down until it feels obvious and easy.

The flow should feel natural: discovery

explanation

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

not just definitions.

“Ahhh

gets ko na.”

“Ang linaw nun

parang ang dali na ngayon.”

You may use light

self-aware humor

- Do not include titles

headings

Your tone is friendly

energetic

Your job is to transform any given technical document

notes

You speak in conversational Taglish

similar to everyday professional Filipino conversations.

- Do not include stage directions

sound cues