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
Tasker task XML with variable set and flash actions
Correct file suffix
100%
100%
TaskerData root node
40%
100%
Task sr attribute format
50%
100%
Variable Set action code
100%
100%
Flash action code
0%
100%
Str value as text content
100%
100%
Variable % prefix preserved
100%
100%
Int literals use val attribute
100%
100%
Four actions present
100%
100%
Tasker project XML with time-triggered profile
Correct file suffix
100%
100%
TaskerData root node
50%
100%
Project sr="proj0"
0%
100%
Project has cdate
0%
100%
Profile sr naming
0%
100%
Task sr naming
0%
100%
Profile links task by id
0%
100%
Project pids contains numeric id
0%
100%
Project tids contains numeric id
0%
100%
Internally consistent ids
0%
100%
Time context present
62%
100%
Multi-match email extraction in Tasker XML
Correct file suffix
100%
100%
TaskerData skeleton
100%
100%
Task sr naming
100%
100%
Correct VSR action code
0%
0%
All-match strategy
100%
100%
Str text content encoding
100%
100%
Variable % prefix retained
100%
100%
No invented argument layout
62%
75%
notes.txt explains first-match limitation
66%
100%
Flash action present
100%
100%
Int boolean encoding
100%
100%
Internally consistent ids
100%
100%
Tasker task XML that pushes a Custom layout to a Widget v2 (code 461)
Correct file suffix
100%
100%
TaskerData skeleton
33%
100%
Task sr naming
0%
100%
Widget v2 action code
0%
100%
Layout selector is Custom
0%
100%
Layout JSON in arg13
0%
100%
Widget name in arg1
12%
100%
Scrolling Column root
20%
100%
Button uses text key
90%
100%
Button runs task with taskVariables
25%
100%
Str value as text content
100%
100%