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

pidj

Pidj integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Pidj data.

Quality

63%

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/pidj/SKILL.md

Quality

Content

63%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 concrete, copy-paste Membrane CLI commands and a sensible connection workflow including a polling feedback loop. Its weaknesses are unnecessary background prose, a broken/empty overview section, and a lack of progressive disclosure into separate reference files.

Suggestions

Remove the opening "Pidj is a platform..." background paragraph and trim explanatory filler like "so you can focus on the integration logic rather than auth plumbing".

Fix or remove the empty "Pidj Overview" section (Note/Attachment/Notebook with "Use action names and parameters as needed"), which currently reads as malformed boilerplate.

Resolve the dangling "Skip to Step 2" references by either labeling the subsequent sections as explicit numbered steps or removing the cross-references.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient copy-paste CLI commands, but the opening "Pidj is a platform that helps businesses..." paragraph and phrases like "so you can focus on the integration logic rather than auth plumbing" explain context Claude does not need.	3 / 5
Actionability	Concrete executable commands cover install, auth, connection, action discovery, running, and proxying with a full flags table, but placeholders (CONNECTION_ID, actionId) and the empty "Pidj Overview" section leave minor gaps.	4 / 5
Workflow Clarity	A clear install→authenticate→connect→poll→search→run sequence exists with a poll/CLIENT_ACTION_REQUIRED feedback loop, but references to a non-labeled "Step 2" and absent output validation introduce minor gaps.	4 / 5
Progressive Disclosure	Headers organize the content reasonably, but the "Pidj Overview" section is malformed/empty (just "Note / Attachment / Notebook" and "Use action names and parameters as needed") and all material is monolithically inlined with no deeper reference structure.	3 / 5
	Total	14 / 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 with a distinct Pidj-specific trigger, but the capability description leans on a single generic verb ("Manage") and an open-ended "and more" rather than concrete actions. Trigger term coverage is relevant but limited.

Suggestions

Replace the generic verb "Manage" with concrete actions (e.g., "Create, update, search, and delete Persons, Organizations, Deals...").

Expand trigger terms with synonyms and natural phrasings users might say (e.g., "Pidj records", "Pidj CRM", "look up a deal in Pidj").

Drop the vague "and more" or replace it with an explicit, bounded list of supported entity types.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete entities ("Persons, Organizations, Deals, Leads, Projects, Activities"), but relies on a single generic action verb ("Manage ... and more") rather than multiple specific actions.	3 / 5
Completeness	Both "what" (manage Pidj entities) and "when" ("Use when the user wants to interact with Pidj data") are present and explicit, but the "what" is generic ("and more") and the "when" could be more specific.	4 / 5
Trigger Term Quality	The trigger phrase "interact with Pidj data" is natural and relevant, but coverage is thin (only "Pidj" / "Pidj data") with no synonyms or common variations.	3 / 5
Distinctiveness Conflict Risk	"Pidj" is a distinct named platform with a clear niche, but the broad entity list (Persons, Organizations, Deals, Leads) carries minor overlap risk with generic CRM/contact 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/pidj/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.