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

Blog Docs Log in Get started

folk

Folk integration. Manage data, records, and automate workflows. Use when the user wants to interact with Folk 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/folk/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 well-structured, actionable guide to driving Folk through the Membrane CLI, with a clear connection workflow and feedback loop. It is slightly held back by an unnecessary marketing intro and inconsistent step numbering.

Suggestions

Trim the introductory marketing paragraph about who uses Folk; keep only what is needed to orient the integration.

Fix the step numbering: label 'Step 1a/1b' consistently or remove the dangling 'skip to Step 2' reference and renumber sections.

Consider extracting the proxy flag table and detailed clientAction state reference into a separate reference file to keep SKILL.md lean.

Dimension	Reasoning	Score
Conciseness	Mostly efficient operational commands, but the opening paragraph ('Folk is a collaborative CRM platform... used by sales, marketing, and recruiting teams to streamline communication and build stronger relationships') is marketing-style padding Claude does not need.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, proxy flag table) covering the common cases, with only minor placeholder gaps.	4 / 5
Workflow Clarity	Clear install→login→connect→poll→search→run sequence with state-based branching and an explicit polling feedback loop; step numbering is inconsistent ('Step 2' referenced but unlabeled, '1b' with no '1a').	4 / 5
Progressive Disclosure	Single well-sectioned file with clear headers and no nested references; content is appropriately placed inline given no bundle files exist.	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 covers both what the skill does and when to use it, and naming Folk keeps it reasonably distinct. Its main weakness is generic action verbs and missing natural CRM trigger terms like 'contacts' or 'people'.

Suggestions

Replace generic verbs with concrete Folk actions, e.g. 'Create, search, and update contacts and groups in Folk'.

Add natural trigger terms users would say, such as 'contacts', 'people', 'CRM', or 'Folk lists'.

Tighten the 'when' clause to reference concrete Folk objects, e.g. 'Use when the user wants to manage Folk contacts, groups, or records.'

Dimension	Reasoning	Score
Specificity	Names the Folk/CRM domain with several listed actions ('Manage data, records, and automate workflows'), but the verbs are generic ('manage') rather than concrete CRM operations like create/search/update contacts.	3 / 5
Completeness	Provides both a 'what' (manage data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with Folk data'), though the trigger clause is somewhat generic.	4 / 5
Trigger Term Quality	Includes some relevant keywords ('Folk data', 'records', 'workflows') but omits the natural CRM terms a user would actually say, such as 'contacts', 'people', or 'CRM'.	3 / 5
Distinctiveness Conflict Risk	Naming Folk specifically gives it a clear niche with minimal conflict risk, though the generic 'manage data, records, automate workflows' phrasing could overlap with broader data skills.	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/folk/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.