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

Blog Docs Log in Get started

cyclr

Cyclr integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cyclr 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/cyclr/SKILL.md

Quality

Content

56%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 CLI workflow guidance is genuinely actionable and well-sequenced with state-based checkpoints, but the document is dragged down by a massive inlined list of generic data-domain terms that wastes context and should live in a separate reference file.

Suggestions

Remove or relocate the ~170-item 'Data ...' bullet list into a separate reference file (e.g., references/categories.md) and link to it; the inlined list is padding that burns tokens without aiding execution.

Fix the dangling 'skip to Step 2' cross-reference by either labeling the 'Searching for actions' section as Step 2 or removing the forward reference.

Trim introductory prose that restates what Cyclr is (the first paragraph), since the description frontmatter already covers the platform's purpose.

Dimension	Reasoning	Score
Conciseness	The ~170-item bullet list of "Data X" / "Data X Platform" entries is heavy padding that adds no actionable value and that Claude does not need, fitting the anchor for noticeably verbose content with several padded sections.	2 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, auth, connecting, action search/run, and proxying, plus a flags table, with only minor gaps (e.g., unresolved placeholders like CONNECTION_ID).	4 / 5
Workflow Clarity	The connection flow is a clear state-driven sequence (ensure -> poll --wait -> branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with feedback loops (re-poll after user action), though the dangling "skip to Step 2" reference leaves a minor gap.	4 / 5
Progressive Disclosure	Section headers organize the CLI guidance, but the large inlined category list clearly belongs in a separate reference file and no bundle references are used, matching the anchor for present-but-imperfect structure with content that should be separated kept inline.	3 / 5
	Total	13 / 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 is concise, third-person, and clearly anchored to the Cyclr platform with an explicit 'Use when' clause, giving it good completeness and distinctiveness. Its main weakness is generic action verbs and thin natural-language trigger coverage beyond the platform name itself.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Cyclr-specific actions (e.g., "Build and deploy Cyclr integration flows, manage connectors and templates, schedule and run workflows").

Expand the 'Use when' clause with natural trigger phrases users would say, e.g., "Use when the user wants to set up Cyclr integrations, manage Cyclr connectors, or automate Cyclr workflows."

Dimension	Reasoning	Score
Specificity	It names the domain ("Cyclr integration") and a couple of actions ("Manage data, records, and automate workflows"), but those actions are generic rather than concrete, matching the anchor for naming the domain with 1-2 non-comprehensive actions.	3 / 5
Completeness	It states both what it does ("Manage data, records, and automate workflows") and when to use it ("Use when the user wants to interact with Cyclr data"), but the 'when' clause is fairly narrow and could be more explicit, fitting the anchor for having both with a less-specific 'when'.	4 / 5
Trigger Term Quality	The only genuinely natural trigger keyword is "Cyclr" (repeated in "interact with Cyclr data"); the surrounding terms ("manage data", "records", "workflows") are generic and lack synonyms or common variations.	3 / 5
Distinctiveness Conflict Risk	"Cyclr" is a specific named platform, so the trigger ("interact with Cyclr data") carves a clear niche with minimal overlap risk against 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/cyclr/SKILL.md
Commit: f484c82

Reviewed: ~15 hours 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.