CtrlK
BlogDocsLog inGet started
Tessl Logo

taskade

Taskade integration. Manage data, records, and automate workflows. Use when the user wants to interact with Taskade data.

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/taskade/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

The content is a well-structured, highly actionable CLI integration guide with copy-paste commands and a clear connection workflow including a polling feedback loop. Its only weaknesses are minor padding in the intro and some repetition of the action-discovery command.

DimensionReasoningScore

Conciseness

The body is mostly dense, executable commands with only minor padding (the 'Think of it as a more flexible... alternative' intro and a repeated `action list --intent=QUERY` example), fitting 'efficient; minor instances of over-explanation that could be trimmed' rather than the fully-lean score 5.

4 / 5

Actionability

It provides copy-paste-ready commands across install, login, connection, action search/run (with JSON input), and proxy requests, with concrete flags and a flag table covering the common cases, matching the 'fully executable; copy-paste ready' anchor.

5 / 5

Workflow Clarity

The connection flow is a clear sequence (ensure -> poll with --wait -> state-based decision tree -> re-poll after CLIENT_ACTION_REQUIRED) with an explicit feedback loop, matching 'clear sequence with most checkpoints present'; it stops short of a full validate-fix-retry checklist that would merit 5.

4 / 5

Progressive Disclosure

It is a single self-contained file with clear section headers and a pointer to official docs, no nested references; at ~140 lines it exceeds the under-50-line simple-skill exception, so it lands at 'good structure; references mostly clear; minor organization gaps' rather than 5.

4 / 5

Total

17

/

20

Passed

Description

62%Weight 40%Scale 1-5

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

The description covers both what and when but leans on generic verbs ('manage data, records') and a single trigger keyword ('Taskade'), missing the natural task/project vocabulary users would say. It is distinct as a niche but would benefit from more specific capabilities and trigger synonyms.

Suggestions

Replace generic verbs with concrete Taskade capabilities, e.g. 'Create and manage projects, tasks, and subtasks; automate workflows'.

Expand the 'Use when' clause with natural trigger terms users actually say: 'tasks, projects, subtasks, notes, or Taskade workspaces'.

Tighten the opening so the skill's distinct value (Taskade data interaction via Membrane) is stated in one concrete phrase.

DimensionReasoningScore

Specificity

Names the domain (Taskade) and a couple of actions ('manage data, records, and automate workflows') but the actions are generic and coverage is not comprehensive, matching the 'names domain and 1-2 concrete actions' anchor rather than the more specific score 4.

3 / 5

Completeness

Both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Taskade data') are present, but the 'when' clause is generic, matching the 'has both what and when; when could be more explicit' anchor rather than the concrete-trigger score 5.

4 / 5

Trigger Term Quality

The only natural term is 'Taskade' in 'interact with Taskade data'; it lacks the common variations users actually say (tasks, projects, notes, workspace), fitting 'some relevant keywords but missing common variations' rather than the fuller coverage of score 4.

3 / 5

Distinctiveness Conflict Risk

'Taskade integration' carves a clear, distinct niche unlikely to trigger the wrong skill, but the generic action phrasing leaves minor overlap risk with other productivity integrations, so it sits at 'mostly distinct' rather than the minimal-conflict score 5.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.