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

Blog Docs Log in Get started

paigo

Paigo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Paigo 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/paigo/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 content is a strong, actionable CLI integration guide with executable commands and a well-sequenced connection workflow including validation checkpoints. It loses points mainly to a redundant action-list example and some introductory context that could be trimmed.

Suggestions

Remove the duplicated `action list` example in "Popular actions" (it restates "Searching for actions") and instead link the reader back to that section.

Trim or condense the opening "Paigo is a platform that helps businesses..." paragraph, keeping only what Claude cannot infer about Paigo's domain model.

Label the "Step 2" target explicitly (e.g., a "## Running actions" step) so the "skip to Step 2" reference resolves to a concrete section.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the introductory Paigo overview paragraph and the duplicated `action list` invocation (shown in both "Searching for actions" and "Popular actions") are unnecessary padding that could be tightened.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action run with --input, request proxy) plus a flags table, with only minor gaps such as unexpanded placeholders (CONNECTION_ID, <agentType>).	4 / 5
Workflow Clarity	The install → authenticate → connect → poll-for-ready → search → run sequence is clear with a state-machine feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED) and re-polling, though "Step 2" is referenced but never explicitly labeled as a section.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested references and no bundle files present; the proxy flags table and clientAction details are sizable enough that they could live in separate files, leaving minor organization gaps.	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 well-formed: third-person, with both a what and an explicit Use-when trigger anchored to a distinct named platform. Its weakness is generic action verbs and a single trigger phrasing, which limit specificity and keyword coverage.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Paigo capabilities (e.g., query invoices, manage subscriptions and payment methods, apply coupons).

Broaden trigger terms with natural synonyms users might say (e.g., "Paigo billing", "cloud spend", "Paigo costs") rather than the single "interact with Paigo data".

Tie the when-clause to concrete scenarios (e.g., "Use when the user asks about Paigo invoices, subscriptions, or cloud spending").

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Paigo domain plus a few actions, but the actions are generic (manage, automate) rather than concrete, matching the anchor that names the domain with 1-2 non-comprehensive actions.	3 / 5
Completeness	It states both what ("Paigo integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Paigo data"), but the when clause is generic and could be more specific, matching the anchor for both present with room to sharpen.	4 / 5
Trigger Term Quality	"interact with Paigo data" plus "data, records, workflows" provides some relevant natural keywords, but it relies on a single phrasing and misses common variations or synonyms, fitting the anchor for partial keyword coverage.	3 / 5
Distinctiveness Conflict Risk	The named "Paigo" platform gives it a clear niche with a distinct trigger, though the generic "manage data, records, automate workflows" action list creates minor overlap risk with other data skills, fitting mostly-distinct with minor overlap.	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/paigo/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.