Name: attendance-giriton
Rating: 47.2 (1 reviews)
Author: membranedev

attendance-giriton

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

Quality

50%

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

Quality

Content

55%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 skill delivers mostly executable, well-sequenced Membrane CLI guidance with a clear connection-action workflow, but it is marred by an irrelevant canned-refusal opener and a meaningless cyclic overview list that waste tokens.

Suggestions

Remove the canned refusal line ('I don't have enough information to do that...') and the cyclic 'Attendance GIRITON Overview' bullet list; they add no value and waste context.

Provide one or two concrete example actionIds and a sample `action run --input` payload so the guidance is copy-paste ready end-to-end.

Tighten the request-proxy section by moving the full flag table into a short inline summary, since no references/ folder exists to offload it.

Dimension	Reasoning	Score
Conciseness	The body opens with an irrelevant canned refusal ('I don't have enough information to do that...'), includes a meaningless cyclic 'Attendance GIRITON Overview' bullet list that explains nothing, and otherwise is mostly efficient CLI guidance, so it is noticeably verbose with several unnecessary padded sections.	2 / 5
Actionability	It provides concrete, executable membrane CLI commands (install, login, connection ensure, action list/run, request) with flags and JSON usage; only minor gaps (e.g. no concrete actionId examples) keep it from a 5.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced (ensure -> wait/poll for state -> search actions -> run), with explicit state handling and a validation loop (poll until READY, handle CLIENT_ACTION_REQUIRED then re-poll); minor gaps (no retry/failure recovery checklist) cap it at 4.	4 / 5
Progressive Disclosure	There are clear section headers and no bundle files to reference, but the cyclic overview bullets and inlined flag tables are content that adds little, and navigation could be tighter; it has structure but some inline content should be trimmed.	3 / 5
	Total	13 / 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 identifies the specific GIRITON integration niche and includes both a 'what' and a 'when', but the actions are generic and the trigger phrasing lacks natural variations users would actually say.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete capabilities such as 'pull attendance records, sync employee time entries, and automate attendance workflows'.

Expand the 'Use when' clause with natural trigger phrases users would say, e.g. 'when the user mentions Attendance GIRITON, attendance records, employee time tracking, or Giriton time-and-attendance data'.

Add common synonyms or identifier hints (e.g. 'giriton.com attendance data') to improve natural trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Attendance GIRITON integration') and a few generic actions ('Manage data, records, and automate workflows'), but these actions are minimal and not tied to concrete capabilities, matching the anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	It states a clear 'what' (manage data, records, automate workflows) and a 'when' ('Use when the user wants to interact with Attendance GIRITON data'), so both are present, but the 'when' is generic and not tied to concrete trigger phrases.	3 / 5
Trigger Term Quality	'Attendance GIRITON data' and 'interact with Attendance GIRITON' are relevant keywords, but it misses common variations, synonyms, or file extensions; it sits at 'Some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	'Attendance GIRITON' is a specific niche, but 'Manage data, records, and automate workflows' is broad and could overlap with other data-management skills, matching 'Somewhat specific but could still overlap'.	3 / 5
	Total	11 / 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/attendance-giriton/SKILL.md
Commit: f484c82

Reviewed: 3 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.