CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

work-track-item

Track a Linear ticket or GitHub PR in today's daily note with fields and timestamped activity. Use when invoked as `$work-track-item` or when the user asks to track a work item.

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

90%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.

An efficient, highly actionable skill body: exact commands, a concrete output template, and clear sequenced steps with useful pre-checks and an error-recovery loop. The only weaknesses are the absence of a post-write verification step and minor organization of the formatting/insertion rules inside the workflow.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: no concept explanations, just an arguments spec, a 7-step workflow, exact commands, and formatting rules. The sandbox/keychain paragraph is non-obvious operational detail (error strings to detect, scoped escalation) that earns its place, fitting the "every token earns its place" anchor.

5 / 5

Actionability

Fully executable guidance: copy-paste bash for locating the note and grepping for existing sections, an exact `gh pr view --json number,title,state,url,repository,headRefName` command, and a complete markdown block template. Both the Linear-ticket and GitHub-PR cases are covered, matching the anchor-5 example.

5 / 5

Workflow Clarity

Seven clearly sequenced steps with pre-checks (note existence with a `$work-start` fallback, existing-section search to avoid duplicates) and an explicit error-recovery loop for sandboxed keychain failures. Not 5 because there is no post-write verification that the block was inserted correctly; the operation is neither destructive nor batch, so the validation cap does not apply.

4 / 5

Progressive Disclosure

Well-organized sections (Arguments, Workflow, formatting rules) with all content appropriately inline and no external references needed. The under-50-lines exception for scoring 5 does not strictly apply (~77-line body), and the insertion-location rule buried as a bullet in step 6 is a minor organization gap, placing this between anchors 4 and 5.

4 / 5

Total

18

/

20

Passed

Description

87%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.

A strong description: concrete, third-person, with an explicit dual-trigger "Use when" clause covering both the slash invocation and a natural user request. Keyword coverage is good though a few natural synonyms ("log", "note", "update") are absent.

DimensionReasoningScore

Specificity

"Track a Linear ticket or GitHub PR in today's daily note with fields and timestamped activity" names concrete objects (Linear ticket, GitHub PR, daily note) and several specific actions (tracking with fields, timestamped activity). It falls short of 5 because it omits actions like adding or updating sections and updating status, and exceeds 3 because more than 1-2 concrete actions are specified along with the destination.

4 / 5

Completeness

Explicitly answers both: what ("Track a Linear ticket or GitHub PR in today's daily note with fields and timestamped activity") and when ("Use when invoked as `$work-track-item` or when the user asks to track a work item") with concrete trigger phrases, matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

Includes natural terms users would say — "Linear ticket", "GitHub PR", "track a work item" — plus the explicit `$work-track-item` invocation. Not 5 because common variations like "log", "add to my notes", or "update ticket status" are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche — tracking Linear tickets and GitHub PRs in daily notes — with a distinct named invocation trigger. Minimal overlap with other skills; the only mild breadth is "track a work item", which is anchored by the specific what-clause.

5 / 5

Total

18

/

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

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

phatblat/dotfiles

Path

.agents/skills/work-track-item/SKILL.md

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.