CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

67

Quality

84%

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

SKILL.md
Quality
Evals
Security

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.

A well-built index: tables distinguish skill versions by substantive differences rather than padding, and the add-a-skill workflow is concrete with exact paths and drift-checking hooks. Main gaps are trimmable provenance narration and a missing explicit pre-PR validation step in the workflow.

Suggestions

Drop or compress provenance narration like 'mined from real review comments (#1214/#1230/#1235)' — the rule references matter, the PR archaeology does not.

Add an explicit final step to the 'Adding a New Skill' workflow: run 'check-skill-pairs' locally (or rely on CI) to verify the new group is in GROUPS before opening the PR.

Tighten the longest Notes cells (devcontainer, install-scripts, pr-analysis rows) to their one-line distinguishing point.

DimensionReasoningScore

Conciseness

Dense, information-rich tables that carry only non-obvious per-version differences ('Gemini version is more comprehensive (22-point guide...); Copilot version covers ccd()') with no re-teaching of known concepts. Minor trimmable narration like 'mined from real review comments (#1214/#1230/#1235)' keeps it below 5.

4 / 5

Actionability

Concrete, executable guidance throughout: exact paths ('.gemini/skills/<name>/SKILL.md'), file names ('scripts/check_skill_pairs.py', 'GROUPS'), and specific adaptation rules ('adapt any such tool references to plain Bash commands'). Not 5 because the core content is lookup pointers rather than copy-paste-ready commands.

4 / 5

Workflow Clarity

'Adding a New Skill' is a clear sequence (create in both trees, keep bodies identical, optionally mirror to Claude, add to GROUPS) and the CI drift check is named. It lacks an explicit local validation step ('run check-skill-pairs before the PR'), so it does not reach 5; the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

Single-file skill with well-organized sections (Shared / Copilot-Only / Gemini-Only / Adding) that needs no external references since it is itself the reference index. A few long Notes rows could be thinned, keeping it just below the well-organized simple-skill ideal of 5.

4 / 5

Total

16

/

20

Passed

Description

87%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.

A strong description: third-person, concise, concrete paths for all three trees, and an explicit 'Load this to...' trigger clause covering both lookup use cases. Its only weakness is keyword coverage of common phrasings users might use when choosing between skills.

Suggestions

Add one more natural trigger phrase such as 'which skill should I use for a task' to broaden keyword coverage.

Mention that it also governs adding/syncing new skills across trees, since that workflow is a significant part of the body.

DimensionReasoningScore

Specificity

Names the domain with concrete paths ('.gemini/skills/', '.github/skills/', '.claude/skills/') and several specific actions ('find the right skill for a task', 'locate the counterpart skill in another assistant's tree'). Falls short of 5 only because it omits the skill-authoring/sync guidance the body actually covers.

4 / 5

Completeness

Explicitly answers both what ('Index of all available skills across Gemini CLI... Copilot... and Claude Code') and when ('Load this to find the right skill for a task, or to locate the counterpart skill') with concrete trigger phrasing, matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

Includes natural terms users would say — 'skill', 'find the right skill', 'counterpart skill', plus the assistant names (Gemini CLI, Copilot, Claude Code). A few common phrasings like 'which skill should I use' are missing, so not a 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche — a cross-assistant skills index — with distinct triggers ('counterpart skill in another assistant's tree') that no individual skill file would claim; minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

netalertx/NetAlertX

Path

.gemini/skills/skills-index/SKILL.md

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.