Name: pactsafe
Rating: 60 (1 reviews)
Author: membranedev

pactsafe

PactSafe integration. Manage data, records, and automate workflows. Use when the user wants to interact with PactSafe data.

Quality

70%

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/pactsafe/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.

The content is highly actionable with copy-paste-ready CLI commands and a well-sequenced connection flow including state-based polling, though it has minor verbosity in the intro and lacks explicit verification steps after action/proxy execution.

Suggestions

Trim marketing-style padding such as 'This helps ensure compliance and reduces legal risk' and 'so you can focus on the integration logic rather than auth plumbing'.

Add a verification step after running actions or proxy requests (e.g. inspect the `output` field / response status) to close the validation gap for potentially destructive proxy calls (DELETE/PUT).

Reconcile the loose step numbering (a referenced 'Step 2' and a '1b' with no 'Step 1' label) into one explicit numbered sequence so the end-to-end workflow is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly command- and code-block-driven with only minor over-explanation (e.g. 'This helps ensure compliance and reduces legal risk' and 'so you can focus on the integration logic rather than auth plumbing'), matching 'efficient; minor instances of over-explanation that could be trimmed.'	4 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus a complete proxy-flags table covering the common cases, matching 'fully executable; copy-paste ready code or commands.'	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with a state-based polling feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but there are no verification steps after running actions or proxy (DELETE) calls, matching 'clear sequence with most checkpoints present; minor validation gaps.'	4 / 5
Progressive Disclosure	The body is well-sectioned (Overview, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no content that clearly belongs in a separate file, but at ~148 lines with no external references it stops short of a clean overview-plus-references split, matching 'good structure; most content appropriately placed; minor organization gaps.'	4 / 5
	Total	17 / 20 Passed

Description

57%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 has an explicit 'Use when' trigger and is distinct thanks to the PactSafe brand name, but its capability verbs ('manage data, records, automate workflows') are generic and it lacks the natural domain terms (contracts, terms, clickwrap) users would actually say.

Suggestions

Replace generic verbs with concrete PactSafe actions, e.g. 'Manage contracts, groups, clickwrap agreements, and acceptance records.'

Add natural domain trigger terms such as 'contracts', 'legal agreements', 'terms and conditions', or 'clickwrap' so the description matches user phrasing.

Tighten the 'when' clause to name the triggering scenarios, e.g. 'Use when the user wants to manage contracts, clickwrap groups, or acceptance records in PactSafe.'

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the PactSafe domain but the actions are generic abstractions rather than concrete capabilities, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states a 'what' ('PactSafe integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with PactSafe data.'), but the 'when' could be more specific, matching the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	It captures the brand keyword 'PactSafe' and 'PactSafe data' as a trigger, but omits the natural domain terms a user would say (contracts, legal agreements, terms, clickwrap), fitting 'some relevant keywords but missing common variations or synonyms.'	3 / 5
Distinctiveness Conflict Risk	The named product 'PactSafe' gives it a clear, distinct trigger unlikely to fire for unrelated skills, with only minor overlap risk from the generic 'manage data/records' phrasing, matching 'mostly distinct; minor overlap risk.'	4 / 5
	Total	13 / 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/pactsafe/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.