Name: kintent
Rating: 56.8 (1 reviews)
Author: membranedev

kintent

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

Quality

65%

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/kintent/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 is a strongly actionable, well-structured CLI integration guide with concrete commands and a clear connection workflow that includes validation and polling feedback loops. Its main weaknesses are moderate explanatory padding in the intro and best-practices prose, and a dangling 'Step 2' reference that slightly muddies the workflow sequence.

Suggestions

Trim the intro paragraph and internal-mechanics prose (e.g. 'The URL is normalized to a domain...') to assume Claude's competence and lift conciseness.

Resolve the dangling 'skip to Step 2' reference by explicitly numbering the post-connection steps (search actions -> run actions) so the workflow sequence is unambiguous.

Add an explicit error-recovery loop for action runs (check the response 'output'/'error' fields and retry or surface clientAction), since these are data-mutating operations against an external API.

Dimension	Reasoning	Score
Conciseness	The bulk is lean command blocks, but the intro marketing-style paragraph ('Kintent is a SaaS platform... used by legal, security, and compliance professionals'), internal-mechanics prose ('The URL is normalized to a domain and matched against known apps'), and the verbose 'Best practices' section add explanation that could be tightened, matching the score-3 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	Concrete, copy-paste-ready commands cover the common cases ('npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://www.kintent.com/" --json', 'membrane action run <actionId> --connectionId=CONNECTION_ID --json'), with only well-explained placeholders (<agentType>, CONNECTION_ID, <actionId>) as gaps, fitting the score-4 'mostly executable guidance; minor gaps' anchor.	4 / 5
Workflow Clarity	The connection setup has a clear sequence with explicit validation checkpoints and feedback loops (poll until 'state is no longer BUILDING', re-poll after CLIENT_ACTION_REQUIRED, handle CONFIGURATION_ERROR/SETUP_FAILED), but the 'skip to Step 2' reference is dangling and action-run failures lack an explicit error-recovery loop, so it sits at 4 rather than 5.	4 / 5
Progressive Disclosure	The body is well-organized into clear sections (Install, Authentication, Connecting, Searching, Running actions, Proxy requests, Best practices), links to official docs, and pushes deep API reference to runtime discovery ('membrane action list --intent=QUERY'), giving good structure with only minor organization gaps; with no bundle files it fits the score-4 anchor rather than the file-split score-5.	4 / 5
	Total	15 / 20 Passed

Description

62%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 cleanly answers both what and when with an explicit 'Use when' clause anchored on the distinctive 'Kintent' proper noun, but its action verbs are generic and its trigger-term coverage is thin (essentially one keyword). It is solid but not comprehensive.

Suggestions

Replace generic verbs with concrete Kintent actions, e.g. 'Manage compliance controls, records, and tasks; automate risk-assessment and data-mapping workflows' to lift specificity.

Broaden trigger terms beyond the single keyword 'Kintent', adding natural phrases like 'compliance program', 'privacy program', or 'data mapping'.

Expand the 'when' clause to list multiple concrete triggers, e.g. 'Use when the user mentions Kintent, privacy compliance, controls, or records.'

Dimension	Reasoning	Score
Specificity	Names the domain ('Kintent integration') and lists actions ('Manage data, records, and automate workflows'), but the verbs are generic ('Manage', 'automate') rather than concrete like 'extract' or 'fill', so it sits between the score-2 'generic actions' and score-4 'several specific actions' anchors.	3 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Kintent data'), but the trigger phrase is a single one rather than the comprehensive concrete triggers of the score-5 anchor, so it lands at 4.	4 / 5
Trigger Term Quality	The natural trigger is essentially the proper noun 'Kintent' / 'Kintent data' ("Use when the user wants to interact with Kintent data"), which is relevant but lacks common variations a user might say (e.g. 'compliance', 'privacy', 'data mapping') that the body mentions, matching the score-3 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The unique named platform 'Kintent' gives a clear niche with minimal conflict risk ('interact with Kintent data'), but the generic action verbs ('Manage data', 'automate workflows') leave minor theoretical overlap with other SaaS-data skills, fitting the score-4 'mostly distinct; minor overlap risk' anchor rather than the fully-distinct score-5.	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/kintent/SKILL.md
Commit: f484c82

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