CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

install-scripts

Read before editing anything under install/ (production-filesystem/, ubuntu24/, etc.) or reviewing a PR that touches it. Covers uninstall safety, why check-*.sh scripts don't all exit the same way, and what's legacy vs. active.

68

Quality

86%

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

The canonical home for this skill is install-scripts in netalertx/NetAlertX

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 tight, well-organized instruction-only skill that gives concrete file-level review guidance without over-explaining basics. It lacks runnable commands, which keeps actionability and workflow_clarity at 4 rather than 5, but structure and conciseness are strong.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence — it names PHP/nginx/avahi as system packages without explaining them — with only mild rationale sentences (e.g. the bare-metal host-sharing justification) that could be trimmed, matching anchor 4 rather than 5 or 3.

4 / 5

Actionability

Provides concrete, specific guidance with real file paths (install/*/uninstall.sh, check-first-run-config.sh, check-ramdisk.sh, back/cron_script.sh) and a concrete directive to check what a script guards before changing its exit behavior; matches anchor 4, not 5 (no copy-paste commands covering common cases) and not 3 (concrete, not pseudocode).

4 / 5

Workflow Clarity

Not a destructive/batch workflow so the validation cap does not apply; the review concerns are organized into clear, well-delineated sections making what to check unambiguous, matching anchor 4 rather than 5 (no explicit sequenced workflow with checkpoints, though the skill isn't that kind) or 3.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references and well-organized section headers, plus a clearly signaled one-level cross-skill pointer ('See the devcontainer-configs/devcontainer-management skills for...'), so the simple-skill exception earns anchor 5.

5 / 5

Total

17

/

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, specific description that clearly states both when to read it and what it covers, scoped tightly to install-script review concerns with natural trigger phrases. The only gap is minor synonym coverage in the trigger terms.

DimensionReasoningScore

Specificity

Lists several concrete covered areas — 'uninstall safety', 'why check-*.sh scripts don't all exit the same way', and 'what's legacy vs. active' — which is several specific items with only minor gaps, matching anchor 4 rather than 5 (these are covered topics, not a comprehensive action list) or 3 (more than 1-2 concrete items).

4 / 5

Completeness

Explicitly answers both — 'when' via 'Read before editing anything under install/... or reviewing a PR that touches it' and 'what' via 'Covers uninstall safety, why check-*.sh scripts don't all exit the same way, and what's legacy vs. active' — with concrete trigger phrases, matching anchor 5.

5 / 5

Trigger Term Quality

Natural trigger phrases 'editing anything under install/' and 'reviewing a PR that touches it' plus named subdirs give good coverage matching anchor 4; not 5 because common synonyms like 'install scripts' or 'uninstall' as standalone triggers are missing, and not 3 because coverage is clearly above 'some'.

4 / 5

Distinctiveness Conflict Risk

Scoped specifically to install/* scripts with named subdirs (production-filesystem/, ubuntu24/), giving a clear niche with minimal conflict risk, matching anchor 5.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

netalertx/NetAlertX

Path

.gemini/skills/install-scripts/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.