CtrlK
BlogDocsLog inGet started
Tessl Logo

odoo-project-timesheet

Expert guide for Odoo Project and Timesheets: task stages, billable time tracking, timesheet approval, budget alerts, and invoicing from timesheets.

61

Quality

72%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/odoo-project-timesheet/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 concrete menu-driven workflows and clear sequencing, though it carries some redundant overview prose that could be tightened for token efficiency.

Suggestions

Trim the Overview (it restates the frontmatter description) and the generic 'How It Works' Activate/Configure/Automate block to improve conciseness.

Add an explicit post-invoice validation step (e.g., confirm line totals and approved-hour quantity match) to strengthen the workflow feedback loop for this batch financial operation.

Consider moving the four detailed Examples into a references file linked from the body to improve progressive disclosure now that the skill exceeds ~50 lines.

DimensionReasoningScore

Conciseness

Mostly efficient concrete menu guidance, but the Overview restates the description and the 'How It Works' Activate/Configure/Automate block is generic skill-mechanic prose that could be trimmed.

3 / 5

Actionability

Fully concrete, copy-ready guidance with exact menu paths, field values, and worked examples (e.g., $150/hr, 80% budget alert) covering the common cases.

5 / 5

Workflow Clarity

Clear numbered sequences for approval and invoicing, with a verify-approved-hours checkpoint before invoicing; minor validation gaps remain (no explicit re-check after invoice creation).

4 / 5

Progressive Disclosure

Self-contained single file with well-organized sections and no nested references; good structure though the detailed Examples block could be considered for a separate file.

4 / 5

Total

16

/

20

Passed

Description

70%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 communicates a distinct Odoo niche and concrete capabilities, but lacks an explicit 'Use when...' trigger clause, which limits its completeness score.

Suggestions

Add an explicit trigger clause such as 'Use when setting up Odoo Project & Timesheets, configuring billable time tracking, or invoicing from approved timesheets.'

Lead with action verbs ('Configure projects, track billable time, approve timesheets, invoice customers') instead of noun-phrases to raise specificity.

Include a common synonym or file/feature term a user might naturally say (e.g., 'Time & Materials billing' or 'project budget') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ('task stages, billable time tracking, timesheet approval, budget alerts, and invoicing from timesheets'), but they are noun-phrases rather than action verbs, leaving minor coverage gaps versus the comprehensive anchor.

4 / 5

Completeness

A clear 'what' is present, but there is no 'Use when...' or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Good natural-keyword coverage ('timesheet', 'billable', 'budget alert', 'invoice', 'Odoo Project'), but a few common synonyms a user might say are absent.

4 / 5

Distinctiveness Conflict Risk

The 'Odoo Project and Timesheets' niche with its specific capability list is clearly distinguishable and unlikely to trigger the wrong skill.

5 / 5

Total

16

/

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.

Validation — 15 / 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
administrakt0r/AI-Agents-Safe-Coding-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.