CtrlK
BlogDocsLog inGet started
Tessl Logo

cflow

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

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/cflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 real, executable CLI commands and a useful action catalog, and it is well sectioned. It is held back by some padded prose and a lack of validation checkpoints around destructive record operations.

Suggestions

Add a validation/verification step around mutating actions (e.g., confirm the record id and re-fetch with get-record after create-record/update-record) so the workflow satisfies the destructive-operations feedback-loop requirement.

Fix the "skip to Step 2" reference by explicitly labeling the downstream section as Step 2, or reword it to name the section (e.g., "skip to Searching for actions").

Trim filler prose such as "so you can focus on the integration logic rather than auth plumbing" and "Use action names and parameters as needed." to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but includes unnecessary prose such as "so you can focus on the integration logic rather than auth plumbing", "Use action names and parameters as needed.", and a what-is-Cflow intro that could be trimmed.

3 / 5

Actionability

It provides fully executable, copy-paste-ready commands for install, auth, connection, action search/run, and proxying, plus a concrete action-key catalog and flag table covering the common cases.

5 / 5

Workflow Clarity

The connection-state flow is well sequenced, but mutating actions (create-record, update-record) lack validation/verification steps, and "skip to Step 2" references an unlabeled step, so the destructive-operations cap applies.

3 / 5

Progressive Disclosure

The single file is well organized into clear sections (install, auth, connecting, searching, running, proxy, best practices), though the action catalog and flag reference are inlined with no deeper references signaled, a minor organization gap.

4 / 5

Total

15

/

20

Passed

Description

73%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 third-person, names a distinct niche, and includes an explicit "Use when" trigger, which gives it solid completeness and low conflict risk. Its main weakness is generic action verbs and a single narrow trigger phrase rather than multiple concrete ones.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the domain and a few actions, but the verbs ("manage", "automate") are generic rather than concrete like extracting or filling, so it stops at naming 1-2 concrete actions.

3 / 5

Completeness

It has both a clear "what" ("Cflow integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with Cflow data"), but the trigger is a single narrow clause rather than multiple concrete trigger phrases.

4 / 5

Trigger Term Quality

"Cflow" is a strong natural brand trigger supported by "data", "records", and "workflows", but common synonyms or phrasings users might say are missing, so it is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

"Cflow" is a distinct named application with a clear niche and trigger, giving it minimal overlap or conflict risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.