Name: seqera
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

seqera

Seqera integration. Manage Organizations, Users, Pipelines. Use when the user wants to interact with Seqera data.

Quality

67%

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

Quality

Content

61%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-sectioned with a genuine connection-state feedback loop, but it is held back by promotional padding in the intro and a broken step-numbering scheme that muddies the workflow sequence.

Suggestions

Fix the workflow numbering: add a 'Step 1' header before '1b', and label the 'Searching for actions' section as 'Step 2' so the 'skip to Step 2' reference resolves.

Trim the promotional intro paragraph ('Seqera Labs develops software...') and the explanatory aside about URL normalization; assume Claude can infer these.

Add an explicit validation/check step after running actions (e.g. inspect the `output` field and handle non-READY or error states) to close the workflow loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational commands, but the opening paragraph ('Seqera Labs develops software for data pipeline orchestration...') and asides like 'This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps...' are unnecessary padding that could be tightened.	3 / 5
Actionability	Provides concrete copy-paste commands (install, login, connection ensure, action run, request) plus a flags table; the only gaps are expected placeholders like CONNECTION_ID and <actionId>, keeping it just below fully-ready 5.	4 / 5
Workflow Clarity	A real polling feedback loop for connection state (READY / CLIENT_ACTION_REQUIRED / re-poll) exists, but the numbering is broken: 'skip to Step 2' references a Step 2 that is never labeled, and '#### 1b' appears with no '1.' or 'Step 1' header, leaving the sequence with implicit checkpoints and gaps.	3 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections (Overview, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no bundle files present and a single-file structure that is appropriate; only minor reorganization (e.g. splitting the proxy flags table) would push it higher.	4 / 5
	Total	14 / 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 Seqera niche and provides both a what and a when, but its actions lean on the generic verb 'Manage' and the trigger phrase ('interact with Seqera data') is broad rather than enumerating concrete trigger situations.

Suggestions

Replace the generic verb 'Manage' with distinct concrete actions, e.g. 'Create and manage Organizations, invite Users, launch and monitor Pipelines'.

Sharpen the 'Use when' clause to name concrete triggers, e.g. 'Use when the user wants to create or monitor Seqera pipelines, manage org members, or list compute environments'.

Consider adding the other core Seqera entities (Runs, Compute Environments, Credentials) as trigger keywords to broaden natural-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Seqera domain and three concrete action targets ('Organizations, Users, Pipelines'), but the single generic verb 'Manage' is less concrete than distinct verbs like extract/fill/merge, so it sits below the anchor-4 example rather than at it.	3 / 5
Completeness	Both 'what' ('Manage Organizations, Users, Pipelines') and 'when' ('Use when the user wants to interact with Seqera data') are present, but the trigger phrase is somewhat generic ('interact with Seqera data') and lacks the concrete trigger variations of the anchor-5 example.	4 / 5
Trigger Term Quality	'Seqera' plus 'Organizations, Users, Pipelines' are natural terms a user would say, giving good keyword coverage; a few common variations and other Seqera entities (Runs, Compute Environments, Credentials) are missing, so it is not a 5.	4 / 5
Distinctiveness Conflict Risk	'Seqera' is a clearly named, narrow product niche with distinct triggers and minimal realistic overlap 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/seqera/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.