Name: solar-nexus
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

solar-nexus

Solar Nexus integration. Manage Organizations. Use when the user wants to interact with Solar Nexus data.

Quality

62%

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/solar-nexus/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 content is a strong, executable CLI integration guide with clear workflows and validation checkpoints for the connection lifecycle; its main weaknesses are a padded introductory paragraph and no validation guidance for mutating action runs.

Suggestions

Trim the opening SaaS/audience description and the auth-prose to keep only what is needed to act.

Add a verify step after mutating actions (e.g., re-fetch the project to confirm an update applied), creating a validate-fix-retry loop for batch/destructive operations.

Optionally move the popular-actions table and proxy flag reference into a references/ file so SKILL.md stays a lean overview pointing one level deep.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and tables, but the opening paragraph explaining what Solar Nexus is and who uses it, plus some auth-prose, is explanation Claude does not strictly need.	3 / 5
Actionability	It provides copy-paste-ready bash commands throughout (connection ensure, action list/run, request proxy) and concrete flag tables, with only minor gaps such as no fully-resolved worked example with real parameter values.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state checkpoints and a poll-after-user-action feedback loop; a minor gap is the absence of a verify step after mutating action runs like update-project or complete-milestone.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with no nested or buried references, but the large popular-actions table and proxy flag reference could be split into separate bundle files to keep SKILL.md a leaner overview.	4 / 5
	Total	15 / 20 Passed

Description

57%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 is third-person, includes an explicit 'Use when' trigger, and is clearly tied to a specific product, but it is vague on concrete capabilities and thin on natural trigger synonyms.

Suggestions

Replace the generic 'Manage Organizations' with 2-3 concrete actions users perform (e.g., 'list projects, update milestones, retrieve project participants').

Add natural trigger synonyms users would actually say, such as 'solar projects', 'solar installations', or 'SolarNexus jobs'.

Tighten the 'when' clause to specific intents (e.g., 'Use when the user wants to query or update Solar Nexus projects, milestones, or workgroups').

Dimension	Reasoning	Score
Specificity	The description names the domain ('Solar Nexus', 'Organizations') but offers only one minimal, generic action verb ('Manage Organizations'), lacking the multiple concrete actions of higher anchors.	2 / 5
Completeness	Both a 'what' ('Solar Nexus integration. Manage Organizations.') and an explicit 'when' ('Use when the user wants to interact with Solar Nexus data.') are present, though the 'what' is thin and the 'when' is somewhat generic.	4 / 5
Trigger Term Quality	It includes relevant keywords ('Solar Nexus', 'Organizations', 'interact with ... data') but misses common natural variations a user would actually say, such as 'solar projects' or 'solar installations'.	3 / 5
Distinctiveness Conflict Risk	The named product 'Solar Nexus' gives it a clear niche with minimal conflict risk, though the broad 'Manage Organizations' leaves minor overlap with other CRM/solar-related skills.	4 / 5
	Total	13 / 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/solar-nexus/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.