Name: amentum-aerospace
Rating: 53.6 (1 reviews)
Author: membranedev

amentum-aerospace

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

Quality

60%

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

Quality

Content

60%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 delivers strong, copy-paste-ready Membrane CLI commands and a genuine connection-readiness polling loop with error handling, but it is undermined by a speculative, apologetic opening and a Popular actions table with empty descriptions.

Suggestions

Delete the speculative first paragraph ("Amentum Aerospace likely serves...") and the "Official docs: I am sorry, I cannot provide..." apology; both are irrelevant filler that does not help Claude execute.

Fill the empty Description column of the Popular actions table (e.g. what each action returns) or move the table into a references file referenced from the body.

Relabel the fragmented "skip to Step 2" / "#### 1b" flow as a coherent numbered sequence (1. Ensure connection, 2. Wait for READY, 3. Search actions, 4. Run) so the steps referenced in prose actually exist.

Dimension	Reasoning	Score
Conciseness	The body opens with speculative filler ("Amentum Aerospace likely serves the aerospace industry... Without further information, it's difficult to specify the exact function") and a first-person apology ("I am sorry, I cannot provide an API..."), which are unnecessary padded sections Claude does not need, matching the score-2 anchor "Noticeably verbose; several unnecessary explanations or padded sections".	2 / 5
Actionability	Concrete copy-paste commands cover the common cases (install, login, connection ensure, action list/run, request proxy) with flags explained, but the Popular actions table leaves the Description column empty and parameter examples use generic placeholders like '{"key": "value"}', leaving minor gaps versus the fully-executable score-5 anchor.	4 / 5
Workflow Clarity	The connect-then-poll flow has a real validation checkpoint (poll until state is READY, with explicit handling of CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR, and SETUP_FAILED plus a re-poll feedback loop), but the "skip to Step 2" / "#### 1b" labeling references steps that are not coherently enumerated, a minor clarity gap below the score-5 anchor.	4 / 5
Progressive Disclosure	The single SKILL.md has well-organized sections (Overview, Working with, Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) and no nested external references, but at ~160 lines with a large inline actions table and clientAction breakdown it exceeds the simple-skill <50-line exception, leaving minor organization gaps versus the score-5 anchor.	4 / 5
	Total	14 / 20 Passed

Description

61%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 uses correct third-person voice and supplies both a what and an explicit Use-when clause, but its capabilities are generic rather than concrete and it leans on a single brand-name trigger with no synonyms.

Suggestions

Replace generic verbs ("manage data, records, automate workflows") with concrete capabilities, e.g. "query geomagnetic and atmosphere forecasts, retrieve ocean and bathymetry data, calculate flight-route radiation dose".

Expand the trigger clause with natural variations, e.g. "Use when the user wants aerospace environmental data, geomagnetic indices, ionosphere/ocean forecasts, or flight radiation calculations from Amentum Aerospace."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain and several action verbs, but the actions are generic categories rather than concrete capabilities (cf. score-3 anchor "extracts content"), matching the score-2 anchor "actions are minimal or generic".	2 / 5
Completeness	Both halves are present — "Manage data, records, and automate workflows" (what) and "Use when the user wants to interact with Amentum Aerospace data" (when) — but the what is generic and the when offers only a single trigger phrase, so it is not the comprehensive score-5 anchor.	4 / 5
Trigger Term Quality	The only natural trigger term is the brand "Amentum Aerospace" repeated in "interact with Amentum Aerospace data"; there are no synonyms, common variations, or file extensions, matching the score-3 anchor "Some relevant keywords but missing common variations or synonyms".	3 / 5
Distinctiveness Conflict Risk	"Amentum Aerospace integration" targets a specific named brand with a distinct trigger ("interact with Amentum Aerospace data"), giving it a clear niche with minimal conflict risk against other skills.	5 / 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/amentum-aerospace/SKILL.md
Commit: f484c82

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