CtrlK
BlogDocsLog inGet started
Tessl Logo

device-guidance-v1-0-2

Helps employees identify available device options based on their needs, using the `Get Employee Assets` tool.

60

Quality

70%

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 ./docs/recruit-nextgen/06-add-skills/assets/device-guidance-v1-0-2/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 lean, highly actionable conversational workflow with concrete SharePoint/OData specifics and clear branching for edge cases, hindered only by a minor lack of explicit validation checkpoints.

DimensionReasoningScore

Conciseness

The body is efficient and focused on domain-specific knowledge Claude would not know (SharePoint internal column names, OData filter syntax, thumbnail sizing); a few instructional sentences could be tightened but there is no padding. Not a 5 because some phrasing is slightly more explanatory than necessary.

4 / 5

Actionability

Provides fully concrete, executable guidance: exact table columns, an alphabet-option-to-Item-ID mapping rule, internal field names with a worked OData example ('$filter=field_4 eq \'Laptop\' and field_2 eq \'Dell\''), thumbnail pixel ranges, and ready-to-use quote prompts.

5 / 5

Workflow Clarity

Steps are clearly sequenced (clarify, look up, present, handle unavailability, confirm) with explicit conditional branches for edge cases. Not a 5 because there is no explicit validation/checkpoint step, though the operation is conversational rather than destructive so the destructive cap does not apply.

4 / 5

Progressive Disclosure

Under 50 lines with no external references needed and no bundle files present; content is well-organized into clearly headed sections, which per the rubric earns a 5 for simple skills.

5 / 5

Total

18

/

20

Passed

Description

53%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 states what the skill does and ties it to a specific tool, but it omits any explicit 'Use when...' trigger guidance, which caps its completeness and leaves trigger-term coverage thin.

Suggestions

Add an explicit trigger clause, e.g. 'Use when an employee asks about finding, selecting, or requesting a device.'

Include natural synonyms users might say (laptop, desktop, phone, peripheral) to improve trigger-term coverage.

Name a second concrete action (e.g. presenting options or initiating a request) to lift specificity above a single action.

DimensionReasoningScore

Specificity

Names the domain (device options) and one concrete action ('identify available device options based on their needs') plus a named tool, but coverage is not comprehensive. Not a 4 because only a single action is described.

3 / 5

Completeness

Has a clear 'what' ('Helps employees identify available device options...using the Get Employee Assets tool') but no 'when'/'Use when...' trigger clause; per the rubric a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant natural terms like 'device' and 'device options', but lacks common variations/synonyms and explicit trigger phrases users would say. Not a 4 because keyword coverage is thin and no synonyms are present.

3 / 5

Distinctiveness Conflict Risk

Scoped to employee device options via a specific named tool (Get Employee Assets), giving it a clear niche with only minor overlap risk. Not a 5 because the phrasing is generic enough that it could brush against general IT-request skills.

4 / 5

Total

13

/

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
microsoft/agent-academy
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.