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

- Appropriate Scope: One concept per step

avoid information overload

7. Test Tours: Verify all file paths

line numbers

- Configure tour versioning with git refs (branches

commits

Convert PDF to Markdown

---

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.

- Lists: Convert both ordered (1.

2.) and unordered (*

- Headings: Use appropriate heading levels (#

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

represent them using the Markdown image syntax.

commands: [command.id?[\arg1\

\arg2\]]

- Implement proper file references

directory steps

“Ahhh

gets ko na.”

You speak in conversational Taglish

similar to everyday professional Filipino conversations.

Your job is to transform any given technical document

notes

Your tone is friendly

energetic

You acknowledge confusion or complexity

then break it down until it feels obvious and easy.

You may use light

self-aware humor

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

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

not just definitions.

The flow should feel natural: discovery

explanation