CtrlK
BlogDocsLog inGet started
Tessl Logo

finkel/tasker-xml-authoring

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

1.31x
Quality

97%

Does it follow best practices?

Impact

97%

1.31x

Average score across 4 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-1/

Greeting Builder Task

Problem Description

A developer is building a personal automation suite for their Android phone using Tasker. They want to create a task that assembles a full greeting from two stored name pieces, then pops up the combined result on screen. They have already set up several other automations and are now ready to add this one.

The task should set a first name and last name into separate variables, combine them into a third variable, and then display the combined greeting on the screen using a flash notification.

The Tasker task needs to work reliably when imported — meaning the XML must conform exactly to what the Tasker app expects when reading a task export file. The developer will import the file directly using Tasker's import feature.

Output Specification

Produce a single Tasker task export file named greeting_builder (with the appropriate file extension for a task export) containing a task called "Greeting Builder" with four actions in order:

  1. Set a variable for first name to the value Alice
  2. Set a variable for last name to the value Smith
  3. Set a variable for full name by combining the first and last name variables (with a space between them)
  4. Flash the full name variable to the screen

The file must be importable into the Tasker Android app via its standard import menu.

tile.json