skills-index

Index of all available skills across Gemini CLI (.gemini/skills/), GitHub Copilot (.github/skills/), and Claude Code (.claude/skills/). Load this to find the right skill for a task, or to locate the counterpart skill in another assistant's tree.

Quality

68%

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

75%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-organized, actionable cross-reference index with clear sections and a concrete add-skill workflow backed by a CI drift check. Its main limitation is minor verbosity in several table note cells.

Suggestions

Tighten the longest table note cells (scan-pipeline, prd-writing, skill-hygiene) to one-line summaries, moving depth into the linked skill files.

Add an explicit validation/feedback step to the 'Adding a New Skill' workflow (e.g., 'run check-skill-pairs locally and confirm no drift before opening the PR').

Consider extracting the per-skill detail columns into a separate reference file so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is a dense, well-structured index table that mostly respects token budget and avoids explaining concepts Claude already knows. A few note cells (scan-pipeline, prd-writing, skill-hygiene) are paragraph-length and could be trimmed, matching anchor 4 rather than the lean anchor 5.	4 / 5
Actionability	Provides concrete, actionable guidance including specific file paths ('.gemini/skills/<name>/SKILL.md', 'scripts/check_skill_pairs.py', 'GROUPS') and a stepwise 'Adding a New Skill' section with named targets. It falls short of anchor 5 only because some cells describe rather than instruct.	4 / 5
Workflow Clarity	The 'Adding a New Skill' workflow is a clear sequence (create in both trees, add copilot-instructions.md entry, optionally mirror to Claude, add to GROUPS) with the CI drift-check acting as a validation checkpoint. It is below anchor 5 because error-recovery feedback loops are not made explicit.	4 / 5
Progressive Disclosure	Content is organized into clear sections (Shared Skills, Copilot-Only, Gemini-Only, Adding a New Skill) with no nested references, and bundle directories do not exist so all structure is self-contained. It is anchor 4 rather than 5 because a couple of inlined note cells read like detail that could live elsewhere.	4 / 5
	Total	16 / 20 Passed

Description

62%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 conveys a distinctive cross-assistant skill-index niche with both a what and a when clause. It is held back by limited trigger-term variation and only two named actions.

Suggestions

Add explicit 'Use when...' trigger phrasing with concrete natural terms (e.g., 'Use when you need to find a skill, compare skills across assistants, or locate the Claude/Gemini/Copilot equivalent of a skill').

Broaden trigger-term coverage with synonyms users actually say ('skill lookup', 'which skill', 'cross-reference skills', 'counterpart').

Name one or two more concrete actions (e.g., 'browse available skills', 'compare skill depth across assistants') to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (an index of skills across three concrete trees) and two concrete actions ('find the right skill for a task', 'locate the counterpart skill in another assistant's tree'), but coverage is not comprehensive. It sits at anchor 3 rather than 4 because only two actions are listed with minor gaps.	3 / 5
Completeness	Explicitly states both what (index of available skills across three trees) and when ('Load this to find the right skill for a task, or to locate the counterpart skill'), but the trigger clause could be more specific, so it falls short of anchor 5.	4 / 5
Trigger Term Quality	Contains some natural phrases a user might say ('find the right skill for a task', 'counterpart skill') but lacks synonyms and file-extension-style variants, matching anchor 3 rather than the fuller coverage of anchor 4.	3 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (cross-referencing skills across Gemini/Copilot/Claude trees) with a distinctive 'counterpart skill' trigger, but 'find the right skill' could mildly overlap with skill-activation skills, keeping it below anchor 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: netalertx/NetAlertX
Path: .gemini/skills/skills-index/SKILL.md
Commit: 014b960

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