Name: pointerpro
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

pointerpro

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

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/pointerpro/SKILL.md

Quality

Content

61%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 highly actionable with concrete CLI commands and a well-structured connection workflow, but it carries some background padding and lacks validation guidance for destructive proxy/action operations, capping workflow clarity.

Suggestions

Trim the introductory platform background and remove the filler line "Use action names and parameters as needed." to tighten conciseness.

Add a validation/verification checkpoint before destructive operations — e.g. for proxy DELETE/PUT/PATCH or destructive action runs, instruct to confirm the target id and dry-run/preview before executing.

Flesh out "Popular actions" with one or two real Pointerpro action examples (e.g. listing surveys or fetching a respondent report with actual input) instead of restating the discovery command.

Dimension	Reasoning	Score
Conciseness	The intro paragraph explains the platform's purpose and audience ("used by HR departments, marketing teams, and consultants") and the line "Use action names and parameters as needed." is filler; the rest is mostly efficient CLI commands.	3 / 5
Actionability	Concrete copy-paste CLI commands cover install, login, connection ensure, action list/run, and proxy requests plus a flags table, but examples use generic placeholders ("{\"key\": \"value\"}") with no real Pointerpro action example.	4 / 5
Workflow Clarity	The connection setup has a clear sequence with state-based polling feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but proxy requests explicitly enable DELETE/PUT/PATCH and action runs can be destructive with no verify-before-execute validation, capping the score.	3 / 5
Progressive Disclosure	A single well-organized file with clear hierarchical sections is appropriate for a CLI integration with no bundle files, though the "Popular actions" section is thin/redundant and a filler line introduces minor organization gaps.	4 / 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 answers both what and when and is anchored to a named app, but its trigger guidance is generic and the entity list appears mismatched with Pointerpro's survey/assessment domain, weakening trigger-term quality and distinctiveness.

Suggestions

Replace the generic "Use when the user wants to interact with Pointerpro data" with concrete survey-domain triggers, e.g. "Use when the user wants to create or analyze surveys, quizzes, assessments, or respondent reports in Pointerpro."

Verify the entity list: Persons/Organizations/Deals/Leads/Projects/Activities read as CRM entities and conflict with the body's survey-domain model (Survey/Question/Respondent/Report) — align the description with the actual Pointerpro objects.

Swap the single generic verb "Manage" for specific actions (e.g. "Create and distribute surveys, collect responses, generate reports") to improve specificity.

Dimension	Reasoning	Score
Specificity	"Manage Persons, Organizations, Deals, Leads, Projects, Activities and more" names the domain and concrete entity targets, but relies on a single generic verb ("Manage") rather than several distinct actions, so it is not comprehensive.	3 / 5
Completeness	Both "what" (Pointerpro integration, manage these entities) and "when" ("Use when the user wants to interact with Pointerpro data") are explicitly present, but the "when" clause is generic rather than concrete.	4 / 5
Trigger Term Quality	The trigger phrase "Use when the user wants to interact with Pointerpro data" is generic, and the listed entities read as CRM terms while the natural survey-domain terms (surveys, questionnaires, assessments, respondents) users would actually say are missing.	3 / 5
Distinctiveness Conflict Risk	The explicit app name "Pointerpro" anchors a clear niche, but the generic CRM-like entity list (Persons, Organizations, Deals, Leads) creates minor overlap risk with other CRM/survey integration 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/pointerpro/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.