Create Tasker profiles and tasks via XML for Android automation. Use when adding new Tasker functionality, creating Intent Received handlers, or building automation that integrates with the rho.tasker extension.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Create Tasker profiles and tasks via XML for Android automation. Use when adding new Tasker functionality, creating Intent Received handlers, or building automation that integrates with the rho.tasker extension.
Tasker XML Creation
Create importable Tasker profiles and tasks via XML files.
Output Location
Write XML files to /storage/emulated/0/Download/ for easy import:
/storage/emulated/0/Download/MyProfile.prf.xml
File Suffixes
.prf.xml - Profile with linked task(s)
.tsk.xml - Standalone task
.prj.xml - Full project
Import Instructions
Open Tasker app
For profiles: Long press PROFILES tab → Import Profile
For tasks: Long press TASKS tab → Import Task
Navigate to Download folder, select the XML file
XML Structure
Basic Profile with Task
<?xml version="1.0" encoding="UTF-8"?><TaskerDatasr=""dvi="1"tv="6.3.13"><Profilesr="prof1"ve="2"><cdate>1706900000000
1706900000000
1
1
Profile Name
1706900000000
1706900000000
1
Task Name
6
</cdate>
<edate>
</edate>
<id>
</id>
<mid0>
</mid0>
<nme>
</nme>
<!-- Event/State goes here -->
</Profile>
<Tasksr="task1">
<cdate>
</cdate>
<edate>
</edate>
<id>
</id>
<nme>
</nme>
<pri>
</pri>
<!-- Actions go here -->
</Task>
</TaskerData>
Important: Profile <mid0> must match Task <id>.
Event Codes (for Profile triggers)
Use inside <Profile> with <Event sr="con0" ve="2">:
<Actionsr="act0"ve="7"><code>410</code><Strsr="arg0"ve="3">/storage/emulated/0/rho/result.txt</Str><Strsr="arg1"ve="3">Content to write
Can be multiline
Variables work: %myvar</Str><Intsr="arg2"val="0"/><Intsr="arg3"val="0"/><Intsr="arg4"val="0"/></Action>
<!-- If %direction equals "down" --><Actionsr="act0"ve="7"><code>37</code><Strsr="arg0"ve="3">%direction</Str><Intsr="arg1"val="0"/><Strsr="arg2"ve="3">down</Str><Intsr="arg3"val="0"/></Action><!-- Actions for down --><Actionsr="act1"ve="7"><code>43</code></Action><!-- Else actions --><Actionsr="act2"ve="7"><code>38</code></Action>
Rho Integration Pattern
For rho.tasker.* handlers, use this standard pattern:
<?xml version="1.0" encoding="UTF-8"?><TaskerDatasr=""dvi="1"tv="6.3.13"><Profilesr="prof1"ve="2"><cdate>1706900000000</cdate><edate>1706900000000</edate><id>1</id><mid0>1</mid0><nme>Rho Action Name</nme><Eventsr="con0"ve="2"><code>599</code><Strsr="arg0"ve="3">rho.tasker.action_name</Str><Intsr="arg1"val="0"/><Intsr="arg2"val="0"/><Strsr="arg3"ve="3"/><Strsr="arg4"ve="3"/></Event></Profile><Tasksr="task1"><cdate>1706900000000</cdate><edate>1706900000000</edate><id>1</id><nme>Rho Action Handler</nme><pri>6</pri><!-- A1: Get result_file from intent --><Actionsr="act0"ve="7"><code>547</code><Strsr="arg0"ve="3">%result_file</Str><Strsr="arg1"ve="3">%result_file</Str><Intsr="arg2"val="0"/><Intsr="arg3"val="0"/><Intsr="arg4"val="0"/><Intsr="arg5"val="3"/><Intsr="arg6"val="0"/></Action><!-- A2: Do the actual work here --><!-- A3: AutoInput UI Query to get screen state --><Actionsr="act1"ve="7"><code>-1</code><Bundlesr="arg0"><Valssr="val"><com.twofortyfouram.locale.intent.extra.BLURB>Check Screen
Configuration: Check Screen</com.twofortyfouram.locale.intent.extra.BLURB><com.twofortyfouram.locale.intent.extra.BLURB-type>java.lang.String</com.twofortyfouram.locale.intent.extra.BLURB-type><net.dinglisch.android.tasker.subbundled>true</net.dinglisch.android.tasker.subbundled><net.dinglisch.android.tasker.subbundled-type>java.lang.Boolean</net.dinglisch.android.tasker.subbundled-type></Vals></Bundle><Strsr="arg1"ve="3">com.joaomgcd.autoinput</Str><Strsr="arg2"ve="3">com.joaomgcd.autoinput.activity.ActivityConfigUIQuery</Str><Intsr="arg3"val="600"/></Action><!-- A4: Write result file in standard format --><Actionsr="act2"ve="7"><code>410</code><Strsr="arg0"ve="3">%result_file</Str><Strsr="arg1"ve="3">%aiapp
~~~
%aicoords()
~~~
%aiid()
~~~
%aitext()
~~~
%err</Str><Intsr="arg2"val="0"/><Intsr="arg3"val="0"/><Intsr="arg4"val="0"/></Action></Task></TaskerData>
Result File Format
The rho.tasker extension expects results in this format:
