CtrlK
BlogDocsLog inGet started
Tessl Logo

alliancehcm

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

59

Quality

68%

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

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 action-oriented, packed with executable Membrane CLI commands, and structured into clear sections covering auth, connection setup, action discovery, and proxying. Its main weaknesses are a padded introductory paragraph and a sparse, vague Overview section.

Suggestions

Trim the introductory paragraph defining AllianceHCM and the redundant explanation of Membrane auth, keeping only what Claude cannot infer.

Flesh out the Overview with concrete entity/action examples (e.g., actual action ids for Pay Statement and Tax Form) instead of the bare 'Use action names and parameters as needed' line.

Add a brief validate/retry step after running actions or proxy requests so failures have an explicit feedback loop.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete CLI commands and minimal padding, though the opening paragraph explaining what AllianceHCM is and a few explanatory lines about Membrane could be trimmed.

4 / 5

Actionability

Provides numerous executable bash commands (install, login, connection ensure, action list/run, request) with flags and JSON examples; minor gaps such as the bare 'Use action names and parameters as needed' line and the unpopulated overview bullets.

4 / 5

Workflow Clarity

Sequences install → login → connection ensure → poll for readiness → search → run, with state-based polling checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED); lacks an explicit validate-and-retry loop for failed action runs.

4 / 5

Progressive Disclosure

Single well-sectioned SKILL.md with clear headers and no external bundle files; the thin Overview section and absence of referenced detail files leave minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

62%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 is third-person, names a specific platform, and includes an explicit 'Use when' clause, satisfying the basic completeness bar. It is held back by generic action verbs and limited natural trigger-term coverage.

Suggestions

Replace generic verbs ('Manage data, records') with concrete operations (e.g., 'fetch pay statements, retrieve tax forms, query employee records').

Expand the 'Use when' clause with natural user phrases like 'pay statements', 'tax forms', 'employee data', or 'AllianceHCM API'.

Add common synonyms or the platform's file/data extensions to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the AllianceHCM domain and lists a few actions ('Manage data, records, and automate workflows'), but the actions are generic and abstract rather than concrete operations.

3 / 5

Completeness

Provides both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with AllianceHCM data'), though the trigger is somewhat generic.

4 / 5

Trigger Term Quality

Includes 'AllianceHCM', 'data', 'records', and 'workflows', but lacks common synonyms, task-specific phrases, or file extensions users would naturally say.

3 / 5

Distinctiveness Conflict Risk

The named platform 'AllianceHCM' gives it a clear niche with minimal conflict risk, though the generic action verbs leave minor overlap with other data/HR skills.

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