Name: column
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

column

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

Quality

62%

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/column/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 delivers executable CLI guidance with a clear, checkpointed connection workflow, but is marred by a leaked non-skill sentence and some vague filler sections. No bundle files exist, so all reference scoring is against the single inline file.

Suggestions

Remove the stray sentence "I don't have enough information to do that. I need a description of the app." which appears to be leaked model output rather than skill content.

Replace the vague "Column Overview" bullet list (Table/Column/View/Integration/Automation/Dashboard) with concrete, actionable information or remove it.

Consolidate the redundant "Popular actions" section, which repeats the action-discovery command already shown under "Searching for actions".

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands, but includes a stray erroneous sentence ("I don't have enough information to do that. I need a description of the app.") and a vague "Column Overview" bullet list that add noise without value.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, auth, connection, action discovery, action execution, and proxying, with only minor gaps such as the redundant "Popular actions" section.	4 / 5
Workflow Clarity	The install → authenticate → connect → wait-for-ready → search → run sequence is clear, and the connection-state handling (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with re-polling) provides an explicit feedback loop.	4 / 5
Progressive Disclosure	Content is organized into well-labeled sections in a single file with no nested references, but the thin overview and popular-actions sections leave minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

57%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 with an explicit Use-when clause, but its actions are generic and trigger-term coverage is limited. It is reasonably distinct thanks to naming the Column app specifically.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Column-specific actions the skill actually performs.

Expand trigger terms to include natural synonyms and entity names users would say (e.g. specific Column objects or record types) beyond "interact with Column data".

Dimension	Reasoning	Score
Specificity	It names the Column domain and a couple of actions, but "Manage data, records, and automate workflows" is generic rather than concrete, matching the anchor where actions are minimal or generic.	2 / 5
Completeness	It states both what it does ("Manage data, records, and automate workflows") and when to use it ("Use when the user wants to interact with Column data"), but the trigger could be more specific, fitting the anchor that has both what and when.	4 / 5
Trigger Term Quality	It includes some relevant keywords ("Column", "data", "records", "workflows") but lacks common variations or synonyms a user might naturally say, matching the "some relevant keywords" anchor.	3 / 5
Distinctiveness Conflict Risk	Naming a specific app ("Column") gives it a clear niche with distinct triggers, though the generic "manage data" phrasing leaves minor overlap risk with general data/CRM skills.	4 / 5
	Total	13 / 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/column/SKILL.md
Commit: f484c82

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