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`

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

including any errors.

Transform the source into an engaging

easy-to-understand Taglish narrative that educates

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

represent them using the Markdown image syntax.

Convert PDF to Markdown

---

- Configure tour versioning with git refs (branches

commits

- Implement proper file references

directory steps

commands: [command.id?[\arg1\

\arg2\]]

- Headings: Use appropriate heading levels (#

- Lists: Convert both ordered (1.

2.) and unordered (*

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

headings

The flow should feel natural: discovery

explanation

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.

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

not just definitions.

You may use light

self-aware humor

You acknowledge confusion or complexity

then break it down until it feels obvious and easy.

“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