Name: 15five
Rating: 64 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

15five

15Five integration. Manage Persons, Organizations. Use when the user wants to interact with 15Five data.

Quality

76%

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

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid integration skill with excellent actionability and workflow clarity—the CLI commands are concrete and the connection state machine is well-documented with clear branching logic. The main weaknesses are moderate verbosity (introductory fluff, a description-less action table consuming tokens) and a monolithic structure that could benefit from externalizing the action catalog or proxy reference details.

Suggestions

Remove the introductory paragraph explaining what 15Five is and the bullet-point overview section—Claude doesn't need this context to execute the integration.

Either add meaningful descriptions to the popular actions table or remove it entirely, as 20 rows of 'No description' waste tokens without aiding action discovery (the `membrane action list --intent` command already handles this).

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary explanatory content (e.g., 'performance management platform that helps companies improve employee engagement...') and the overview section listing Objectives/Check-ins/People/Reviews/Settings adds no actionable value. The popular actions table has 'No description' for every entry, wasting tokens. However, the core CLI commands are reasonably lean.	2 / 3
Actionability	The skill provides fully executable, copy-paste-ready CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Flag tables and JSON parameter examples are concrete and specific.	3 / 3
Workflow Clarity	The connection workflow is clearly sequenced with explicit state-based branching (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), polling instructions with --wait flag, and clear next steps for each state. The overall flow from install → auth → connect → discover → run is well-structured with validation checkpoints.	3 / 3
Progressive Disclosure	The content is a single monolithic file with no references to supporting files, and the popular actions table (20 rows, all without descriptions) could be externalized. The overview section at the top doesn't serve as effective navigation. However, for a skill of this size (~120 lines of substantive content), the inline approach is borderline acceptable.	2 / 3
	Total	10 / 12 Passed

Description

75%

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 specific integration (15Five) and includes an explicit 'Use when' clause, which helps with completeness and distinctiveness. However, the actions are vague ('Manage') and the trigger terms could be expanded to include natural language variations users might employ when referring to 15Five's domain (HR, performance reviews, employees).

Suggestions

Replace 'Manage' with specific concrete actions like 'Create, update, list, and delete Persons and Organizations' to improve specificity.

Add natural trigger terms users might say, such as 'employees', 'people', 'HR data', 'performance management', or 'team members' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (15Five) and mentions 'Manage Persons, Organizations' which are some actions, but 'manage' is vague and doesn't specify concrete operations like create, update, delete, or list.	2 / 3
Completeness	Answers both 'what' (manage Persons, Organizations in 15Five) and 'when' ('Use when the user wants to interact with 15Five data'), providing an explicit trigger clause.	3 / 3
Trigger Term Quality	Includes '15Five' as a key trigger term and mentions 'Persons' and 'Organizations', but misses natural variations users might say like 'employees', 'people', 'companies', 'HR', or 'performance management'.	2 / 3
Distinctiveness Conflict Risk	15Five is a specific product name, making this highly distinctive and unlikely to conflict with other skills. The niche is clear.	3 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: membranedev/application-skills
Path: skills/15five/SKILL.md
Commit: f484c82

Reviewed: 1 day 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.