Name: penneo
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

penneo

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

Quality

66%

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

Quality

Content

75%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 an efficient, actionable guide with a clear connection workflow and well-organized sections. Its main gaps are a broken 'Step 2' cross-reference and a few trimmable explanatory sentences.

Suggestions

Fix the dangling navigation: label the 'Step 1 / Step 2' sections explicitly or remove the 'skip to Step 2' references so the workflow is self-contained.

Trim marketecture prose (the opening paragraph and the 'so you can focus on the integration logic' aside) to improve token efficiency.

Add one fully-resolved action-run example (with a real actionId and --input payload) to close the actionability gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command blocks with brief context, fitting 'Efficient; minor instances of over-explanation that could be trimmed'; small patches like the opening Penneo marketecture sentence and 'so you can focus on the integration logic rather than auth plumbing' are trimmable, keeping it below 5.	4 / 5
Actionability	Concrete, copy-pasteable commands (install, login, connection ensure, action list/run, request) with documented flags cover the common cases, matching 'Mostly executable guidance; concrete code or commands with minor gaps'; placeholders like CONNECTION_ID and the lack of a worked action-run example keep it from 5.	4 / 5
Workflow Clarity	The connection setup is sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll loop, fitting 'Clear sequence with most checkpoints present; minor validation gaps'; the dangling 'skip to Step 2' reference with no labeled Step 2 is a structural gap that prevents a 5.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections and appropriately kept inline given there are no bundle files, fitting 'Good structure; most content is appropriately placed'; it does not reach 5 because the skill exceeds 50 lines and the proxy-flag table / action discovery could plausibly live in separate reference files.	4 / 5
	Total	16 / 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 correctly answers both what and when and leverages a distinct product name, but its capabilities and trigger terms are generic. Tightening the action list and adding concrete Penneo-specific triggers would lift the weaker dimensions.

Suggestions

Replace generic actions with concrete Penneo capabilities, e.g. 'Create case files, send documents for signing, and manage signers'.

Add natural trigger phrases users would actually say, such as 'Use when the user wants to send a document for signature or manage Penneo case files'.

Mention file formats or Penneo-specific terms (e.g. case files, signing templates) to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the Penneo domain but its actions ('Manage data, records, and automate workflows') are generic rather than concrete, matching the anchor 'Names the domain but actions are minimal or generic'; it does not reach 3 because no truly concrete capability (e.g. send for signing, create case files) is stated.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Penneo data') are present, matching the anchor for a clear what plus a present-but-could-be-more-specific when; not 5 because the trigger phrase is generic rather than concrete.	4 / 5
Trigger Term Quality	'interact with Penneo data' and 'records', 'workflows' provide some relevant keywords but miss natural synonyms and specific user phrases, fitting 'Some relevant keywords but missing common variations or synonyms'; not 4 because keyword coverage is thin and generic.	3 / 5
Distinctiveness Conflict Risk	Naming the specific Penneo product gives it a clear niche with low conflict risk, fitting 'Mostly distinct; minor overlap risk'; not 5 because the surrounding trigger language ('data', 'records', 'workflows') is generic enough to overlap with other data-integration skills.	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/penneo/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.