get-search-view-results

Get the current search results from the Search view in VS Code

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./extensions/copilot/assets/prompts/skills/get-search-view-results/SKILL.md

Quality

Content

85%

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 tight, highly actionable three-step instruction that names the exact command, tool, and argument to use, with a clear single-step workflow and appropriate organization for a short skill. Its only weakness is minor padding in the framing and closing clause that keeps conciseness just below the top anchor.

Suggestions

Drop the obvious framing in step 1 and the "as we know it does" aside to make every token load-bearing.

Optionally show the literal `copilot_runVscodeCommand` invocation with the command and skipCheck argument inline so the call is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is short and mostly efficient, but step 1 ("VS Code has a search view, and it can have existing search results") states context Claude already knows and step 3's "as we know it does" is filler, so not every token earns its place.	2 / 3
Actionability	It names the exact command (`search.action.getSearchResults`), the exact tool (`copilot_runVscodeCommand`), and the exact argument value (`skipCheck` as true), giving fully executable, copy-paste-ready guidance.	3 / 3
Workflow Clarity	This is a simple single-step task with a clear numbered sequence and an unambiguous action; as a read-only get operation it needs no validation checkpoint, so the simple-skill allowance applies.	3 / 3
Progressive Disclosure	The skill is under 50 lines, needs no external references, and is organized into a clear heading plus a numbered list, meeting the 'well-organized sections' bar for simple skills.	3 / 3
	Total	11 / 12 Passed

Description

50%

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 concise and states a clear single action in a specific niche, but it omits any 'Use when...' trigger guidance and offers only one action with limited keyword coverage. It is solid but falls short of the top anchor on completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to retrieve or inspect current results shown in the VS Code Search view.'

Broaden keyword coverage to include natural variations users might say, such as 'search panel', 'find results', or 'search results list'.

If there are related actions (e.g. reading result count, iterating matches), mention them to lift specificity above a single action.

Dimension	Reasoning	Score
Specificity	The description names a concrete action ("Get the current search results") and a clear domain ("the Search view in VS Code"), but lists only a single action rather than the multiple specific actions the top anchor calls for.	2 / 3
Completeness	It clearly states what the skill does but provides no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like "search results", "Search view", and "VS Code" are natural, but coverage is thin with no common variations or explicit trigger phrasing, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The VS Code Search view niche is fairly specific, but the absence of distinct trigger phrasing means it could still overlap with other VS Code-related skills rather than being unmistakably unique.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: posit-dev/positron
Path: extensions/copilot/assets/prompts/skills/get-search-view-results/SKILL.md
Commit: b87c504

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.