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

knowfirst

KnowFirst integration. Manage Organizations, Activities, Notes, Files, Pipelines, Users and more. Use when the user wants to interact with KnowFirst 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/knowfirst/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 CLI commands, a clear connection workflow, and a useful polling/feedback loop for connection states. Its main weaknesses are a padded marketing intro and a broken step-numbering reference ('Step 2') that slightly undermines workflow clarity.

Suggestions

Trim or remove the opening marketing paragraph about KnowFirst's audience and value proposition; Claude only needs the API interaction details.

Fix the dangling 'skip to Step 2' reference by labeling the subsequent sections as explicit numbered steps (e.g., 'Step 2: Search for actions').

Consider moving the popular-actions table and proxy flag reference into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The opening marketing paragraph ('KnowFirst is a SaaS platform that provides real-time alerts and insights...') and explanatory asides like 'This is the fastest way to get a connection' add padding Claude does not need, placing it at 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands (`npm install -g @membranehq/cli@latest`, `membrane connection ensure ... --json`, `membrane action run <actionId> ...`) plus a populated actions table, with only minor gaps from placeholders like `<agentType>` and `CONNECTION_ID` requiring substitution.	4 / 5
Workflow Clarity	There is a clear install → authenticate → connect → poll-until-ready → search → run sequence with an explicit feedback loop (poll connection state, handle CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll), but the dangling 'skip to Step 2' reference and the unlabeled step numbering are minor validation/sequencing gaps.	4 / 5
Progressive Disclosure	The body is a single well-organized file with clear section headers and a clearly signaled external reference ('Official docs: https://knowfirst.com/platform/api/'); no bundle files exist, and content is appropriately placed with no nested references, though the popular-actions table and proxy flag list could optionally live in separate files.	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 clearly identifies the KnowFirst domain and includes an explicit 'Use when' trigger, but the action verb is generic ('Manage') and the trigger phrase is somewhat abstract rather than concrete. It is solid but leaves room for sharper, more natural trigger language.

Suggestions

Replace the single generic verb 'Manage' with several distinct concrete actions (e.g., 'Create, update, and query Organizations, Activities, Notes...') to lift specificity.

Make the 'Use when' trigger more concrete with natural user phrases, e.g. 'Use when the user wants to track businesses, pull business feeds, or query KnowFirst data.'

Add common synonyms/file-style cues users might say (e.g. 'KnowFirst alerts', 'business tracking', 'market feed') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage Organizations, Activities, Notes, Files, Pipelines, Users and more' names six concrete entities but relies on a single generic verb ('Manage') rather than enumerating distinct actions, so it sits at the 'names domain and concrete items but not comprehensive actions' anchor.	3 / 5
Completeness	It states both the 'what' ('Manage Organizations, Activities, Notes, Files, Pipelines, Users...') and an explicit 'when' ('Use when the user wants to interact with KnowFirst data'), but the 'when' trigger is generic rather than concrete, fitting the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with KnowFirst data' plus the entity list provides the core 'KnowFirst' keyword and several domain terms, but lacks common synonyms or variations a user might naturally say, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific SaaS 'KnowFirst' gives it a clear niche with low conflict risk, though generic entity terms like 'Notes', 'Files', and 'Users' create minor overlap with other skills, matching the 'mostly distinct; minor overlap risk' anchor.	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/knowfirst/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.