Name: proprofs-project
Rating: 56.8 (1 reviews)
Author: membranedev

proprofs-project

ProProfs Project integration. Manage Projects, Goals, Filters. Use when the user wants to interact with ProProfs Project 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/proprofs-project/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 integration guide built around concrete Membrane CLI commands and a genuinely good connection-state workflow with feedback loops. Its main weaknesses are a padded marketing-style introduction and slightly loose cross-section sequencing rather than content placement.

Suggestions

Remove or condense the introductory product-description paragraph ('ProProfs Project is a cloud-based project management software...') since Claude does not need that background.

Label 'Step 2' explicitly and add a final verify/check step after running actions so the end-to-end workflow reads as a single numbered sequence with explicit checkpoints.

Provide at least one fully concrete end-to-end example (real connection id flow) instead of leaving CONNECTION_ID as an unexpanded placeholder.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph ('ProProfs Project is a cloud-based project management software. It helps project managers and teams plan, track, and execute projects efficiently...') explains a product concept Claude does not need, and phrasing like 'so you can focus on the integration logic rather than auth plumbing' is padding, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (membrane login, connection ensure, action run, request) with a flag table explaining options, matching the 'mostly executable guidance with minor gaps' anchor; it stops short of 5 because some examples leave placeholders like CONNECTION_ID without a complete end-to-end runnable example.	4 / 5
Workflow Clarity	The install→authenticate→connect→search→run sequence is clear, and the connection section has explicit state-based validation with a feedback loop (poll until READY; on CLIENT_ACTION_REQUIRED act then re-poll), matching the 4 anchor. It does not reach 5 because the cross-section numbering is loose ('skip to Step 2' with no labeled Step 2) and there is no explicit verify step after running actions.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is organized into well-labeled sections (Overview, Working with, Install, Auth, Connecting, Searching, Popular actions, Proxy, Best practices) giving good navigation, matching the 4 anchor; it is not 5 because the content is somewhat long for a single file and the entity overview adds little structural value.	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 is solid: it states a clear domain, lists concrete managed objects, and includes an explicit 'Use when' trigger tied to a distinctive app name. Its main weakness is generic verb choice and limited keyword variation, which keeps specificity and trigger quality at mid-range scores.

Suggestions

Replace the generic verb 'Manage' with specific concrete actions (e.g. 'create, update, and track Projects, Tasks, and Time Entries') to lift specificity toward 5.

Expand trigger terms with natural synonyms users might say (e.g. 'ProProfs Project, project tasks, timesheets, invoices') to improve trigger-term coverage.

Tighten the 'when' clause to enumerate concrete triggering scenarios (e.g. 'Use when the user wants to create tasks, log time, or pull project reports from ProProfs Project').

Dimension	Reasoning	Score
Specificity	The description names the domain and a few concrete objects ('Manage Projects, Goals, Filters'), but the verb 'Manage' is generic and the coverage is not comprehensive, fitting the '1-2 concrete actions but not comprehensive' anchor rather than the multiple-specific-actions anchor at 4.	3 / 5
Completeness	It answers both 'what' ('Manage Projects, Goals, Filters') and 'when' via an explicit 'Use when the user wants to interact with ProProfs Project data' clause; the 'when' is present and explicit but could be more specific, matching the 4 anchor and justifying not capping at 3 since a Use-when clause exists.	4 / 5
Trigger Term Quality	'ProProfs Project data' provides a relevant keyword, but there are no synonyms, common variations, or file extensions, matching the 'some relevant keywords but missing common variations' anchor and falling below the good-coverage anchor at 4.	3 / 5
Distinctiveness Conflict Risk	'ProProfs Project' is a specific named application niche with a distinct trigger phrase, giving minimal conflict risk; it is not quite the maximally-distinct 5 anchor because the generic 'Manage' phrasing leaves slight overlap room with other project-management integrations.	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/proprofs-project/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.