Name: kintone
Rating: 60.8 (1 reviews)
Author: membranedev

kintone

Kintone integration. Manage Apps, Users, Organizations, Groups, Views, Reports. Use when the user wants to interact with Kintone data.

Quality

71%

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

Quality

Content

68%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 highly actionable with executable CLI commands and a clear connection-state workflow, but it loses points on a padded marketing intro and a lack of validation/verification steps for the destructive batch record operations it documents.

Suggestions

Cut the opening marketing paragraph to a single factual line about what Kintone is, and remove "auth plumbing"-style prose asides.

Add an explicit verify step after batch/destructive actions, e.g. after `update-records`/`delete-records`, run `membrane action run get-records` (or the relevant get) to confirm the change took effect before reporting success.

Consider moving the 16-row popular-actions catalog and the proxy flag table into a separate REFERENCE.md linked one level deep to slim the main SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight command reference, but the opening marketing paragraph ("customizable workplace platform... streamline their processes without needing extensive coding knowledge") and asides like "so you can focus on the integration logic rather than auth plumbing" are unnecessary explanation that could be trimmed.	3 / 5
Actionability	Copy-paste-ready commands cover the full common path (install, login, connection ensure, action list, action run, request proxy) with concrete flags, plus a 16-row action catalog keyed by action id, matching the fully-executable anchor.	5 / 5
Workflow Clarity	The connection setup is well sequenced with explicit state checks (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-after-action feedback loop, but the destructive/batch record operations (delete-records, update-records, create-records) have no verification step, invoking the workflow-clarity cap of 3 for batch ops without validation.	3 / 5
Progressive Disclosure	The file is well organized with clear section headers and no broken or nested references, but it is a single ~160-line monolith with the action catalog and proxy-flag table inlined rather than split into one-level-deep reference files, leaving a minor organization gap.	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 names the Kintone niche and includes an explicit "Use when" clause, giving strong distinctiveness and completeness. It is weakened by a single generic action verb ("Manage") and missing common trigger terms like "records" and "fields".

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Create, query, update, and delete records, comments, and form fields across Kintone Apps."

Add high-frequency trigger terms users actually say ("records", "fields", "forms", "Kintone database") to broaden natural-language matching.

Make the "Use when" clause more specific, e.g. "Use when the user wants to query or modify Kintone records, apps, users, or groups."

Dimension	Reasoning	Score
Specificity	"Manage Apps, Users, Organizations, Groups, Views, Reports" enumerates six concrete entity categories, but "Manage" is a single generic verb and no concrete CRUD actions (create/query/update/delete records) are named, matching the domain-plus-actions-but-not-comprehensive anchor.	3 / 5
Completeness	Both what ("Kintone integration. Manage Apps, Users...") and when ("Use when the user wants to interact with Kintone data") are present, but the trigger clause is generic rather than listing concrete triggering scenarios.	4 / 5
Trigger Term Quality	Natural Kintone vocabulary is well covered ("Kintone", "Apps", "Users", "Organizations", "Groups", "Views", "Reports", "Kintone data"), but common variations like "records", "fields", "forms", and "database" are missing.	4 / 5
Distinctiveness Conflict Risk	"Kintone integration" names a specific niche platform with distinct triggers ("interact with Kintone data"), giving it a clear niche and minimal overlap with other skills.	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/kintone/SKILL.md
Commit: f484c82

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