skills-index

Index of all available skills across both Gemini CLI (.gemini/skills/) and GitHub Copilot (.github/skills/). Load this to find the right skill for a task, or to locate the counterpart skill in the other AI system.

Quality

64%

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 ./.gemini/skills/skills-index/SKILL.md

Quality

Content

72%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise, well-structured, and free of fluff, but the skill's central purpose — selecting the right skill or counterpart — lacks an actionable decision procedure and verification step, weakening its guidance for the most common use case.

Suggestions

Add a short decision procedure for the primary lookup, e.g. criteria or an ordered checklist for choosing among shared/copilot-only/gemini-only skills given a task description.

Include a verification step in the add-skill workflow, such as confirming both files exist and that the copilot-instructions table entry was added before considering the task complete.

Surface the richer-version guidance as an explicit rule (e.g. 'prefer the Gemini version for testing/settings, the Copilot version for plugin dev/navigation') so the cross-reference is actionable rather than descriptive.

Dimension	Reasoning	Score
Conciseness	The body is lean and table-driven, with no explanation of concepts Claude already knows and no padding; every line (skill mappings, purposes, add instructions) earns its place.	3 / 3
Actionability	Provides concrete reference data (specific skill names, file paths) and an actionable 'Adding a New Skill' section, but offers no decision procedure for the core task of choosing the right skill from the index, leaving the primary lookup under-guided.	2 / 3
Workflow Clarity	The 'Adding a New Skill' section lists steps, but the primary 'find the right skill for a task' workflow has no sequenced decision logic, and no validation/verification checkpoint exists for confirming a chosen skill applies.	2 / 3
Progressive Disclosure	A single, well-organized file with clearly labeled sections and tables; no external bundle references are needed and navigation is straightforward, satisfying the simple-skill note for progressive disclosure.	3 / 3
	Total	10 / 12 Passed

Description

57%Weight 40%Scale 1-3

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 occupies a distinct niche, but its trigger guidance is implied rather than explicit and its action vocabulary is narrow, leaving the core 'when to load this' condition underspecified.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks which skill to use, or when you need to find a skill's counterpart in the other AI system.'

Broaden the natural trigger terms to include variations users actually say, such as 'which skill', 'skill for this task', or 'Gemini vs Copilot skills'.

Distinguish the two use cases more sharply (choosing a skill vs. locating its cross-system counterpart) so the actions read as distinct capabilities rather than synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain ('Index of all available skills') and two concrete actions ('find the right skill for a task', 'locate the counterpart skill'), but the actions overlap as variants of a single lookup capability rather than a broad, comprehensive set of distinct actions.	2 / 3
Completeness	Clearly answers 'what' (an index/cross-reference of skills across two AI systems), but the 'when' is only implied through 'Load this to find the right skill for a task' rather than stated as an explicit trigger condition, capping completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Contains natural phrases a user might say ('find the right skill', 'counterpart skill'), but lacks common trigger variations and has no explicit 'Use when...' clause; terms are purpose-oriented rather than trigger-oriented.	2 / 3
Distinctiveness Conflict Risk	Occupies a clear niche — cross-referencing skills between Gemini CLI and GitHub Copilot — with triggers unlikely to fire for any other skill, so conflict risk is low.	3 / 3
	Total	9 / 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: netalertx/NetAlertX
Path: .gemini/skills/skills-index/SKILL.md
Commit: 20ddf48

Reviewed: 6 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.