Name: google-tasks
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

google-tasks

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

Quality

61%

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/google-tasks/SKILL.md

Quality

Content

61%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 action-dense with executable Membrane CLI commands and a clear connection-state workflow, but it over-explains basic concepts and offers no validation steps for its destructive task actions. Splitting the action table into a reference file would improve progressive disclosure.

Suggestions

Remove or trim the introductory paragraph explaining what Google Tasks is, since Claude already knows this.

Add a validation/confirmation checkpoint before destructive actions (e.g. list-tasks to confirm the target, then confirm with the user before delete-task or clear-completed-tasks).

Provide one worked example with real parameters for a popular action (e.g. create-task with an actual title and task list id) instead of generic '{"key": "value"}'.

Dimension	Reasoning	Score
Conciseness	The bulk is lean commands and tables, but the opening paragraph explains what Google Tasks is ('a simple task management app that allows users to create and organize to-do lists') and Membrane's auth behavior in ways Claude already knows.	3 / 5
Actionability	It gives copy-paste-ready commands for install, login, connection, action list/run, and proxy requests, but the parameter example uses generic placeholders ('{"key": "value"}') with no worked example of a real popular action.	4 / 5
Workflow Clarity	The connection flow has state-checking and polling checkpoints, but destructive actions (delete-task, delete-task-list, clear-completed-tasks) are listed with no validation/confirmation steps, capping this dimension at 3.	3 / 5
Progressive Disclosure	The body is well-sectioned (install, auth, connect, search, run, proxy, best practices) with no nested references; the inlined popular-actions table is reasonable for an overview, though it could live in a separate reference file.	4 / 5
	Total	14 / 20 Passed

Description

61%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 correctly includes an explicit 'Use when...' trigger and names the Google Tasks niche distinctly, but its capability list is generic ('Manage data, records, and automate workflows') rather than naming concrete task actions. Tightening the action verbs would lift specificity and trigger-term quality.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete task actions such as 'create, list, update, and delete tasks and task lists'.

Add natural trigger synonyms users say, e.g. 'to-do lists', 'tasks', 'task lists', alongside 'Google Tasks'.

Make the 'when' clause more specific, e.g. 'Use when the user wants to manage Google Tasks, to-do lists, or task reminders.'

Dimension	Reasoning	Score
Specificity	It names the domain ('Google Tasks integration') but the only actions offered are generic ('Manage data, records, and automate workflows') with no concrete operations like create/list/delete tasks.	2 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Google Tasks data'), though the 'what' is somewhat vague.	4 / 5
Trigger Term Quality	The phrase 'Google Tasks' appears as a natural keyword, but common variations and synonyms a user might say ('to-do lists', 'tasks', 'task lists') are missing.	3 / 5
Distinctiveness Conflict Risk	'Google Tasks' is a clearly named app niche with distinct triggers, giving minimal overlap risk with other skills.	5 / 5
	Total	14 / 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/google-tasks/SKILL.md
Commit: f484c82

Reviewed: 5 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.