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

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is an excellent, highly specialized skill that addresses a genuinely underdocumented domain (Tasker XML action encoding). Its greatest strength is the clear safety principle — never guess argument layouts — reinforced throughout with concrete examples and a comprehensive mistakes table. The content is dense but every section provides non-obvious, actionable knowledge that Claude wouldn't have from training data alone.

DimensionReasoningScore

Conciseness

The content is dense and efficient. It assumes Claude's competence with XML and programming concepts, never explains what XML is or how Android works. Every section earns its place — the common mistakes table, encoding rules, and skeleton are all non-obvious domain knowledge that Claude wouldn't have. The repeated emphasis on 'don't guess arg layouts' is warranted given it's the core safety principle.

3 / 3

Actionability

Provides fully executable XML examples (file skeleton, action encoding, complete Morning.tsk.xml), specific tag formats with exact attribute names, a concrete workflow, and a detailed common mistakes table with fixes. The encoding rules table with exact syntax for Str/Int/App/Bundle is copy-paste ready. The guidance to export-and-copy rather than guess is itself a concrete, actionable instruction.

3 / 3

Workflow Clarity

The 4-step 'Reliable Workflow' section is clearly sequenced with an implicit validation checkpoint (step 4: import to verify). The core safety principle — never guess argument layouts, always export from the app — serves as a validation feedback loop. The common mistakes table acts as a pre-flight checklist. For a domain where the primary risk is silent misbehavior from wrong arg order, the workflow appropriately emphasizes verification.

3 / 3

Progressive Disclosure

References to external files (references/tasker-xml-codes.md, references/confirmed-arg-layouts.md) are well-signaled and one level deep, which is good. However, no bundle files were provided, so we can't verify these references exist. The SKILL.md itself is fairly long (~180 lines) but the content density justifies inline placement. The external upstream repo link is appropriate. Could benefit from slightly clearer section navigation for the amount of content present.

2 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that clearly defines a narrow, specific domain (Android Tasker XML files) with comprehensive trigger terms including file extensions and Tasker-specific terminology. It opens with an explicit 'Use when' clause, lists concrete capabilities, and occupies a highly distinctive niche that minimizes conflict risk with other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'hand-writing, generating, or editing Android Tasker XML files', and specifies concrete structural elements like 'TaskerData node skeleton, numeric action codes, and per-argument Str/Int/App encoding'.

3 / 3

Completeness

Clearly answers both 'what' (generating/editing Tasker XML files covering TaskerData skeleton, action codes, argument encoding) and 'when' (explicit 'Use when' clause specifying hand-writing, generating, or editing Tasker XML files for import into the Tasker app).

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'Tasker', 'XML', specific file extensions (.tsk.xml, .prf.xml, .prj.xml, .scn.xml), 'tasks', 'profiles', 'projects', 'scenes', 'backup', 'Android', and 'Tasker app'. These are exactly the terms a user working with Tasker would use.

3 / 3

Distinctiveness Conflict Risk

Extremely distinct niche — Android Tasker XML is a very specific domain with unique file extensions and terminology. Virtually no risk of conflicting with other skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents