CtrlK
BlogDocsLog inGet started
Tessl Logo

altera-payroll

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

66

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

95%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, executable guide with concrete CLI commands, a clear connection-to-action workflow, and good structure. Its main gaps are minor verbosity and the absence of explicit validation checkpoints in the connection/action workflow.

DimensionReasoningScore

Conciseness

The body is mostly efficient, built around executable commands and short explanations with only minor over-explanation (the opening 'Altera Payroll is a payroll processing...' sentence and the proxy paragraph), matching the 'efficient; minor instances of over-explanation' anchor.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands (membrane connection ensure, action run, action list, request proxy) with real flags and parameters and an options table, covering the common cases comprehensively.

5 / 5

Workflow Clarity

The connection workflow is clearly sequenced with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-after-action feedback loop, but lacks explicit validation checkpoints for external/batch operations, fitting the 'clear sequence with most checkpoints present; minor validation gaps' anchor.

4 / 5

Progressive Disclosure

Single, well-organized file with clear section headers, command blocks, and a flag table; content is appropriately inline with no nested references, though the proxy/action detail could optionally be split out.

4 / 5

Total

17

/

20

Passed

Description

66%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 niche (Altera Payroll) and includes an explicit 'Use when' trigger, but its capability phrasing is generic ('manage data, records, automate workflows') and trigger-term coverage is narrow. Strengthening the action verbs and adding common payroll-specific triggers would raise specificity and completeness.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete payroll capabilities like 'run payroll, review paychecks, manage employee records, and pull tax/compliance reports'.

Broaden the trigger clause to include natural phrasings such as 'Use when the user wants to run or review payroll, check paychecks, manage employee or tax records, or automate Altera Payroll workflows'.

Mention common trigger terms and entities (paychecks, payroll runs, tax compliance) so the description matches what users actually ask for.

DimensionReasoningScore

Specificity

Names the Altera Payroll domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, fitting the 'names domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

Provides a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when the user wants to interact with Altera Payroll data' trigger, though the 'when' could be more specific.

4 / 5

Trigger Term Quality

Includes some natural terms ('Altera Payroll', 'interact with Altera Payroll data') but lacks common synonyms and variations users would naturally say, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

Targets a specific named application (Altera Payroll) with distinct triggers, giving it a clear niche with minimal conflict risk against other skills.

5 / 5

Total

15

/

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.