CtrlK
BlogDocsLog inGet started
Tessl Logo

simplicate

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

61

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/simplicate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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 well-structured, highly actionable integration guide with copy-paste commands and a clear connection workflow. Its main weakness is the absence of validation/verification steps around create, update, and proxy (DELETE) operations that can mutate or destroy data.

Suggestions

Add explicit validation checkpoints after create/update actions (e.g., re-fetch the created/updated record with the matching 'get' action and confirm the returned fields before reporting success).

Add a destructive-operation guard around `membrane request` and any DELETE/PUT proxy calls: confirm the target id and method with the user, and document how to dry-run or undo where possible.

Trim the introductory Simplicate overview paragraph and the 'Use action names and parameters as needed' filler, since they explain context Claude already has.

DimensionReasoningScore

Conciseness

The body is largely efficient with executable commands and tables, though the marketing-style Simplicate overview blurb and filler lines like 'Use action names and parameters as needed' could be trimmed.

4 / 5

Actionability

It provides copy-paste-ready commands for every key operation (install, login, connection ensure, action list/run, proxy flags) with concrete parameter examples covering the common cases.

5 / 5

Workflow Clarity

The connect-to-run sequence is present with polling and state-based branching, but create/update and proxy (DELETE-capable) operations have no validation or verification steps, so the destructive-capable workflow cannot exceed 3 per the cap.

3 / 5

Progressive Disclosure

The skill is a single self-contained SKILL.md with no bundle files and is organized into clear, navigable sections, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

17

/

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 competent description with an explicit use-when clause and a clearly named niche, but its capability list is generic rather than enumerating Simplicate's specific entities. Tightening the action list to concrete domains (CRM, projects, invoices, hours) would lift specificity and trigger quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Simplicate capabilities such as 'Manage organizations, persons, projects, invoices, hours, and deals'.

Expand the 'Use when' clause with natural trigger phrases (e.g., 'when the user mentions Simplicate CRM, projects, sales, invoices, or time tracking').

Add file- or module-level keywords (CRM, HRM, time registration) so the trigger surfaces for the specific sub-domains a user is likely to name.

DimensionReasoningScore

Specificity

The description names the domain and a few actions ('Manage data, records, and automate workflows') but the actions are generic and do not reflect the concrete capabilities (invoices, projects, hours, deals) the skill actually exposes.

3 / 5

Completeness

Both a 'what' (Simplicate integration managing data, records, workflows) and an explicit 'when' ('Use when the user wants to interact with Simplicate data') are present, though the 'when' clause is generic rather than listing concrete triggers.

4 / 5

Trigger Term Quality

It includes 'Simplicate', 'data', and 'records' but misses natural synonyms and variations a user would say; the trigger phrasing is fairly generic.

3 / 5

Distinctiveness Conflict Risk

The named app 'Simplicate' plus an explicit 'Use when...interact with Simplicate data' trigger carves a clear niche with minimal risk of triggering for unrelated skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.