Name: nutshell
Rating: 64.8 (1 reviews)
Author: membranedev

nutshell

Nutshell integration. Manage Leads, Persons, Organizations, Deals, Projects, Activities and more. Use when the user wants to interact with Nutshell 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/nutshell/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 highly actionable with executable commands and reference tables, and the connection workflow has good validation checkpoints. Its main weaknesses are minor padding, a dangling 'Step 2' reference, and a lack of file-based progressive disclosure for the inlined action reference.

Suggestions

Trim the padded phrases (e.g., 'so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') and the generic Nutshell intro paragraph.

Label the downstream section 'Step 2: Search for actions' (or reword 'skip to Step 2') so the cross-reference resolves, and add a verify step for mutations (e.g., re-fetch with get-lead after create-lead).

Move the 20-row Popular actions table into a references/ file (e.g., ACTIONS.md) and link to it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is predominantly concrete commands and reference tables, but includes minor over-explanation that could be trimmed such as 'so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection', and the three-sentence intro about Nutshell being a B2B CRM.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands across the common cases (install, login, connection ensure with a real URL, action list/run, proxy request), reinforced by a 20-row Popular actions table and a proxy-flags table.	5 / 5
Workflow Clarity	The connection flow is a clear sequence with explicit state checkpoints and a poll/check/act feedback loop, but 'skip to Step 2' dangles with no labeled Step 2, and no verification guidance is given for data-mutating actions (create/update).	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but the skill is over 50 lines with a 20-row inlined action reference that could be split into a separate file, and content is monolithic rather than split across one-level-deep references.	4 / 5
	Total	17 / 20 Passed

Description

73%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 clearly identifies the Nutshell CRM niche and gives an explicit 'Use when' clause, but its action language is generic ('Manage') and its trigger phrasing ('interact with Nutshell data') lacks concrete, natural variations.

Suggestions

Replace the single generic verb 'Manage' with several concrete actions (e.g., 'Find, create, update, and delete Leads, Contacts, Deals, and Activities').

Make the 'Use when' clause list concrete trigger phrases a user would actually say (e.g., 'Use when the user wants to find leads, log activities, or manage deals in Nutshell').

Use the natural entity names users say (Contacts, Opportunities) alongside or instead of 'Persons'/'Deals' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Nutshell) and six concrete entity types, but the only action verb is the generic 'Manage Leads, Persons, Organizations, Deals, Projects, Activities and more' — no several distinct concrete actions, so it sits at anchor 3 rather than 4.	3 / 5
Completeness	It explicitly answers both what ('Nutshell integration. Manage Leads...') and when ('Use when the user wants to interact with Nutshell data'), but the 'when' clause is generic rather than listing concrete trigger phrases, so it is not a 5.	4 / 5
Trigger Term Quality	Good keyword coverage via 'Nutshell' plus natural CRM entity terms (Leads, Deals, Activities), but it misses common synonyms users say such as Contacts (it says 'Persons') and Opportunities (it says 'Deals').	4 / 5
Distinctiveness Conflict Risk	It is anchored to a named, specific product (Nutshell CRM) with distinct triggers, giving it a clear niche and minimal conflict risk with other skills.	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/nutshell/SKILL.md
Commit: f484c82

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