CtrlK
BlogDocsLog inGet started
Tessl Logo

flexitime

Flexitime integration. Manage data, records, and automate workflows. Use when the user wants to interact with Flexitime 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/flexitime/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 highly actionable with copy-paste commands and a well-sequenced connection workflow including polling feedback, though it carries some marketing padding and a couple of structural inconsistencies that keep it from top marks.

Suggestions

Remove the marketing-style overview paragraph ('streamline workforce management and improve productivity') and the 'rather than auth plumbing' aside to tighten conciseness.

Fix the '#### 1b. Wait for the connection to be ready' heading which has no corresponding step 1, and add a concrete recovery action for CONFIGURATION_ERROR/SETUP_FAILED beyond 'check the error field'.

Consider moving the proxy flags table and full clientAction state-machine detail to a reference file to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

It is mostly efficient with concrete commands, but includes unnecessary padding such as the marketing-style intro ('streamline workforce management and improve productivity') and editorial asides, matching the score-3 anchor.

3 / 5

Actionability

It provides fully executable, copy-paste-ready commands for every common case (login, connection ensure, action list/run, proxy request) plus a flags table, matching the score-5 anchor.

5 / 5

Workflow Clarity

The connect-search-run sequence is clear with explicit state-transition checkpoints and a poll-retry feedback loop, but the '#### 1b' heading has no matching '1' and error recovery for CONFIGURATION_ERROR is thin, fitting the score-4 anchor.

4 / 5

Progressive Disclosure

No bundle files exist and the single SKILL.md is well-organized with clear sections, but it inlines a full state-machine breakdown and proxy flags table that a larger skill would split out, matching the score-4 anchor.

4 / 5

Total

16

/

20

Passed

Description

57%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 correctly identifies the product and includes a 'Use when' clause, but it relies on generic verbs ('manage', 'automate') instead of concrete Flexitime capabilities and lacks the natural trigger terms (timesheets, time off) users would say.

Suggestions

Replace generic verbs with concrete Flexitime actions, e.g. 'Create and approve timesheets, submit time-off requests, and pull work-hours reports.'

Add natural user-facing trigger terms such as 'timesheets', 'time entries', 'time off', and 'payroll hours' to improve trigger matching.

Make the 'when' clause more specific: 'Use when the user wants to track work hours, manage time off, or query attendance data in Flexitime.'

DimensionReasoningScore

Specificity

It names the Flexitime domain but the actions are generic ('Manage data, records, and automate workflows') rather than concrete operations like creating timesheets or approving time off, matching the score-2 anchor.

2 / 5

Completeness

It answers both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with Flexitime data'), but the 'when' trigger is generic rather than concrete, fitting the score-4 anchor.

4 / 5

Trigger Term Quality

It includes the domain keyword ('Flexitime data', 'interact with Flexitime data') but omits the natural task vocabulary users would actually say (timesheets, time entries, time off), matching the score-3 anchor.

3 / 5

Distinctiveness Conflict Risk

The product-specific 'Flexitime integration' framing gives a distinct trigger with minimal conflict risk, though the generic 'manage data, records' phrasing leaves minor overlap, matching the score-4 anchor.

4 / 5

Total

13

/

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.