Name: sidetracker
Rating: 52.8 (1 reviews)
Author: membranedev

sidetracker

Sidetracker integration. Manage Organizations, Projects, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Sidetracker data.

Quality

58%

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

Quality

Content

58%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 delivers concrete, executable CLI commands and a recognizable connection-to-action workflow with helpful state-handling detail. It loses points for some generic boilerplate, a duplicated actions/search section, and workflow checkpoints that are implied rather than explicit validation steps.

Suggestions

Trim the generic product description and de-duplicate the 'Popular actions' / 'Searching for actions' sections that restate the same action-list command.

Add an explicit validation checkpoint before running actions (e.g., verify `state: READY` is confirmed before proceeding, and a verify-output step after `action run`).

Make placeholders concrete or add a one-line note that CONNECTION_ID comes from the prior `connection ensure --json` output and QUERY is a natural-language intent string.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but sections like the generic product description ('time tracking and productivity management application... helps users identify distractions') and the repetition of the same action-list/search command add explanation Claude does not need.	3 / 5
Actionability	Commands are concrete and largely copy-paste ready (login, connection ensure, action run with --input, request proxy) with a flag table; minor gaps are abstract placeholders like CONNECTION_ID and QUERY that the user must substitute.	4 / 5
Workflow Clarity	A sequence exists (install, login, connection ensure, poll for READY, search actions, run actions) with state checks for BUILDING/CLIENT_ACTION_REQUIRED, but the connect-to-act flow lacks explicit validation checkpoints and recovery is only partially spelled out relative to a full feedback loop.	3 / 5
Progressive Disclosure	Content is well-sectioned into overview, connection, searching, running, proxy, and best practices with no bundle files needed; minor organization gaps (a duplicated Popular actions/search section and the entity overview sitting awkwardly above the workflow) keep it from a 5.	4 / 5
	Total	14 / 20 Passed

Description

58%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 identifies the Sidetracker domain and includes an explicit 'Use when' trigger, satisfying both what and when. It is held back by the single generic verb 'Manage' covering many entities and by limited natural trigger-term variation.

Suggestions

Replace the single verb 'Manage' with specific concrete actions per entity (e.g., 'Create and update Projects, start and stop Timers, assign Goals').

Expand the 'Use when' clause with natural trigger phrases users would say (e.g., 'Use when the user wants to track time, start a timer, or manage Sidetracker tasks and projects').

Add synonyms and concrete terms users actually mention (e.g., 'time tracking', 'timers', 'tasks') alongside 'Sidetracker data'.

Dimension	Reasoning	Score
Specificity	It names the domain (Sidetracker) and lists several concrete entities ('Organizations, Projects, Pipelines, Users, Goals, Filters') but the only action verb is 'Manage', so the actions remain generic rather than a comprehensive set of specific operations.	3 / 5
Completeness	It answers 'what' ('Manage Organizations, Projects...') and 'when' ('Use when the user wants to interact with Sidetracker data'); the 'when' clause is explicit but generic rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	'Sidetracker data' and the entity names are relevant keywords, but natural trigger phrasing is thin and synonyms/file extensions a user would actually say are missing, leaving some common variations uncovered.	3 / 5
Distinctiveness Conflict Risk	The Sidetracker-specific name and entity list carve a clear niche with minimal overlap risk against other skills, though the generic 'Manage' framing is slightly less distinctive than trigger-based examples.	4 / 5
	Total	14 / 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/sidetracker/SKILL.md
Commit: f484c82

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