Name: cradlepoint
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

cradlepoint

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

Quality

66%

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

Quality

Content

67%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 actionable and well-structured with a clear state-driven connection workflow and concrete CLI commands. The main weaknesses are a marketing-fluff opening, a filler line, and minor organization/labeling gaps.

Suggestions

Delete the opening marketing paragraph and the filler 'When to use which actions: Use action names and parameters as needed.' to tighten token use.

Define 'Step 2' explicitly (or relabel the 'Searching for actions' section as Step 2) so the cross-reference resolves.

Consolidate the duplicated action-list command between 'Searching for actions' and 'Popular actions' to remove redundancy.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the opening marketing paragraph ('Cradlepoint provides cloud-managed network solutions...') and the filler line 'When to use which actions: Use action names and parameters as needed.' are unnecessary explanation that could be trimmed.	3 / 5
Actionability	Provides copy-paste ready commands (login, connection ensure, action list/run, request) and a complete proxy flag table, but no example runs a concrete Cradlepoint action end-to-end, leaving a minor gap versus the 5 anchor.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling feedback loops, but 'Step 2' is referenced without being explicitly defined, a minor validation/clarity gap.	4 / 5
Progressive Disclosure	Single well-organized file with clear section headers and no unnecessary nested references; at ~145 lines it exceeds the simple-skill threshold, and 'Popular actions' duplicates the action-list command from 'Searching for actions', a minor organization gap keeping it at 4.	4 / 5
	Total	15 / 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.

The description includes an explicit 'Use when...' trigger and names the specific Cradlepoint niche, giving it strong distinctiveness and completeness. Weaknesses are generic action verbs and limited trigger-term variation.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Cradlepoint actions such as 'manage routers, configure NetCloud groups, and run API actions'.

Expand the trigger clause with natural variations, e.g. 'Use when the user wants to manage Cradlepoint routers, NetCloud groups, or API keys.'

Add file/extension-style concrete nouns (e.g. 'routers', 'configurations', 'API keys') to raise trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the Cradlepoint domain plus several actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete; fits the '1-2 concrete actions, not comprehensive' anchor better than the minimal/generic anchor below.	3 / 5
Completeness	It answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Cradlepoint data') with an explicit trigger clause, but the 'when' could be more specific, fitting the 4 anchor rather than the fully explicit 5.	4 / 5
Trigger Term Quality	The trigger clause offers 'Cradlepoint' and 'Cradlepoint data' as natural keywords, but lacks synonyms or variations users might say, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The Cradlepoint brand name is a distinct niche trigger with minimal overlap risk against other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	15 / 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/cradlepoint/SKILL.md
Commit: f484c82

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