Name: reclaim
Rating: 59.2 (1 reviews)
Author: membranedev

reclaim

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

75%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 body is highly actionable with concrete, executable CLI commands and a well-validated connection workflow. Its main weaknesses are a redundant intro/concept explanation and a duplicated action-discovery section, plus a broken 'Step 2' cross-reference.

Suggestions

Remove or condense the opening 'Reclaim is a time management and scheduling tool...' paragraph, which restates general knowledge Claude already has.

Merge the 'Searching for actions' and 'Popular actions' sections, which both demonstrate `membrane action list --intent=QUERY`, into one discovery section.

Fix the 'skip to Step 2' reference — there is no labeled Step 2 — by either numbering the steps explicitly or pointing to a concrete section heading.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete CLI commands, but it opens by explaining what Reclaim is ('Reclaim is a time management and scheduling tool that integrates with your calendar...') which Claude largely knows, and the 'Searching for actions' and 'Popular actions' sections duplicate the same discovery command, so it could be tightened.	3 / 5
Actionability	Provides fully executable, copy-paste-ready membrane CLI commands (login, connection ensure, action run, request) with a complete flag table and JSON-output examples covering the common cases, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit validation checkpoints (poll --wait, state checks for READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a feedback loop (re-poll after the user acts), but the 'skip to Step 2' reference points to a non-existent Step 2, leaving a minor navigation gap.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized with clear section headers and no nested references, and there are no bundle files to navigate; over 50 lines so the simple-skill exception does not apply, but structure and placement are good with only minor gaps (duplicated discovery section).	4 / 5
	Total	16 / 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 names a specific app and includes both a what and a Use-when clause, but the listed actions are generic and it omits the natural scheduling vocabulary (habits, tasks, calendar) that would help it trigger reliably. It is functional but could be sharper and more concrete.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Reclaim actions like 'create and manage habits, tasks, events, and time blocks'.

Expand the 'Use when' clause with natural trigger terms users actually say, e.g. 'Use when the user wants to schedule habits, block time for tasks, or manage Reclaim events and calendars'.

Add the file/extension or feature vocabulary (calendar, time blocks, smart meetings) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Reclaim) and several actions — 'Manage data, records, and automate workflows' — but the actions are generic rather than concrete (no habits/tasks/scheduling specifics), fitting the 'names domain and 1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	Provides a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Reclaim data'), but the trigger clause is generic and could be more specific, matching the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	Includes 'Reclaim' and 'data', 'records', 'workflows' but is missing the natural scheduling vocabulary users would say (habits, tasks, events, calendar, time blocks), matching 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	Reclaim is a named app giving it a clear niche with Reclaim-specific triggers, but 'Manage data, records, and automate workflows' is broad enough to overlap with general data-management skills, so it is 'mostly distinct; minor overlap risk'.	4 / 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/reclaim/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.