Name: meistertask
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

meistertask

MeisterTask integration. Manage Projects, Users, Roles. Use when the user wants to interact with MeisterTask data.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/meistertask/SKILL.md

Quality

Content

68%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.

A solidly actionable, concise CLI integration skill with concrete commands and a strong connection state machine. Its main weaknesses are undefined step numbering, missing validation/feedback loops on destructive actions, and inlined reference material that would benefit from a separate file.

Suggestions

Add explicit validation or fix-and-retry feedback steps for the create/update/delete and proxy (DELETE) actions so destructive workflows clear the workflow-clarity cap.

Define a clear "Step 1 / Step 2" backbone for the connection flow instead of referencing an undefined "Step 2" after the READY state.

Move the Popular-actions table into a separate reference file (e.g. references/actions.md) and link to it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Lean mix of CLI commands, tables, and code blocks with little concept re-explanation; a few padded sentences like "so you can focus on the integration logic rather than auth plumbing" and a redundant nested overview list could be trimmed.	4 / 5
Actionability	Copy-pasteable `membrane` commands with concrete flags throughout and a popular-actions table mapping names to keys; minor gap is the lack of a fully worked example with real values in place of `<actionId>`/`CONNECTION_ID` placeholders.	4 / 5
Workflow Clarity	The connection flow has a clear state-machine sequence with poll loops, but it references an undefined "Step 2" backbone, and the create/update/delete actions lack validation or fix-and-retry feedback loops, which caps destructive/batch workflow clarity at 3.	3 / 5
Progressive Disclosure	Well-sectioned single-file structure with clear navigation, but the large inline Popular-actions table is bulk API reference that could live in a separate file, and no bundle files exist to provide one-level-deep detail.	4 / 5
	Total	15 / 20 Passed

Description

66%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.

A clear, third-person description with explicit what and when clauses anchored to a specific product niche. It is held back by limited action verbs and thin keyword coverage that omits common synonyms.

Suggestions

Expand the action list with concrete verbs (e.g. create, list, update, comment on tasks and projects) to raise specificity.

Add natural trigger synonyms such as "tasks", "Kanban boards", "projects", and "sections" so users' varied phrasing matches.

Make the when-clause more specific (e.g. "Use when the user wants to list, create, or update MeisterTask tasks, projects, or sections") to push completeness toward 5.

Dimension	Reasoning	Score
Specificity	Names the MeisterTask domain plus three concrete nouns (Projects, Users, Roles) but offers no verbs beyond "Manage", so coverage is not comprehensive enough for a 4.	3 / 5
Completeness	Explicitly answers both what ("Manage Projects, Users, Roles") and when ("Use when the user wants to interact with MeisterTask data"), though the when-clause is broad and could be more specific.	4 / 5
Trigger Term Quality	Includes the natural product name "MeisterTask" but lacks common synonyms (tasks, Kanban, projects) and file extensions, so keyword coverage is partial rather than good.	3 / 5
Distinctiveness Conflict Risk	Tied to a single named product (MeisterTask) with distinct triggers, giving it a clear niche and minimal risk of conflicting with other skills.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/meistertask/SKILL.md
Commit: f484c82

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.