CtrlK
BlogDocsLog inGet started
Tessl Logo

add-new-jit-ee-api

Add a new API to the JIT-VM (aka JIT-EE) interface in the codebase.

56

Quality

63%

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 ./.github/skills/add-new-jit-ee-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 a well-sequenced, highly actionable procedural guide with concrete diffs and a Definition-of-Done checklist, but it lacks an explicit build/test validation feedback loop for a batch multi-file change, which caps workflow clarity. Tightening the agnostic.h guidance and adding a verification step would raise the score.

Suggestions

Add an explicit validation step after the edits (e.g. build coreclr and run SuperPMI replay smoke test) with a fix-and-retry loop to satisfy the batch-operation feedback-loop requirement.

Provide a concrete agnostic.h type-definition example instead of relying on 'inspect the whole file', closing the actionability gap.

Consider moving the large methodcontext.cpp diff into a referenced template file so SKILL.md stays a tighter overview.

DimensionReasoningScore

Conciseness

The body is mostly lean, leading with concrete diffs and exact paths; the only mild over-explanation is the SuperPMI purpose paragraph and a few 'inspect similar methods' notes, fitting the efficient-with-minor-trim anchor rather than the padded ones below.

4 / 5

Actionability

Most steps give copy-paste-ready diffs with concrete file paths (ThunkInput.txt, corinfo.h, methodcontext.cpp), but the agnostic.h step leaves type definitions to 'inspect the file', leaving a minor gap that keeps it just below fully executable.

4 / 5

Workflow Clarity

The 8 steps are clearly sequenced with a Definition-of-Done checklist, but this is a batch operation across ~10 files with no build/compile/test validation feedback loop, so per the batch-operations cap workflow_clarity cannot exceed 3.

3 / 5

Progressive Disclosure

The skill is a single self-contained file with well-organized sections (Goal, Inputs, numbered Steps, Definition of Done) and no nested references; structure is good, though at >50 lines some large diff examples could theoretically split out, leaving a minor organization gap versus a clean 5.

4 / 5

Total

15

/

20

Passed

Description

57%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 specific and distinctive about a narrow domain (JIT-EE interface extension) but is missing an explicit 'Use when' trigger clause and only states a single generic action. Adding trigger phrasing and one or two more concrete actions would lift completeness and specificity.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g. 'Use when extending the JIT-VM/JIT-EE interface or adding a new JIT-to-VM API').

List the concrete supporting actions the skill performs (e.g. updating ThunkInput.txt, regenerating via gen.sh, wiring SuperPMI record/replay) to raise specificity.

Include natural synonyms users might say (e.g. 'JIT-EE API', 'corinfo.h interface', 'SuperPMI') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('JIT-VM (aka JIT-EE) interface') and one concrete action ('Add a new API'), but the action is generic and coverage is not comprehensive. It sits between anchor 2 (generic action) and anchor 4 (several specific actions), closer to the minimal-but-concrete band.

3 / 5

Completeness

It clearly states the 'what' ('Add a new API to the JIT-VM interface in the codebase') but provides no explicit 'Use when...' / 'when' guidance, so per the missing-trigger-clause rule completeness is capped at 3.

3 / 5

Trigger Term Quality

It surfaces relevant keywords a user might say ('Add a new API', 'JIT-VM', 'JIT-EE', 'interface') including the two common synonyms, but lacks file extensions or broader natural variations, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The phrase targets a very specific niche ('JIT-VM / JIT-EE interface' extension) with distinct triggers, making conflict with unrelated skills minimal, matching the clear-niche anchor.

5 / 5

Total

14

/

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
dotnet/runtime
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.