CtrlK
BlogDocsLog inGet started
Tessl Logo

performyard

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

60

Quality

71%

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/performyard/SKILL.md
SKILL.md
Quality
Evals
Security

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 body is an efficient, highly actionable integration guide with concrete commands and a clear sequenced workflow including validation checkpoints. Minor trimming of explanatory phrasing and a clearer 'Step 2' anchor would push it to the top level.

DimensionReasoningScore

Conciseness

The body is mostly lean command-driven guidance, with only minor over-explanation such as 'so you can focus on the integration logic rather than auth plumbing' that could be trimmed.

4 / 5

Actionability

It provides copy-paste-ready, fully executable membrane commands with flags and JSON examples covering installation, auth, connection, action discovery, execution, and proxying.

5 / 5

Workflow Clarity

The install→auth→connect→wait→search→run sequence is clear with state-based branching (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, though the unlabeled 'Step 2' reference is a minor gap.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections in a single file with no nested references; structure is good though some inline detail (proxy flag table, connection states) could optionally live in a reference file.

4 / 5

Total

17

/

20

Passed

Description

61%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 the PerformYard niche and includes an explicit 'Use when' trigger, but its action phrasing is generic rather than concrete to the performance-management domain. Tightening the verbs and adding domain-specific trigger terms would lift specificity and trigger quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete PerformYard actions, e.g. 'Track employee goals, run performance reviews, and capture continuous feedback.'

Add natural trigger terms users would actually say, such as 'performance reviews', 'employee goals', 'check-ins', or 'feedback cycles', alongside 'PerformYard'.

Make the 'when' clause more specific, e.g. 'Use when the user wants to manage goals, reviews, or feedback in PerformYard.'

DimensionReasoningScore

Specificity

It names the PerformYard domain but the actions ('Manage data, records, and automate workflows') are generic verb phrases rather than concrete, domain-specific operations like managing goals, reviews, or feedback.

2 / 5

Completeness

Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with PerformYard data') are present, though the 'when' could be more specific.

4 / 5

Trigger Term Quality

The product name 'PerformYard' and 'PerformYard data' are relevant natural keywords, but common variations or synonyms a user might say are missing.

3 / 5

Distinctiveness Conflict Risk

Naming the specific product 'PerformYard' gives it a clear niche with distinct triggers and minimal risk of conflicting with other skills.

5 / 5

Total

14

/

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.