Name: nocodb
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

nocodb

Nocodb integration. Manage Projects, Users, Roles. Use when the user wants to interact with Nocodb data.

Quality

66%

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/nocodb/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 content is highly actionable with executable Membrane CLI commands and a well-sequenced, validated connection workflow. It loses points mainly to an unnecessary opening description of what NocoDB is and a 'Popular actions' section that does not actually list popular actions.

Suggestions

Cut the opening 'NocoDB is an open-source, self-hostable Airtable alternative...' paragraph and the 'Use action names and parameters as needed.' filler; assume Claude knows what NocoDB is.

Populate the 'Popular actions' section with a few real Nocodb action examples (e.g. list tables, create row, query records) instead of only pointing to 'action list'.

Fix the dangling 'skip to Step 2' reference by labeling the searching/running-actions section as Step 2 or removing the cross-reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but opens with marketing-style background Claude already knows ('NocoDB is an open-source, self-hostable Airtable alternative...It's used by developers and business users to build internal tools') and includes padded phrasing like 'so you can focus on the integration logic rather than auth plumbing' and 'Use action names and parameters as needed.'	3 / 5
Actionability	It provides copy-paste-ready commands for the full flow (install, login, connection ensure, action list/run, request proxy) plus a concrete flag table, but the 'Popular actions' section only tells you to discover actions rather than listing any actual Nocodb actions, leaving a minor gap.	4 / 5
Workflow Clarity	The connection lifecycle is clearly sequenced with state-based feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED then re-poll, check error fields on CONFIGURATION_ERROR/SETUP_FAILED), but the 'skip to Step 2' reference dangles with no labeled Step 2, a minor navigation gap.	4 / 5
Progressive Disclosure	No bundle files are present and the body is well-sectioned with clear headers, so navigation is easy; however the ~150-line doc inlines the full connection state machine and request-flag table that could live in a separate reference, a minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

66%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 in third-person voice and is clearly anchored to the Nocodb product, keeping conflict risk low. Its main weakness is thin action specificity and limited trigger-term coverage beyond the product name itself.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'Create and query Projects, Tables, Rows, and Views; manage Users and Roles'.

Broaden the trigger clause with natural synonyms users say, e.g. 'Use when the user wants to work with Nocodb spreadsheets, tables, rows, or Airtable-style data'.

Align the listed resources with the body's full overview (add Table, Row, View, Team, Plugin) so the description's coverage matches the skill's scope.

Dimension	Reasoning	Score
Specificity	It names the domain and lists 'Manage Projects, Users, Roles', but 'Manage' is a single generic verb applied to entities rather than concrete actions (create/list/update/delete), and the overview shows more resources (Table, Row, View, Team, Plugin) than the description covers.	3 / 5
Completeness	Both 'what' ('Nocodb integration. Manage Projects, Users, Roles.') and 'when' ('Use when the user wants to interact with Nocodb data') are present and explicit, but the trigger is a single phrase rather than a rich set of concrete trigger phrases, so it stops short of a 5.	4 / 5
Trigger Term Quality	The natural trigger 'Use when the user wants to interact with Nocodb data' surfaces the key keyword 'Nocodb', but it lacks common variations or synonyms (spreadsheet, Airtable, database, tables, rows) that users might actually say.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the specific named product 'Nocodb' with the trigger 'interact with Nocodb data' gives it a clear niche and minimal risk of triggering for unrelated skills.	5 / 5
	Total	15 / 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/nocodb/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.