CtrlK
BlogDocsLog inGet started
Tessl Logo

jobs

Inspect visible research run state, scheduled research follow-ups when available, and durable watch artifacts. Use when the user asks what's running for a research workflow or wants research-run status.

68

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 extremely concise, well-targeted body that delegates the real workflow to the /jobs slash command while giving one concrete instruction and a useful capability-blocking note. It is appropriately lean for a simple single-action skill with no unnecessary padding.

DimensionReasoningScore

Conciseness

Three lean sentences with no padding and no explanation of concepts Claude already knows; the 'do not try to read a relative prompt-template path' guidance earns its tokens, matching the 'lean and efficient, every token earns its place' anchor.

5 / 5

Actionability

Gives a concrete executable action ('Run the `/jobs` workflow') plus a guard and a fallback behavior, but the substantive workflow lives in the /jobs command rather than here, leaving minor gaps versus copy-paste-ready completeness.

4 / 5

Workflow Clarity

This is a single-action skill where the one action ('Run the `/jobs` workflow') is unambiguous, so the simple-skill exception applies; no destructive/batch operation triggers the validation cap.

5 / 5

Progressive Disclosure

Under 50 lines and single-purpose with no external file references needed; the body appropriately delegates to the /jobs command rather than nesting files, but it lacks section structure beyond a single heading, sitting just below the well-organized 5.

4 / 5

Total

18

/

20

Passed

Description

75%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 clear, third-person description that concretely names capabilities and provides explicit 'Use when' trigger guidance for the research-run domain. It is concise and well-targeted, with only minor gaps in trigger synonym coverage.

Suggestions

Add a few natural trigger synonyms (e.g., 'job status', 'background tasks', 'queued runs') to broaden trigger-term coverage.

Consider naming the specific artifacts or run types more concretely (e.g., 'replication runs', 'watch artifacts on disk') to push specificity toward comprehensive.

DimensionReasoningScore

Specificity

Names the research-run domain and several concrete actions ("Inspect visible research run state", "scheduled research follow-ups", "durable watch artifacts"), with only minor coverage gaps, matching the 'lists several specific actions' anchor.

4 / 5

Completeness

Explicitly states both what it does and when to use it ("Use when the user asks what's running... or wants research-run status"), with the 'when' concrete but not maximally comprehensive, matching the 4 anchor above the 3 ('when missing/weakly implied').

4 / 5

Trigger Term Quality

Includes natural phrases users would say ("what's running for a research workflow", "research-run status") but is missing some common variations like 'job status' or 'background tasks', fitting the 'good coverage, a few terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The research-run/watch-artifact niche is mostly distinct with only minor overlap risk against generic task-management skills, fitting the 4 anchor rather than 3 (still-overlapping) or 5 (minimal conflict).

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
companion-inc/feynman
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.