CtrlK
BlogDocsLog inGet started
Tessl Logo

load-skill

Load, activate, and optionally install an AI skill from a .skill file. Use this skill when the user wants to load, activate, or use a skill file. The user can invoke this skill with slash command `/load-skill [ --install | -i ] SKILLFILE`, where SKILLFILE is the path to a .skill file.

82

1.16x
Quality

78%

Does it follow best practices?

Impact

86%

1.16x

Average score across 3 eval scenarios

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./load-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 clear, reasonably lean instruction skill with concrete steps and good structure. Its main weakness is workflow validation: the permanent auto-install step proceeds without verifying SKILL.md was found or the install succeeded.

Suggestions

Add an explicit validation checkpoint after extraction to confirm SKILL.md was located and is readable before proceeding to install/activate.

Add a verify-after-install step (e.g., confirm the skill appears in the skills folder) with error-recovery guidance, since --install performs a persistent write without prompting.

Trim the screenshot aside and the '(depending on how the skill was packaged)' parenthetical to tighten the body.

DimensionReasoningScore

Conciseness

Mostly efficient step-by-step guidance with one concrete command; a few lines of padding (the screenshot aside, the packaging parenthetical) could be trimmed, but it is not verbose.

4 / 5

Actionability

Provides a concrete executable command ('unzip -o "SKILLFILE" -d "TEMPDIR"') and specific actionable steps (validate extension, locate SKILL.md, install, activate, clean up), with only minor gaps.

4 / 5

Workflow Clarity

An clear 8-step sequence exists with one validation checkpoint (verify file exists/extension), but a permanent un-prompted install lacks verification/feedback loops, so the validation cap applies.

3 / 5

Progressive Disclosure

Well-organized into Usage, How to Process, Examples, and Notes sections with no nested references; content is appropriately inline for a simple skill with only minor organization gaps.

4 / 5

Total

15

/

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 that clearly answers what the skill does and when to use it, with concrete actions and distinct, low-conflict triggers. Minor room to add synonyms, but no significant weaknesses.

DimensionReasoningScore

Specificity

Names three concrete actions ('Load, activate, and optionally install an AI skill from a .skill file') plus the slash-command syntax, giving several specific actions with only minor coverage gaps.

4 / 5

Completeness

Explicitly states both what it does (load/activate/install a skill from a .skill file) and when to use it ('Use this skill when the user wants to load, activate, or use a skill file'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('load, activate, or use a skill', 'skill file', '.skill file') and the '/load-skill' command; a few synonyms could be added but coverage is good.

4 / 5

Distinctiveness Conflict Risk

The '.skill file' / '/load-skill' niche is distinct with minimal overlap risk; triggers are specific to skill loading rather than generic file handling.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fpl9000/ai-skills
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.