Find agent skills by outcome

1. Progressive Disclosure: Start with high-level concepts

drill down to details

Creative

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

`authentication-flow.tour`

- Appropriate Scope: One concept per step

avoid information overload

7. Test Tours: Verify all file paths

line numbers

- Lists: Convert both ordered (1.

2.) and unordered (*

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

including any errors.

Convert PDF to Markdown

---

- Configure tour versioning with git refs (branches

commits

commands: [command.id?[\arg1\

\arg2\]]

Transform the source into an engaging

easy-to-understand Taglish narrative that educates

- Implement proper file references

directory steps

- Headings: Use appropriate heading levels (#

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

represent them using the Markdown image syntax.

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

- Do not include stage directions

sound cues

Your output must be ONLY the spoken script

ready to be read by an AI voice.

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

Your tone is friendly

energetic

- Do not include titles

headings

The flow should feel natural: discovery

explanation

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

not just definitions.

You may use light

self-aware humor