Name: people-data-labs
Rating: 61.6 (1 reviews)
Author: membranedev

people-data-labs

People Data Labs integration. Manage Persons, Companies. Use when the user wants to interact with People Data Labs data.

Quality

72%

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/people-data-labs/SKILL.md

Quality

Content

82%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.

A well-structured, highly actionable Membrane CLI integration guide with concrete commands, a useful actions table, and strong connection-state feedback loops. Its main weaknesses are a little intro padding and some unlabeled workflow step references.

Suggestions

Trim the marketing-style opening paragraph ('People Data Labs provides comprehensive B2B contact and company data. Developers and data scientists use it...') to save tokens without losing actionable content.

Label the 'Searching for actions' section as 'Step 2' to resolve the dangling 'skip to Step 2' forward reference in the connection workflow.

Add a brief validation note for action/batch results (e.g., checking the 'output' field and error states) to close the workflow-validation gap for enrichment operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, concrete CLI operational detail that Claude does not already know, with only minor padding (the marketing-style intro 'Developers and data scientists use it to enrich...' and a few restated best practices) that could be trimmed.	4 / 5
Actionability	Copy-paste-ready commands with real flags ('membrane connection ensure "https://peopledatalabs.com" --json', 'membrane action run <actionId> --connectionId=CONNECTION_ID --input {"key": "value"} --json') plus a 13-row popular-actions table and a proxy-flags table cover the common cases.	5 / 5
Workflow Clarity	The connection setup is a clear sequence with explicit validation checkpoints and feedback loops (poll until READY, branch on CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after user action); minor gaps are the referenced-but-unlabeled 'Step 2' and no output validation for batch/enrichment actions.	4 / 5
Progressive Disclosure	No bundle files exist; the single self-contained body is well-organized with clear section headers and logical navigation, though the large popular-actions and proxy-flags lookup tables are inlined rather than split into a reference file.	4 / 5
	Total	17 / 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.

A concise, service-specific description that clearly answers both what and when. Its main weakness is the generic verb ('Manage') and trigger phrasing, which under-specify the concrete actions and natural search terms users would actually say.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'Search and enrich Person and Company profiles.'

Broaden the trigger phrase beyond 'interact with People Data Labs data' to natural user terms such as 'Use when the user wants to search for people, enrich company profiles, or clean/standardize contact data.'

Include common synonyms or file/format cues (e.g., 'enrich', 'lookup', 'firmographics') to raise trigger-term coverage.

Dimension	Reasoning	Score
Specificity	'Manage Persons, Companies' names the domain and two entities but uses a single generic verb ('Manage') and is not comprehensive, matching the 'names domain and 1-2 concrete actions' anchor rather than the several-actions anchors above.	3 / 5
Completeness	It states both a clear 'what' ('People Data Labs integration. Manage Persons, Companies.') and an explicit 'Use when...' trigger clause; the 'when' is present but could be more specific, so it sits at the 'both what and when, when could be more specific' anchor rather than the concrete-trigger-phrases anchor at 5.	4 / 5
Trigger Term Quality	It names the service ('People Data Labs') and entities ('Persons, Companies') but relies on the generic phrase 'interact with People Data Labs data' and misses natural user terms like enrich, search, or lookup.	3 / 5
Distinctiveness Conflict Risk	Naming a specific third-party service gives it a clear niche with low conflict risk, but the somewhat generic 'interact with...data' trigger leaves minor overlap risk with adjacent data-enrichment skills, keeping it just below the minimal-conflict anchor at 5.	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/people-data-labs/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.