Name: reflect
Rating: 61.6 (1 reviews)
Author: membranedev

reflect

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

Quality

72%

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

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 strong, action-dense CLI integration guide with executable commands and a clear, validated connection-setup workflow. Its main weaknesses are minor: a slightly padded intro, a redundant 'Popular actions' section, and a dangling 'Step 2' reference with no post-execution verification.

Suggestions

Trim the opening 'Reflect is a note-taking app...' paragraph and the redundant 'Popular actions' section (it repeats the `action list` command already shown under 'Searching for actions').

Fix the 'skip to Step 2' / '#### 1b' numbering so referenced steps have matching labeled headings.

Add a brief verification/retry step after running actions (e.g. inspect the `output` field and re-run or adjust on error), since record operations can be destructive or batch-oriented.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense, executable CLI reference, but the opening paragraph explaining what a note-taking app is and the 'Popular actions' section re-stating the already-shown `action list` command are minor over-explanation that could be trimmed, matching the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	It provides copy-paste-ready commands throughout (npm install -g @membranehq/cli@latest, membrane connection ensure ... --json, membrane action run ... --input JSON) plus a proxy flag table, fully covering the common cases with executable guidance.	5 / 5
Workflow Clarity	The install → authenticate → connection ensure → poll-until-READY → handle client actions → search → run sequence is clear with explicit polling/validation feedback loops for connection state, but the dangling 'skip to Step 2' reference (no Step 2 heading) and the absence of any verification step after running actions are minor gaps.	4 / 5
Progressive Disclosure	It is a single, well-sectioned file with clear headers (Overview, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) and easy navigation; no external references are needed for this self-contained CLI reference, but the redundant 'Popular actions' section and inline note-hierarchy list are minor organization gaps rather than a perfectly split structure.	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 the skill does and when to use it, anchored on a clearly named product, but relies on generic action verbs and lacks richer natural trigger terms. It is solid but leaves room for more concrete, note-specific language.

Suggestions

Replace generic verbs with concrete note-taking actions, e.g. 'Create and link notes, manage daily reflections, and apply tags/templates'.

Expand the 'Use when...' clause with natural user phrases like 'when the user wants to take or search notes, write a daily reflection, or organize their Reflect knowledge base'.

Mention Reflect-specific entities (notes, daily reflections, templates, tags) as trigger keywords to reduce overlap with generic data-management skills.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the Reflect domain and enumerates a few actions, but the verbs ('manage') are generic and do not describe concrete, note-specific operations, fitting the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Reflect data'), matching the anchor where both are present but the 'when' could be more specific; not a 5 because the triggers are not comprehensive.	4 / 5
Trigger Term Quality	'interact with Reflect data' surfaces the product name 'Reflect' as a natural keyword, but it omits common synonyms users would actually say (notes, daily notes, journal, linking notes), matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the distinct product 'Reflect' gives it a clear niche with minimal conflict risk, but the generic 'Manage data, records, and automate workflows' phrasing leaves minor overlap with other data-management skills, so it is mostly distinct rather than fully.	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/reflect/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.