Name: deel
Rating: 60.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

deel

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

Quality

71%

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/deel/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 strong, command-first integration guide with executable examples, clear state-driven connection workflow, and good section organization. Main weaknesses are minor verbosity in the intro and the absence of verification steps for the action-running and proxy workflows.

Suggestions

Trim the opening 'Deel is a global payroll and compliance platform...' paragraph and the auth-plumbing aside to reduce token overhead on concepts Claude already knows.

Add an explicit verification step after running actions or proxy requests (e.g. inspect the `output` field and handle error states) to strengthen the feedback loop for potentially destructive operations like invoice adjustments or department updates.

Consider moving the full Popular actions table and detailed clientAction field reference into a bundled reference file, keeping SKILL.md as a concise overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven with only minor padding such as the introductory 'Deel is a global payroll and compliance platform...' paragraph and the 'so you can focus on the integration logic rather than auth plumbing' aside, which could be trimmed without loss.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands for install, login, connection ensure/get, action list/run, and proxy requests, with flags documented and a concrete Popular actions table covering common cases.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state-based validation checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a polling feedback loop, though the action-running and proxy workflows lack explicit post-run verification steps.	4 / 5
Progressive Disclosure	Content is well-organized under clear section headers with no nested references; however everything is inlined in SKILL.md with no bundle files, so the detailed clientAction breakdown and full actions table could optionally live in a reference file.	4 / 5
	Total	17 / 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 identifies the Deel niche and includes an explicit Use-when trigger, but relies on generic verbs ('Manage', 'interact') and omits high-frequency synonyms like payroll, contractors, and employees. It is distinct and complete enough but lacks specificity and richer trigger coverage.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Manage contracts, invoices, timesheets, time off, and worker records in Deel'.

Broaden trigger terms to include natural user phrases such as payroll, contractors, employees, compliance, and legal entities.

Tighten the Use-when clause to enumerate concrete triggers, e.g. 'Use when the user wants to manage Deel contracts, invoices, timesheets, or worker data'.

Dimension	Reasoning	Score
Specificity	Names the Deel/HRIS domain but the only actions ('Manage hris data, records, and workflows') are generic with minimal concrete verbs, matching the anchor where the domain is named but actions are minimal.	2 / 5
Completeness	Provides both a 'what' (manage hris data, records, workflows) and an explicit 'when' ('Use when the user wants to interact with Deel data'), though the when clause is somewhat generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes relevant keywords ('Deel', 'hris data', 'records', 'workflows') and a natural trigger phrase, but misses common synonyms a user would say like payroll, contractors, employees, or compliance.	3 / 5
Distinctiveness Conflict Risk	Targets a specific named platform (Deel) with a distinct trigger ('interact with Deel data'), giving it a clear niche with minimal overlap risk against 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/deel/SKILL.md
Commit: f484c82

Reviewed: ~16 hours 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.