Name: outsystems
Rating: 56.8 (1 reviews)
Author: membranedev

outsystems

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

Quality

65%

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

Quality

Content

67%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 solid, command-driven integration guide with good actionability and a mostly clear connection workflow, but it explains background knowledge Claude already has and is a monolithic file with no progressive disclosure. A dangling 'Step 2' reference and absent validation checkpoint slightly weaken workflow clarity.

Suggestions

Remove or condense the introductory paragraph explaining what OutSystems is, since Claude already knows this; lead with the install/auth commands.

Define the referenced 'Step 2' or replace the cross-reference with a concrete next action so the workflow has no dangling pointer.

Add an explicit validation step (e.g., confirm the connection state is READY before running actions) to strengthen the workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-focused content, but the opening paragraph ('OutSystems is a low-code development platform that enables businesses to rapidly build and deploy...') and the Overview explanatory text explain background Claude already knows, fitting the 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request proxy flags in a table) with minor gaps such as CONNECTION_ID placeholders left unresolved, matching 'mostly executable guidance with minor gaps.'	4 / 5
Workflow Clarity	The connection flow is well sequenced with explicit state checks (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-then-act loop, but there is no explicit validation checkpoint before running actions and the 'Step 2' referenced in the text is never defined, leaving minor gaps.	4 / 5
Progressive Disclosure	The body is a single monolithic SKILL.md with no bundle files (references/scripts/assets absent) and no external file references, so while sections are organized, all content lives inline with no one-level-deep split, matching 'some structure but could be better organized.'	3 / 5
	Total	14 / 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 functional and includes an explicit 'Use when' trigger plus a clear domain, but its action list and trigger keywords are generic and thin. It clears a usable bar without being comprehensive or rich in natural terms.

Suggestions

Expand the action list with concrete verbs (e.g., 'create and update records, query entities, trigger workflows') to lift specificity.

Add natural trigger synonyms users would say, such as 'OutSystems records,' 'OutSystems entities,' or 'low-code app data.'

Make the 'when' clause enumerate concrete situations (e.g., 'Use when the user wants to query, create, or update OutSystems records or run OutSystems workflows').

Dimension	Reasoning	Score
Specificity	It names the domain (OutSystems) and a few concrete actions ('Manage data, records, and automate workflows'), but the actions are generic and not comprehensive, matching the score-3 anchor that lists domain plus 1-2 vague actions.	3 / 5
Completeness	It gives a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with OutSystems data'), though the 'when' clause is somewhat generic rather than enumerating concrete triggers, fitting the score-4 anchor.	4 / 5
Trigger Term Quality	'OutSystems data' provides a relevant keyword but the description lacks common natural variations or synonyms (no phrases like 'OutSystems records,' 'OutSystems workflows,' 'low-code apps'), matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the trigger explicitly to 'OutSystems data' gives it a clear niche with minimal overlap risk against other skills; it is not generic but the trigger phrasing is narrow rather than richly distinct, 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/outsystems/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.