CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cinc

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

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/cinc/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 strongly actionable integration guide: copy-paste-ready Membrane CLI commands for auth, connection setup with state-machine handling, action discovery/execution, and proxy fallback. Main weaknesses are the broken step references ('Step 2', '1b' with no matching labels), the low-value bare entity list, and no validation guidance for action results or destructive operations.

Suggestions

Fix the incoherent step numbering: either label the sections 'Step 1'/'Step 2' consistently or replace 'skip to **Step 2**' and '#### 1b.' with descriptive headings.

Cut or enrich the 27-item bare entity list ('**Matter**', '**Note**', ...) — either move it to a reference file or annotate entries with what each object is for; also delete the filler line 'Use action names and parameters as needed.'

Add a validation step after running actions — e.g. check the output/error fields of 'membrane action run' before proceeding, especially before destructive actions like delete-lead.

DimensionReasoningScore

Conciseness

The body is mostly lean, executable command blocks and tables with no over-explanation of concepts Claude already knows. The 27-item entity list under 'CINC Overview' (e.g. '**Matter**', '**Note**') is bare names with no accompanying guidance and reads as padding, plus the filler line 'Use action names and parameters as needed.' — minor trimmable instances matching score 4 rather than the fully lean score 5.

4 / 5

Actionability

Every section gives copy-paste-ready commands with exact flags: 'npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://www.cincpro.com/" --json', 'membrane action run <actionId> --connectionId=CONNECTION_ID --input ... --json', plus a flags table for proxy requests and a 14-row popular-actions table covering common cases. It is fully executable and covers the common cases, matching the score 5 anchor.

5 / 5

Workflow Clarity

The sequence (install → login incl. headless flow → connect → poll state → search → run) is clear, with a genuine feedback loop for connection states (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR with clientAction fields to inspect). It falls short of 5 due to incoherent step numbering — 'skip to **Step 2**' and '#### 1b.' reference steps that are never labeled elsewhere — and no validation guidance for action-run results or destructive actions like delete-lead, which are minor gaps fitting score 4's 'most checkpoints present'.

4 / 5

Progressive Disclosure

No bundle files exist, so all content is necessarily inline in SKILL.md; sections are clearly headed and easy to navigate (CLI setup, connection, actions, proxy, best practices). The bare entity list and full actions table are content that could live in a separate reference file if a bundle were used, which keeps it at 'Good structure; most content appropriately placed; minor organization gaps' rather than 5.

4 / 5

Total

17

/

20

Passed

Description

48%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 uses third person, has an explicit 'Use when' clause, and anchors on the distinctive CINC product name. Its weakness is the 'what' half: 'Manage data, records, and automate workflows' is generic filler that could describe any integration, with no concrete capabilities (lead management, notes, agents, webhooks) that this skill demonstrably supports.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete capabilities drawn from the skill, e.g. 'Manage leads, agents, labels, notes, and webhook subscriptions in CINC (real estate CRM)' to raise specificity and completeness.

Add natural trigger terms and synonyms users would actually say — e.g. 'CINC, CINCpro, real estate CRM, leads' — so the description fires on realistic phrasings.

State the integration mechanism briefly (e.g. 'runs CINC actions via the Membrane CLI') to sharpen the 'what' and further reduce overlap with other data-management skills.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the domain (CINC) but the actions are minimal and generic — no concrete operations like retrieving leads, creating notes, or managing transactions that the skill actually supports. This matches the anchor 'Names the domain but actions are minimal or generic' and falls below score 3, which requires 1-2 concrete named actions.

2 / 5

Completeness

The 'when' is explicit ("Use when the user wants to interact with CINC data") but the 'what' is vague — "Manage data, records, and automate workflows" describes virtually any integration. Because the what half is generic, this sits between the score 3 anchor (clear what, weak when) and score 4 (both present, when could be more specific), and the vague 'what' pulls it to 3.

3 / 5

Trigger Term Quality

"CINC" is the key natural term a real estate agent would say, and "data"/"records" add mild relevance, but common variations are missing (e.g., "leads", "real estate CRM", "CINCpro"). This fits 'Some relevant keywords but missing common variations or synonyms' rather than score 4, which expects good keyword coverage with only a few natural terms missing.

3 / 5

Distinctiveness Conflict Risk

"CINC" is a distinctive product name giving a clear niche with minimal conflict risk, but the surrounding phrases ("Manage data, records, and automate workflows") are generic and could overlap with other integration skills. Mostly distinct with minor overlap risk — score 4 rather than 5 because the generic action language isn't tied to CINC-specific triggers like leads or real estate CRM.

4 / 5

Total

12

/

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.

Validation — 15 / 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

Path

skills/cinc/SKILL.md

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.