CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

linear-work-rhythm

Answer "what should I do today" for a Langfuse maintainer, from the tracker rather than from memory: which projects you lead, which owe an update before the Monday engineering weekly, what shipped but is not finished, what waits on your decision, and what colleagues are working on that overlaps. Use on "what should I do today", "what's on my plate", "what should I work on next", "prep my Monday update", "what did I say last week", "who else is working on this", "who should review this", and whenever someone hands over a bare link — a ticket, a pull request, a Slack permalink — and expects you to take it from there.

Quality

84%

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

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

A well-structured, genuinely knowledgeable skill body with concrete queries for most checks, hard gates (auth failure, P0 override, propose-don't-act), and honest external delegation. Its weaknesses are length — the same rules are justified multiple times at prose length — and uneven actionability, with two of the six checks reduced to vague directions while the rest are copy-paste ready.

Suggestions

Trim the repeated rationale: state 'the handbook wins; this file only tells you what to query' and 'read handbook pages from origin/main' once each instead of three and two times respectively, and compress the essay-style justifications in checks 1 and 3 to single sentences.

Give check 4 (triage/decision) and check 6 (lifecycle compliance) the same concrete MCP query with fields that checks 1, 2, 3 and 5 have, so every check is executable.

Move the roster/name-join procedure (check 3, ~30 lines) and the link-handling routing into a reference file, leaving SKILL.md as the overview the progressive-disclosure rubric expects.

DimensionReasoningScore

Conciseness

The body is intelligent — it never explains what Linear or git is — but it spends substantial tokens on motivation and repeated warnings: handbook primacy is stated three times ('this file is only the set of queries', 'If what you are about to say contradicts one of them, the handbook wins', 'When the two disagree, the handbook wins'), the 'read it from origin/main' instruction appears twice, and passages like 'Do not report this as staleness' and 'That sentence is the whole feature. A list of forty updates is not.' argue a point at essay length where a sentence would do. This is the 'mostly efficient but could be tightened' anchor, not the 'minor instances of over-explanation' of score 4.

3 / 5

Actionability

Three of the six checks ship copy-ready MCP queries with explicit fields ('list_projects(member: "me", state: "started", fields: [...])', 'list_issues(assignee: "me", state: "Merged", ...)', 'get_status_updates(type: "project", user: "me")') plus the auth-stop gate and a worked example of the desired output format. It falls short of score 5 because check 4 ('Check the triage state on your teams') and check 6 give no query at all, and check 3's query contains unfilled placeholders ('<the Langfuse team>', '<each one>') rather than an executable form.

4 / 5

Workflow Clarity

The sequence is explicit and gated: auth check with a hard stop before anything runs, read the handbook pages, derive ownership, then the six checks in priority order with a P0 override rule, and write-back rules that require proposing rather than acting. This is 'clear sequence with most checkpoints present'. It does not reach score 5 because checks 4 and 6 have no verification step defined and there is no guidance for recovering from a failed or empty query (the truncation trap in check 3 is the only failure-mode handling).

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent), so this scores on the body's own structure: clean section headers, a table that signals exactly what to read from each external handbook page, and all external pointers (four handbook pages, three sibling skills) one level deep and clearly signaled. It stays at 4 rather than 5 because the 270-line body inlines detail that belongs in reference files — the full name/handle roster-join logic in check 3 (~30 lines) and the link-handling decision tree could be split out, per the 'content that should be separate is inline' language separating the two anchors.

4 / 5

Total

15

/

20

Passed

Description

96%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 capability list, an explicit and unusually thorough 'Use on' trigger set, and a clearly staked-out niche. The only weakness is that some trigger phrases (bare links, review routing) bleed into the territory of sibling skills that this file itself delegates to.

DimensionReasoningScore

Specificity

The description enumerates concrete capabilities rather than abstractions: 'which projects you lead, which owe an update before the Monday engineering weekly, what shipped but is not finished, what waits on your decision, and what colleagues are working on that overlaps.' This is comprehensive coverage of the skill's checks, matching the score-5 anchor's breadth (equivalent of 'Extract text and tables from PDF files, fill forms, merge documents, convert pages to images').

5 / 5

Completeness

Both halves are explicit: 'what' is the enumerated capability list and 'when' is the 'Use on ...' clause with concrete trigger phrases and the bare-link case. This mirrors the score-5 example structure ('Extract text and tables... Use when working with PDF files or when the user mentions...').

5 / 5

Trigger Term Quality

It quotes seven natural phrases a user would actually say — 'what should I do today', 'what's on my plate', 'what should I work on next', 'prep my Monday update', 'what did I say last week', 'who else is working on this', 'who should review this' — plus the bare-link handover case, giving comprehensive synonym-level coverage. Not the 4 anchor, because no common variation of the request is obviously missing.

5 / 5

Distinctiveness Conflict Risk

The niche is well defined — 'for a Langfuse maintainer, from the tracker rather than from memory' — so it would not fire for generic productivity questions. However, the bare-link and 'who should review this' triggers overlap with the sibling linear-context-handover and git-workflow skills that the body says own those flows, which is exactly the 'minor overlap risk with closely related skills' of the score-4 anchor rather than the minimal conflict of score 5.

4 / 5

Total

19

/

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: 4 suspicious

Warning

Total

15

/

16

Passed

Repository

langfuse/langfuse

Path

.agents/skills/linear-work-rhythm/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.