Name: cyfe
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

cyfe

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

Quality

70%

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

Quality

Content

67%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 strong, executable Membrane CLI guidance with a clear connection-readiness workflow and good section structure. Its main weaknesses are the padded generic taxonomy list that hurts token efficiency and a 'Popular actions' section that promises examples but delivers none.

Suggestions

Cut or collapse the generic data-category bullet list (Sales Data, Marketing Data, HR Data, etc.) — these are concepts Claude already knows and add little actionable value.

Make the 'Popular actions' section actually list a few common Cyfe actions (e.g. create dashboard, add widget, pull metric) instead of only redirecting to `membrane action list`.

Add a brief validation/confirmation step after running actions (e.g. check the `output`/`error` field and retry or report on failure) to strengthen the feedback loop.

Dimension	Reasoning	Score
Conciseness	The CLI/auth/action sections are lean and efficient, but the ~50-item taxonomy list (Dashboard, Widget, ... Sales Data, Marketing Data, HR Data, etc.) is padded with generic data-category concepts Claude already knows, pulling it down from a 4.	3 / 5
Actionability	Provides copy-paste-ready commands for install, login, connection ensure, polling, action list/run, and proxy with a flags table; minor gaps remain — the 'Popular actions' header only redirects to `action list` rather than naming any popular actions.	4 / 5
Workflow Clarity	Clear sequenced workflow (install -> login -> ensure connection -> poll until READY / handle CLIENT_ACTION_REQUIRED -> search -> run) with an explicit readiness checkpoint and state-handling feedback; validation of action results is absent but the described flow is not framed as destructive, so it holds at 4 rather than being capped at 3.	4 / 5
Progressive Disclosure	Single-file skill with no bundle files present; sections are well-organized and clearly headed, so structure is good. It sits at 4 rather than 5 because the file exceeds 50 lines and the long inline taxonomy list could be trimmed or split out.	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 clearly identifies the Cyfe niche with an explicit 'Use when...' trigger, giving it strong distinctiveness and completeness. Its main weakness is specificity — the listed actions ('manage data', 'automate workflows') are generic rather than naming concrete Cyfe operations.

Suggestions

Replace generic verbs with concrete Cyfe operations, e.g. 'Create dashboards, add widgets, pull metrics from data sources, and schedule reports.'

Expand the 'Use when' clause with natural trigger phrases users would actually say: 'Use when the user mentions Cyfe, business dashboards, widgets, or wants to visualize/report on data sources.'

Mention the Membrane-backed integration angle (auth-handled API access) to distinguish it from raw Cyfe API work.

Dimension	Reasoning	Score
Specificity	Names the domain ('Cyfe integration') and lists a few actions ('Manage data, records, and automate workflows'), but the actions are generic/abstract rather than concrete API operations, fitting between the 'minimal or generic' (2) and '1-2 concrete actions' (3) anchors.	3 / 5
Completeness	Explicitly answers both what ('Cyfe integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Cyfe data.'); the 'when' is present but gives a single trigger phrase rather than multiple concrete ones, so it stops short of a 5.	4 / 5
Trigger Term Quality	Includes the natural app-name trigger ('Cyfe') plus related terms ('data', 'records', 'workflows') in an explicit 'Use when...' clause; good coverage though a few natural variations (dashboards, widgets, reports) are missing.	4 / 5
Distinctiveness Conflict Risk	The named app 'Cyfe' is a clear niche trigger with minimal overlap risk against other skills; a user mentioning Cyfe would unambiguously select this skill.	5 / 5
	Total	16 / 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/cyfe/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.