Name: armoryio
Rating: 49.6 (1 reviews)
Author: membranedev

armoryio

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

Quality

54%

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

Quality

Content

46%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 provides solid, executable Membrane CLI guidance for auth, connection setup, and action discovery, but it is undermined by a large padded entity list and slightly broken workflow navigation. Structure and token efficiency are the weakest areas.

Suggestions

Remove or collapse the ~150-item entity list; if enumeration is needed, move it to a reference file the agent loads only on demand.

Fix the 'Skip to Step 2' reference by labeling the action-search section as Step 2 or rewriting the navigation to point to the 'Searching for actions' heading.

Add an explicit validate/feedback loop for action runs, e.g. check the response `output`/`error` field and retry with adjusted parameters before reporting failure.

Dimension	Reasoning	Score
Conciseness	The body inlines a ~150-item undifferentiated entity list (Asset, Project, User … Watermark) that earns no token and adds no guidance, plus a 'what is Armory.io' intro; this is noticeable padding despite otherwise efficient CLI sections, matching 'noticeably verbose; several unnecessary padded sections'.	2 / 5
Actionability	It gives concrete, executable CLI commands with flags and examples (install, login, connection ensure, action list/run, request) covering common cases, with only minor gaps like placeholder <actionId>, fitting 'mostly executable guidance with minor gaps'.	4 / 5
Workflow Clarity	The connection flow is sequenced with state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and polling, but it references a 'Step 2' that is not clearly labeled and lacks explicit validate-fix-retry feedback loops, matching 'steps present but checkpoints missing or implicit'.	3 / 5
Progressive Disclosure	No bundle files exist and the SKILL.md is a single ~290-line file whose large entity list is inlined content that adds no navigational value and should not be inlined, matching 'minimal structure; content that clearly belongs elsewhere is inlined'.	2 / 5
	Total	11 / 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 is third-person, names the product, and includes an explicit 'Use when' clause, covering both what and when. Its main weakness is generic action verbs and limited natural trigger terms beyond the brand name.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Deploy applications, manage pipelines, and view deployment status across cloud environments'.

Add natural user trigger phrases and synonyms such as 'Spinnaker', 'continuous delivery', or 'deployment pipelines' alongside 'Armory.io'.

Tighten the 'Use when' clause to specific intents, e.g. 'Use when the user wants to trigger or monitor Armory.io deployments and pipelines'.

Dimension	Reasoning	Score
Specificity	Names the domain (Armory.io) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, so it is not comprehensive — fitting the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Armory.io data'); the 'when' is explicit but generic, so it sits at the 'has both, when could be more specific' anchor rather than a 5.	4 / 5
Trigger Term Quality	Includes the brand keyword 'Armory.io' plus 'data' and 'records', but lacks common variations, synonyms, or natural user phrasings beyond the product name, matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named product 'Armory.io' gives it a clear niche with minimal conflict risk, though the generic action verbs leave minor overlap with other data-management skills, matching 'mostly distinct; minor overlap risk'.	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/armoryio/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.