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

cronfree

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

Quality

Content

75%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 delivers highly actionable, executable CLI guidance with a sensible workflow and connection-state feedback loop. Its main weaknesses are a cryptic unexplained overview section, a duplicated action-discovery section, and slightly implicit step labeling.

Suggestions

Either explain or remove the cryptic "Cronfree Overview" bullet tree (Meeting/Availability/Account/API Key) which currently adds tokens without guidance.

Merge the "Searching for actions" and "Popular actions" sections, which both demonstrate `membrane action list`, to remove redundancy.

Label the post-connection steps explicitly (e.g. "Step 2: Search for actions") so the "skip to Step 2" reference resolves clearly.

Dimension	Reasoning	Score
Conciseness	Mostly efficient executable commands, but the cryptic "Cronfree Overview" bullet list (Meeting/Availability/Account/API Key) and the duplicated action-list command in both "Searching for actions" and "Popular actions" add unnecessary tokens, fitting the 3 anchor over the lean 4.	3 / 5
Actionability	Commands are copy-paste ready across the full flow (install, login, connection ensure/get with --wait, action list/run with --input, request with a flags table), covering the common cases, matching the fully-executable 5 anchor.	5 / 5
Workflow Clarity	A clear install→auth→connect→search→run→proxy sequence exists with a real feedback loop (poll --wait until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but the "Step 2" reference is not labeled as a section and some checkpoints are implicit, fitting the 4 anchor.	4 / 5
Progressive Disclosure	With no bundle files present, content is organized into well-separated sections that mostly place material appropriately; minor organization gaps (cryptic overview, duplicated section) keep it at 4 rather than 5.	4 / 5
	Total	16 / 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 correctly identifies the Cronfree niche and includes a usable Use-when clause, but its action list is generic and it omits the most natural trigger terms (scheduling, cron, recurring tasks). It is solid but not exemplary.

Suggestions

Replace generic actions with concrete Cronfree capabilities, e.g. "schedule recurring tasks, manage cron jobs, and trigger workflows".

Add natural trigger phrases users actually say, such as "Use when the user wants to schedule tasks, set up cron jobs, or automate recurring Cronfree workflows".

Make the Use-when clause more specific about the triggering situations rather than the generic "interact with Cronfree data".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Cronfree domain plus a couple of actions, but the actions are generic and not comprehensive, matching the 3 anchor rather than the multiple-specific-actions 4 anchor.	3 / 5
Completeness	It states what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Cronfree data"), but the when clause is somewhat generic, matching the 4 anchor where both are present but the when could be more explicit.	4 / 5
Trigger Term Quality	"automate workflows" and "interact with Cronfree data" provide some natural keywords, but the core user phrasings ("schedule tasks", "cron jobs", "recurring tasks") are missing, fitting the 3 anchor for partial keyword coverage.	3 / 5
Distinctiveness Conflict Risk	"Cronfree integration" carves a clear niche tied to a named product, leaving only minor overlap risk with other generic automation skills, which fits the 4 anchor better than the broad 3.	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/cronfree/SKILL.md
Commit: f484c82

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