Name: dear-systems
Rating: 65.60000000000001 (1 reviews)
Author: membranedev

dear-systems

DEAR Systems integration. Manage Organizations, Projects, Users, Goals, Filters. Use when the user wants to interact with DEAR Systems data.

Quality

78%

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/dear-systems/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 body is a highly actionable, well-structured integration guide with concrete CLI commands and a solid connection workflow, held back only by minor verbosity, a broken step reference, and inline reference content that could be externalized.

Suggestions

Fix the dangling "skip to Step 2" reference and label the workflow steps consistently (1a/1b/2) so the connection sequence is unambiguous.

Add a validation/recovery step after running write actions (e.g., re-fetch or check the output status) to close the feedback loop for create/update operations.

Move the 40-item entity list and the full Popular actions table into a separate reference file, keeping SKILL.md as a lean overview with a clear pointer.

Dimension	Reasoning	Score
Conciseness	The body is largely lean, command-driven reference material, with only minor over-explanation (the two-sentence ERP intro, the "auth plumbing" aside, and "Use action names and parameters as needed.") that could be trimmed, fitting the efficient-with-minor-padding anchor.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands with real flags (npm install, membrane login, connection ensure, action run with --input, proxy requests) plus a Popular actions table with concrete keys, covering the common cases.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state-based checkpoints and a feedback loop (poll BUILDING, handle CLIENT_ACTION_REQUIRED, re-poll), but the dangling "skip to Step 2" reference and the absence of post-write validation guidance are minor gaps that keep it below 5.	4 / 5
Progressive Disclosure	The single self-contained file is well-organized into clear section headers with no broken or nested references; the only organization gap is the long inline entity dump and Popular actions table that could be split into a reference file.	4 / 5
	Total	17 / 20 Passed

Description

75%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 cleanly answers what the skill does and when to use it, anchored by a distinctive named product, but its action vocabulary is a single generic verb and it lacks the broader natural vocabulary (ERP, inventory, sales) users associate with DEAR.

Suggestions

Replace the single generic verb "Manage" with a few distinct concrete actions (e.g., "List and create sales orders, customers, and invoices") to lift specificity.

Add natural synonyms users actually say — ERP, inventory, sales orders, purchase orders, invoices — so the trigger fires on common phrasings.

Align the listed entities (Organizations/Projects/Goals/Filters) with what the skill actually exposes (Sales, Customers, Inventory) to avoid over-claiming capabilities.

Dimension	Reasoning	Score
Specificity	Names the DEAR Systems domain and five concrete managed entities ("Organizations, Projects, Users, Goals, Filters"), but the single generic verb "Manage" carries all of them rather than distinct concrete actions, so it sits at the anchor-3 level rather than 4.	3 / 5
Completeness	It explicitly answers both — "Manage Organizations, Projects, Users, Goals, Filters" states the what, and "Use when the user wants to interact with DEAR Systems data" gives an explicit trigger clause — matching the anchor-5 example pattern.	5 / 5
Trigger Term Quality	The product name "DEAR Systems" is a strong, prominent natural keyword, but common variations a user would actually say (ERP, inventory, sales orders, invoices) are absent, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the named product "DEAR Systems" carves a clear niche with minimal conflict risk against other skills; the generic entity nouns are outweighed by the distinctive product name.	5 / 5
	Total	16 / 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/dear-systems/SKILL.md
Commit: f484c82

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