Name: foundriesio
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

foundriesio

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

Quality

61%

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/foundriesio/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 content is a solidly actionable CLI integration guide with concrete commands and a clear connection-setup workflow. Its weak spots are missing validation/verification after running potentially destructive actions and some filler phrasing that could be trimmed.

Suggestions

Add a verification step after running actions or deployments (e.g., re-query the resource or check job state) to satisfy the destructive-operation validation requirement and lift workflow_clarity.

Trim filler lines like 'Use action names and parameters as needed.' and tighten marketing phrasing around auth plumbing to improve conciseness.

Resolve the overlap between 'Searching for actions' and 'Popular actions', and provide at least one fully-worked action example (real actionId, input, expected output) to close the actionability gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but contains padding such as 'Use action names and parameters as needed', the marketing phrasing about auth plumbing, and 'burn less tokens', fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	It provides copy-paste ready commands (install, login, connection ensure, action list/run, request) and a flags table, but relies on placeholders (CONNECTION_ID, <actionId>, QUERY) with no complete worked example, matching 'concrete code or commands with minor gaps'.	4 / 5
Workflow Clarity	The connection setup has clear sequencing and state-polling checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but running actions and deployments lacks verification steps; since deployments/rollouts are destructive, the missing validation caps this at 3.	3 / 5
Progressive Disclosure	The body is well-organized into clear sections (Overview, Working with Foundries.io, Popular actions, Best practices) with no nested or buried references, but the 'Popular actions' section slightly duplicates 'Searching for actions' and there is no reference structure, leaving minor organization gaps.	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 cleanly answers both what the skill does and when to use it, anchored by a highly distinctive product-name trigger. Its main weakness is generic action language ('manage data, records, automate workflows') instead of concrete Foundries.io capabilities, which limits specificity and trigger-term breadth.

Suggestions

Replace generic verbs with concrete Foundries.io actions, e.g. 'Manage devices, factory targets, builds, deployments, and rollouts' to lift specificity.

Broaden the trigger clause to enumerate natural phrases users say, e.g. 'Use when the user wants to manage Foundries.io devices, targets, builds, deployments, or rollouts.'

Add the .io / 'Foundries' short-form and key domain nouns (devices, factories, fleets) to improve trigger-term synonym coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the domain but the actions are generic verbs rather than concrete Foundries.io operations (e.g., deploy devices, trigger rollouts, manage factory targets), matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It explicitly states both the 'what' (Foundries.io integration; manage data, records, workflows) and the 'when' ('Use when the user wants to interact with Foundries.io data'), but the 'when' is a single narrow trigger rather than multiple concrete trigger phrases, so it is not a 5.	4 / 5
Trigger Term Quality	The trigger 'interact with Foundries.io data' surfaces the specific product name but offers only one keyword with no common variations or synonyms, fitting 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	Foundries.io is a specific named platform, so the 'Foundries.io' trigger carves a clear niche with minimal conflict risk against other skills, matching the 'clear niche with distinct triggers' anchor.	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/foundriesio/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.