Name: octolis
Rating: 61.6 (1 reviews)
Author: membranedev

octolis

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

Quality

72%

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

Quality

Content

82%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 body is highly actionable, with executable CLI commands and a connection state-machine that includes validation and retry logic. Its main gaps are inconsistent step numbering and an inline-everything structure that, while well-organized, does not split heavier reference material into separate files.

Suggestions

Fix the workflow numbering: label the post-connection section 'Step 2' so the 'skip to Step 2' reference resolves, and renumber '1b' consistently.

Move the proxy flag reference table and the Octolis entity overview into a dedicated reference file, keeping SKILL.md as a lean overview with one-level-deep links.

Trim the marketing framing in the intro and best-practices to the concrete technical facts to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands and a compact flag table, but the marketing-toned intro ('helps marketing teams centralize and transform customer data') and best-practices phrasing ('burn less tokens') are minor over-explanation that could be trimmed, fitting the efficient-with-minor-instances anchor.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands across the common cases (install, login, connection ensure, action list/run, request proxy) with concrete flags and JSON input examples, matching the fully-executable anchor.	5 / 5
Workflow Clarity	The connection flow is sequenced with explicit state checkpoints and a poll-retry feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the 'skip to Step 2' reference points to an unlabeled section and the '1b' numbering is inconsistent, fitting the clear-sequence-with-minor-gaps anchor.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested references, but at ~145 lines it exceeds the simple-skill threshold and keeps everything inline (e.g., the full proxy flag table, the bare entity list) that could be split out, fitting the good-structure-with-minor-gaps anchor.	4 / 5
	Total	17 / 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 successfully pairs a clear capability statement with an explicit 'Use when' trigger and anchors on a named platform, keeping conflict risk low. Its weakness is generic action verbs and a lack of trigger-term synonyms, which limit specificity and trigger-term quality.

Suggestions

Replace generic verbs with concrete Octolis-specific actions (e.g., 'Sync source schemas, map destinations, build datamart models') to lift specificity.

Add natural trigger synonyms and entity terms users say (e.g., 'customer data, destinations, sources, datamarts') alongside 'Octolis'.

Tighten the 'when' clause with concrete trigger phrases such as 'Use when the user mentions Octolis, customer data pipelines, or destination mappings'.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Octolis domain plus 2-3 actions, but the actions ("manage data", "records") are generic rather than concrete, matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It states both a clear "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Octolis data"), but the trigger could be more specific with concrete phrases, matching the anchor where both are present yet 'when' could be more explicit.	4 / 5
Trigger Term Quality	The trigger relies on the brand name "Octolis" and a single phrase ("interact with Octolis data"); there are relevant keywords but no natural synonyms or variations users might say, fitting the anchor for some keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific platform "Octolis" gives it a distinct niche with minimal conflict risk, though the generic "manage data" actions leave minor overlap with other data-handling skills, fitting the mostly-distinct anchor.	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/octolis/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.