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

Blog Docs Log in Get started

cinc

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

Quality

Content

63%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 content is highly actionable with concrete executable commands, but it over-inlines reference material and lacks validation checkpoints for destructive operations. Splitting bulk reference content into separate files and adding verification steps would meaningfully improve it.

Suggestions

Move the 30-item entity list and clientAction schema enumeration into a separate reference file and link to it from the overview.

Add explicit validation/verification checkpoints before destructive or batch actions (e.g., confirm lead IDs before 'delete-lead', verify output after action run or proxy POST).

Trim the generic entity bullet list and the padded best-practice explanations to reduce token load.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with command snippets and tables, but the long inlined 'CINC Overview' entity list (~30 generic bullet items) and the verbose clientAction field enumeration add padding that could be trimmed or moved.	3 / 5
Actionability	Provides copy-paste-ready, executable commands for install, login, connection ensure/get, action list/run, and proxy requests, with concrete flags and JSON examples covering the common cases.	5 / 5
Workflow Clarity	The connect-to-CINC flow is sequenced with polling and state handling, but it involves batch/destructive operations (deleting leads, running actions, proxy POSTs) with no validation/verification checkpoints, capping clarity at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	Sections are reasonably organized, but no bundle files exist and large reference-style content (the 30-item entity list, the full clientAction schema, and the Popular actions table) is inlined rather than split into separate reference files.	3 / 5
	Total	14 / 20 Passed

Description

60%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 names a clear, specific niche (CINC CRM for real estate) and includes an explicit 'Use when' trigger, which is its main strength. Its weakness is generic action verbs and limited keyword coverage that misses the natural terms users would say.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete CINC actions such as 'create and update leads, track transactions, manage contacts and tasks'.

Broaden trigger keywords to include natural user phrasing like 'CRM', 'leads', 'transactions', 'real estate contacts'.

Tighten the 'Use when' clause to reference real-estate CRM tasks explicitly to further reduce overlap with generic data skills.

Dimension	Reasoning	Score
Specificity	Names the CINC domain and several action categories ('Manage data, records, and automate workflows'), but the actions are generic (manage, automate) rather than a concrete list like 'create leads, track transactions, send invoices'.	3 / 5
Completeness	Provides a clear 'what' (CINC integration: manage data, records, automate workflows) and an explicit 'when' clause ('Use when the user wants to interact with CINC data'), though the trigger phrasing is somewhat narrow.	4 / 5
Trigger Term Quality	Includes 'CINC' and 'CINC data' as relevant keywords, but lacks common variations a user would naturally say ('CRM', 'leads', 'transactions', 'real estate').	3 / 5
Distinctiveness Conflict Risk	The CINC niche is specific and unlikely to conflict with other skills, though the generic verb 'Manage data, records' adds minor overlap risk with other data-integration skills.	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/cinc/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.