Name: contis
Rating: 65.60000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

contis

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

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/contis/SKILL.md

Quality

Content

92%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 executable commands, a clear validated workflow, and clean organization. The only minor weakness is a few sentences of mild over-explanation that could be trimmed for token efficiency.

Suggestions

Trim editorial filler such as 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection' to improve conciseness.

Tighten the Agent Types line ('claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling...') into a concise list without the explanatory tail.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with copy-paste commands and no padded concept explanations, but a few sentences (e.g. 'so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') could be trimmed, fitting 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	It provides fully executable, copy-paste-ready CLI commands for install, auth, connection, action discovery, action runs, and proxy requests, plus a complete flags table covering the common cases.	5 / 5
Workflow Clarity	The connection flow is a clearly sequenced state machine (ensure -> poll -> handle CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR -> READY) with explicit validation via state checks and feedback loops for error recovery.	5 / 5
Progressive Disclosure	As a single-file skill with no bundle files, it is well-organized into clear navigable sections and inlines only content appropriate to the overview, satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	19 / 20 Passed

Description

66%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 covers what and when with a distinctive brand trigger, but the capability list is generic and lacks natural term variations. Strengthening the concrete actions and trigger synonyms would raise specificity and trigger_term_quality.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with specific Contis actions such as 'issue virtual and physical cards, process payments, and manage transactions and accounts'.

Add natural trigger variations users might say, e.g. 'Use when the user wants to issue cards, process payments, or query Contis transactions and accounts.'

Tighten the 'when' clause with concrete trigger phrases rather than the broad 'interact with Contis data'.

Dimension	Reasoning	Score
Specificity	Names the Contis domain with a couple of concrete actions ('Manage data, records, and automate workflows'), but they are generic and not comprehensive, fitting the score-3 anchor better than 4.	3 / 5
Completeness	It states both what ('Contis integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Contis data.'), though the trigger clause is somewhat generic rather than concrete.	4 / 5
Trigger Term Quality	The brand term 'Contis' is the natural keyword a user would say, but there are no synonyms, variations, or file extensions, leaving it at 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The named brand 'Contis' creates a clear niche with distinct triggers and minimal conflict risk, as no other skill would fire on Contis-related requests.	5 / 5
	Total	15 / 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/contis/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.