CtrlK
BlogDocsLog inGet started
Tessl Logo

pandadoc

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

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/pandadoc/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 strong, actionable guide: concrete CLI commands throughout, a clear state-driven connection workflow with validation checkpoints, and clean section structure. The only weakness is minor over-explanation in the opening and entity list that could be trimmed for token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly concrete commands and tables, but a few lines over-explain concepts Claude already knows — e.g. 'PandaDoc is a document automation software that helps businesses create...' and 'so you can focus on the integration logic rather than auth plumbing' — which could be trimmed.

4 / 5

Actionability

It provides copy-paste-ready commands for the common cases (login, connection ensure, action list/run, proxy requests) with a clear flag table, all directly executable.

5 / 5

Workflow Clarity

The connection workflow is a well-sequenced state machine — ensure → check state → poll with --wait → handle CLIENT_ACTION_REQUIRED and re-poll after the user acts → inspect error on CONFIGURATION_ERROR — with explicit validation checkpoints and feedback loops.

5 / 5

Progressive Disclosure

The skill is well-organized into clearly labeled sections with easy navigation and no nested references; the inlined 20-item entity list is minor content that slightly pads the overview rather than belonging elsewhere.

4 / 5

Total

18

/

20

Passed

Description

45%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 clearly identifies its niche (PandaDoc) and includes a 'Use when' clause, but the capability language is generic and it lacks natural trigger-term variations. Strengthening the action verbs and adding concrete trigger phrases would markedly improve it.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete PandaDoc actions such as 'create and send proposals, generate contracts, fill templates, and track documents'.

Add natural trigger phrases and synonyms beyond the product name, e.g. 'Use when the user wants to create proposals, send contracts, or manage PandaDoc documents, templates, or e-signatures'.

Tighten the 'what' so it lists specific operations (documents, templates, pricing tables) rather than the abstract 'data, records, and workflows'.

DimensionReasoningScore

Specificity

The description names the domain (PandaDoc) but its actions are minimal and generic — 'Manage data, records, and automate workflows' uses abstract language rather than concrete operations.

2 / 5

Completeness

Both a 'what' ('Manage data, records, and automate workflows') and a 'when' ('Use when the user wants to interact with PandaDoc data') are present, but both are generic, so it does not reach the explicit, concrete level of 4.

3 / 5

Trigger Term Quality

Beyond the product name 'PandaDoc', there are no natural synonyms, variations, or file extensions; the only trigger phrase ('interact with PandaDoc data') is generic and misses common terms users would say.

2 / 5

Distinctiveness Conflict Risk

The named SaaS product 'PandaDoc' forms a clear niche with an unambiguous trigger, giving it minimal conflict risk with other skills.

5 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.