Name: iris-cascade
Rating: 61.6 (1 reviews)
Author: membranedev

iris-cascade

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

Quality

72%

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/iris-cascade/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, executable guide: concrete CLI commands, a clear connection-state workflow, and useful best practices. Its main gaps are light prose padding and a missing explicit validation/verification checkpoint before running actions or proxy requests against live IRIS Cascade data.

Suggestions

Add an explicit validation checkpoint after the connection is READY and before running actions (e.g., 'Confirm state is READY and a sample action list returns results before proceeding'), which would lift workflow clarity.

Trim editorial padding such as 'so you can focus on the integration logic rather than auth plumbing' and de-duplicate the repeated action-list discovery command to improve conciseness.

Move the proxy request options table and the clientAction field reference into a short separate reference section or file so the main flow stays lean, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and short prose, but contains light padding (e.g., 'so you can focus on the integration logic rather than auth plumbing' and the repeated action-list discovery commands) that could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor rather than the lean top anchor.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, polling, action search/run, and proxy requests with a concrete options table, covering the common cases with executable guidance rather than pseudocode, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with state-based branches (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and re-polling feedback, but there is no explicit validation step before running actions against live data and the destructive/batch proxy operations lack a verify checkpoint, so it sits at the 'clear sequence with most checkpoints; minor validation gaps' anchor rather than the explicit-validation top anchor.	4 / 5
Progressive Disclosure	Content is well organized into overview, install, auth, connection, actions, proxy, and best-practices sections with no bundle files to defer to, but the proxy options table and clientAction details are inlined where a separate reference could keep the overview leaner, fitting 'good structure; most content appropriately placed; minor organization gaps' rather than the ideal one-level-deep split.	4 / 5
	Total	17 / 20 Passed

Description

62%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 names its domain and includes a usable 'Use when...' trigger, giving it a solid functional baseline. Its weakness is generic action verbs ('Manage', 'automate workflows') that under-specify what IRIS Cascade actually does, leaving the trigger and specificity short of the top anchors.

Suggestions

Replace generic verbs with IRIS-Cascade-specific capabilities (e.g., 'view employee absence, teams, org charts, and reports') so the description signals concrete actions.

Expand the trigger clause with natural user phrases and synonyms (e.g., 'Use when the user wants to query IRIS Cascade HR data, pull employee records, or run absence/team reports').

Tighten the 'when' to reference the data types users actually mention (employees, absences, teams, reports) to sharpen distinctiveness and trigger matching.

Dimension	Reasoning	Score
Specificity	Names the IRIS Cascade domain and two concrete actions ('Manage data, records, and automate workflows'), but the actions are generic verbs rather than a comprehensive, specific list, so it matches the 'domain and 1-2 concrete actions, but not comprehensive' anchor rather than the multi-action anchor above.	3 / 5
Completeness	It states a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with IRIS Cascade data'), but the 'when' is fairly generic, so it matches the 'has both what and when; when could be more explicit or specific' anchor rather than the concrete-trigger-phrases anchor above.	4 / 5
Trigger Term Quality	'interact with IRIS Cascade data' and 'Manage data, records, and automate workflows' give some relevant keywords but miss common natural variations or synonyms a user would say, fitting the 'some relevant keywords but missing common variations' anchor rather than the good-coverage anchor above.	3 / 5
Distinctiveness Conflict Risk	The IRIS Cascade name gives it a clear niche distinct from other skills, with only minor overlap risk from the generic 'Manage data, records, and automate workflows' phrasing, so it sits above the 'somewhat specific but could overlap' anchor but below the minimal-conflict anchor.	4 / 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/iris-cascade/SKILL.md
Commit: f484c82

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