Name: chift
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

chift

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

Quality

59%

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

Quality

Content

61%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 a well-structured, actionable CLI guide with a genuine connection-state feedback loop, but it carries some filler and duplication, placeholder-only examples, and lacks verification guidance before destructive action runs or proxy requests.

Suggestions

Add a verification/confirmation step before running actions or sending mutating proxy requests (e.g. inspect outputSchema or confirm with the user before DELETE/PUT/PATCH) to lift the destructive-operations cap on workflow clarity.

Remove the filler 'Chift Overview' entity tree and merge the duplicated 'Popular actions' command into 'Searching for actions' to tighten conciseness.

Include at least one fully-worked end-to-end example with realistic values (a sample actionId, intent, and proxy path) so the guidance is copy-paste ready rather than placeholder-only.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight, executable CLI commands, but the 'Chift Overview' entity tree plus 'Use action names and parameters as needed.' is filler, and the `action list` command is duplicated across 'Searching for actions' and 'Popular actions', fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, auth, connection, action list/run, and proxy plus a full flags table, but every example uses placeholders (CONNECTION_ID, QUERY, /path/to/endpoint) with no fully-worked end-to-end example, fitting 'mostly executable... with minor gaps'.	4 / 5
Workflow Clarity	A clear install→auth→connect→search→run sequence exists with a real polling/state feedback loop for connections, but the proxy supports destructive methods (DELETE/PUT/PATCH) and action runs have no verification step before execution, so the destructive/batch-operations cap applies and holds this at 3 rather than 4.	3 / 5
Progressive Disclosure	As a single CLI-guide file with no external references needed, it is well-organized into clear headers with content appropriately placed inline; the only organization gap is the redundant 'Popular actions' section overlapping 'Searching for actions', fitting 'good structure; minor organization gaps'.	4 / 5
	Total	14 / 20 Passed

Description

57%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 answers both what and when with an explicit trigger clause and a distinctive product name, but relies on generic action verbs and thin trigger phrasing. It is solid but not comprehensive.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Chift capabilities such as syncing records, fetching invoices/payrolls, or triggering specific API actions.

Expand the trigger clause with concrete phrases a user would say, e.g. 'Use when the user mentions Chift, wants to sync Chift data, or automate Chift integrations.'

Add common synonyms or surface terms (e.g. 'Chift API', 'Chift connectors', 'SaaS integration') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the Chift domain, but the actions ('Manage data, records, and automate workflows') are generic verbs rather than concrete capabilities, matching the 'names the domain but actions are minimal or generic' anchor rather than the concrete 1-2 actions of score 3.	2 / 5
Completeness	Both a clear 'what' (Chift integration; manage data, records, automate workflows) and an explicit 'Use when the user wants to interact with Chift data' trigger are present, but the 'when' is generic and could list more specific triggers, matching anchor 4 rather than the concrete-trigger-phrases of 5.	4 / 5
Trigger Term Quality	It includes some natural terms ('Chift', 'data', 'records', 'workflows', 'interact with Chift data') but offers no synonyms or common variations a user might say, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The named platform 'Chift' gives a clear niche and distinctive trigger with minimal conflict risk, but the generic verbs ('manage data', 'automate workflows') create minor overlap with other integration skills, fitting 'mostly distinct; minor overlap risk'.	4 / 5
	Total	13 / 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/chift/SKILL.md
Commit: f484c82

Reviewed: 3 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.