CtrlK
BlogDocsLog inGet started
Tessl Logo

harvest

Harvest integration. Manage Projects, Tasks, Persons, Expenses, Clients. Use when the user wants to interact with Harvest data.

62

Quality

74%

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

Quality

Content

82%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 covering the full connection-to-execution flow and a well-structured connection state machine with validation checkpoints. Minor trimming of explanatory prose and fixing the broken 'Step 2' cross-reference would push it higher.

DimensionReasoningScore

Conciseness

The body is largely lean concrete commands and tables, but includes minor over-explanation that could be trimmed, such as the marketing-style opener ('It's used by businesses, especially small to medium-sized ones...') and asides like 'This is the fastest way to get a connection.'

4 / 5

Actionability

It provides copy-paste-ready, fully executable commands for every common case — install, login, connection ensure/get, action list, action run, and proxy requests — plus a table of popular action keys and a proxy options table.

5 / 5

Workflow Clarity

The connection flow is a clear sequenced state machine with explicit validation checkpoints and a feedback loop (poll BUILDING, handle CLIENT_ACTION_REQUIRED, re-poll until READY), but the 'skip to Step 2' cross-reference points to no labeled 'Step 2' header, leaving the numbering slightly incoherent.

4 / 5

Progressive Disclosure

Content is well-organized into clear headed sections with no nested references, but everything lives in a single ~180-line file with the 20-row Popular actions table inlined rather than split into a separate reference file.

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 is clearly scoped to Harvest and answers both what and when, but its action vocabulary is generic and its triggers miss Harvest's core time-tracking and invoicing concepts. It is distinct and low-conflict but could be sharper and more complete.

Suggestions

Replace the single generic verb 'Manage' with distinct concrete actions (e.g., 'Create, list, update, and delete Projects, Tasks, Users, Expenses, and Clients') to raise specificity.

Add Harvest's flagship concepts to the description and trigger so that requests to 'track time', 'log timesheets', or 'send invoices' surface the skill.

Make the 'Use when...' clause enumerate concrete triggers (e.g., 'Use when the user wants to track time, manage projects or tasks, record expenses, or send invoices in Harvest') instead of the generic 'interact with Harvest data'.

DimensionReasoningScore

Specificity

The description names the Harvest domain and several entities ('Manage Projects, Tasks, Persons, Expenses, Clients'), but relies on a single generic verb 'Manage' rather than distinct concrete actions, so coverage is not comprehensive.

3 / 5

Completeness

Both 'what' ('Manage Projects, Tasks, Persons, Expenses, Clients') and 'when' ('Use when the user wants to interact with Harvest data') are present and explicit, though the 'when' clause is generic rather than enumerating concrete trigger phrases.

4 / 5

Trigger Term Quality

It includes the app name and a list of entity keywords plus an explicit trigger ('Use when the user wants to interact with Harvest data'), but omits Harvest's flagship concepts — time tracking, timesheets, and invoices — which are the terms users most naturally say.

3 / 5

Distinctiveness Conflict Risk

Tied to a specific named product ('Harvest integration') with concrete entity triggers, giving it a clear niche with minimal risk of triggering for an unrelated skill.

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.