skill-installer

Install workspace skills from curated sources or import open-source skills from GitHub.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./runtime/harnesses/src/embedded-skills/skill-installer/SKILL.md

Quality

Content

100%

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 tight, actionable reference: concrete endpoints and bodies, a preview-then-install checkpoint, and clean sectioning with no padding. It models good token-efficient skill authoring.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: it gives operational specifics (endpoints, body shapes, URL patterns, install paths) without explaining what skills, GitHub, or frontmatter are.	3 / 3
Actionability	It provides concrete, copy-paste-ready guidance: exact POST endpoints, JSON request bodies, accepted URL formats, and the destination path skills/<id>/.	3 / 3
Workflow Clarity	The import flow is a clear preview-then-install sequence where the preview step is an explicit confirmation checkpoint before any write; for this simple skill that suffices.	3 / 3
Progressive Disclosure	The skill is under 50 lines with no need for external references, and its content is organized into well-signaled sections (Import, Notes); no bundle files exist to evaluate.	3 / 3
	Total	12 / 12 Passed

Description

57%

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 clear and occupies a distinct niche, but it stops at naming actions without an explicit 'when to use' trigger and leaves 'curated sources' vague. Adding a Use-when clause and naming the curated sources would raise it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to install, add, or import a skill into the workspace.'

Name the curated sources instead of the vague 'curated sources' phrase, or specify what 'workspace skills' refers to.

Include common trigger variations like 'add', 'download', or 'get skills' to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names two concrete actions ('Install workspace skills from curated sources', 'import open-source skills from GitHub'), but 'curated sources' is left unspecified, so it names the domain and some actions without being fully comprehensive.	2 / 3
Completeness	It clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	It includes relevant natural terms ('install', 'import', 'skills', 'GitHub') that a user might say, but misses common variations such as 'add', 'download', or 'get skills'.	2 / 3
Distinctiveness Conflict Risk	Skill installation/importing is a clear niche with distinct triggers ('install workspace skills', 'import ... from GitHub') that are unlikely to fire for unrelated skills.	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: holaboss-ai/holaOS
Path: runtime/harnesses/src/embedded-skills/skill-installer/SKILL.md
Commit: 74c7b6f

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.