Name: sedna
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

sedna

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

Quality

63%

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

Quality

Content

68%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 highly actionable with concrete, copy-pasteable Membrane CLI commands and a well-validated connection workflow, but it carries a marketing-flavored intro and lacks verification checkpoints around the destructive data-operation and proxy workflows. Structure is solid with minor navigation gaps.

Suggestions

Cut the marketing language from the intro (keep only what Claude needs: what SEDNA is and its core entities) to improve conciseness.

Add a verification checkpoint before/after running actions and proxying destructive requests (e.g., 'For write/delete actions, confirm the target id and inspect the output field for errors before proceeding').

Resolve the dangling 'Step 2' reference by explicitly numbering the connect -> discover -> run workflow, or fold 'Popular actions' into 'Searching for actions' to remove the overlap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI guidance, but the opening marketing paragraph ('streamline communication and workflow... improving efficiency and decision-making... used by ship operators, managers, and crew members') and phrases like 'auth plumbing' are unnecessary padding, fitting the 'mostly efficient but includes some unnecessary explanation' anchor rather than the minor-trim 4.	3 / 5
Actionability	The body provides fully executable, copy-paste-ready commands for every common case (install, login, connection ensure/get --wait, action list/run with --input, request with a complete flags table), with placeholders appropriate for a dynamic integration, matching the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	The connection flow has explicit state-based validation and polling feedback loops, but the data-operation workflows (running actions and proxying requests including destructive PUT/DELETE) lack any validation or verification checkpoints, so the destructive-operations cap holds at the 'sequence present but checkpoints missing or implicit' anchor.	3 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with an official-docs link and no nested references, but the ~140-line body is entirely inline with no external reference files and has minor organization gaps (a dangling 'Step 2' reference, a thin 'Popular actions' section), fitting the 'good structure; minor organization gaps' anchor rather than a 5.	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 correctly uses third-person voice and includes an explicit 'Use when' trigger with a distinctive product name, but its capabilities are stated generically rather than concretely and its trigger keywords lack common synonyms. It is functional and distinct but would benefit from naming specific SEDNA operations.

Suggestions

Replace generic verbs with concrete SEDNA operations (e.g., 'search messages, manage tasks, and query records') to lift specificity.

Expand the trigger clause with natural user phrasing and synonyms (e.g., 'Use when the user wants to search SEDNA messages, manage tasks, or query shipping records').

Mention the actual SEDNA entities (email, tasks, issues, projects) in the description so the 'when' is more specific.

Dimension	Reasoning	Score
Specificity	Names the SEDNA domain but the actions ('Manage data, records, and automate workflows') are generic verbs on generic nouns rather than concrete operations, matching the 'names the domain but actions are minimal or generic' anchor rather than the 1-2 concrete actions needed for a 3.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with SEDNA data') are present, but the when could be more specific about actual SEDNA use cases, matching the 'has both what and when; when could be more explicit' anchor rather than the fully concrete 5.	4 / 5
Trigger Term Quality	'SEDNA', 'data', 'records', and 'workflows' provide some relevant keywords with SEDNA as a strong specific trigger, but common variations/synonyms (email, tasks) that users would actually say are missing, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The SEDNA product name establishes a clear niche with a distinct trigger, but the generic 'manage data, records, automate workflows' phrasing carries minor overlap risk with other data-management skills, fitting the 'mostly distinct; minor overlap risk' anchor.	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/sedna/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.