Author and edit Android Tasker XML (tasks, profiles, projects, scenes) for import into the Tasker app — node skeleton, action codes, and per-arg encoding.
97
97%
Does it follow best practices?
Impact
97%
1.31xAverage score across 4 eval scenarios
Passed
No known issues
A small support team uses Tasker on Android to automate processing of incoming notification blobs. One recurring job is pulling every email address out of a raw text string — for example, a forwarded message that contains multiple contact addresses mixed into a paragraph of prose. The team lead wants a reusable Tasker task that can take any such text (held in a Tasker variable), find every email address in it, and make all of the extracted addresses available so a follow-up action (e.g., a List Dialog or a Flash) can show them.
The tricky part is that real messages typically contain several addresses, not just one, so the extraction must collect all of them — not just the first hit. The team already has a Tasker setup and knows the action they want to use for pattern matching, but has run into trouble getting all results back. Your job is to produce a working Tasker task XML file that solves this correctly.
Produce the following files in your working directory:
ExtractEmails.tsk.xml — A valid Tasker task export file for a task called "Extract Emails". Save it with the correct file extension for a Tasker task export. The task should:
"Contact alice@example.com or bob@test.org or carol@demo.net for details." to the variable %inputText.%inputText and collect them so they are all available (not just the first one found).notes.txt — A short plain-text file (a few sentences) explaining the approach used to collect all email addresses and why a single pattern-match action might not be sufficient on its own for getting every address from the text.
Keep any intermediate files small; do not leave large files in the working directory.