Name: incorta
Rating: 59.2 (1 reviews)
Author: membranedev

incorta

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

Quality

68%

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

Quality

Content

71%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 skill is highly actionable with concrete, executable Membrane CLI commands and a solid state-handling workflow, but it is token-heavy due to an inlined glossary and conceptual intro, and it does not use progressive disclosure to offload reference material. Splitting reference material into bundled files and trimming the glossary would improve both conciseness and progressive disclosure.

Suggestions

Move the 38-item Incorta vocabulary list and the proxy flag table into a references/ file (e.g. INCORTA_TERMS.md, PROXY_REFERENCE.md) and link to them, improving both progressive_disclosure and conciseness.

Cut the conceptual "Incorta is a data analytics platform..." intro; assume Claude's competence and lead straight with the CLI workflow.

Add an explicit validation checkpoint for destructive action runs (e.g., inspect inputSchema/outputSchema and confirm scope with the user before running mutating actions) to strengthen workflow_clarity.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient operational CLI content, but the conceptual intro ("Incorta is a data analytics platform that provides self-service data exploration...") and the 38-item bare glossary are padding that could be trimmed, fitting the mostly-efficient-but-could-be-tighter anchor.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure/get with --wait, action list, action run with JSON input, and request proxy, plus a complete flag table, fully covering the common cases.	5 / 5
Workflow Clarity	The connect-search-run sequence is clear with real checkpoints (polling --wait, READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR state handling, discover-before-build), but it is sectioned rather than numbered and lacks an explicit verify-before-destructive-run loop, leaving minor validation gaps.	4 / 5
Progressive Disclosure	The body is well-sectioned but is a 175-line monolith with no bundle references, and reference material (the 38-item glossary and the proxy flag table) is inlined rather than split into separate files, matching the some-structure-but-inline-content anchor.	3 / 5
	Total	15 / 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 cleanly covers what and when and is well-scoped to a distinct named platform, but its action list and trigger terms are generic and could be more concrete. Tightening the verbs and adding common Incorta-specific trigger phrases would raise specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Incorta actions (e.g., "query dashboards and insights, manage schemas and materialized views, schedule jobs") to lift specificity.

Expand the trigger clause with natural variations users say, e.g. "Use when the user wants to query Incorta dashboards, inspect schemas, or automate Incorta jobs."

Mirror the trigger terms to the listed actions so the "when" covers records and workflows, not just data.

Dimension	Reasoning	Score
Specificity	The description names the Incorta domain and three actions ("Manage data, records, and automate workflows"), but the verbs and objects are generic rather than concrete like the anchor-4 examples, so it sits at the domain-plus-couple-actions level.	3 / 5
Completeness	It answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Incorta data"), but the trigger is a single generic phrase rather than the multiple concrete triggers required for a 5.	4 / 5
Trigger Term Quality	"Incorta" and "Incorta data" are relevant natural keywords a user would say, but coverage is limited to essentially one term with no common variations (dashboards, reports, schemas, .incorta), matching the some-keywords-but-missing-synonyms anchor.	3 / 5
Distinctiveness Conflict Risk	Being explicitly scoped to the named Incorta platform gives it a clear niche with distinct triggers and minimal overlap risk with other skills.	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/incorta/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.