CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

install-store-skill

Install a Skill from the OpenAkita Platform Skill Store

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/system/install-store-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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-structured instruction skill: concrete tool tables, an explicit workflow, and useful license/fallback notes with zero padding. The only meaningful gap is the absence of validation — particularly the silent overwrite of an existing same-named skill — which caps workflow clarity.

Suggestions

Add a verification step after install, e.g. call `list_skills` (or equivalent) to confirm the skill is loaded and report the result to the user.

Before installing when "a skill with the same name already exists locally", instruct Claude to surface the pending update to the user and confirm, since the update overwrites the local version.

DimensionReasoningScore

Conciseness

The body is lean — parameter tables, terse workflow steps, no explanations of concepts Claude already knows — with only minor redundancy: the opening line repeats the frontmatter description and the "auto-loaded and immediately usable" note restates workflow step 4. It matches anchor 4 ('efficient, minor instances that could be trimmed') rather than 5 because of that small duplication.

4 / 5

Actionability

Every tool is named with an exact parameter table (`skill_id`, `repo_url`), the workflow gives concrete call-by-call steps with optional steps marked, and the fallback section names specific alternative tools. Per the rubric's code-vs-instruction note, an instruction-only skill with fully actionable guidance like this earns the top anchor.

5 / 5

Workflow Clarity

The sequence is clearly numbered with optional steps flagged, but there are no validation checkpoints at all — no verification that installation succeeded, and "If a skill with the same name already exists locally, it will be updated" is a destructive overwrite with no confirm-or-check step, which the rubric caps at 3. Not a 2 because the sequence itself is well-defined and gaps are only in checkpoints.

3 / 5

Progressive Disclosure

The skill is under 50 lines, self-contained with no external references needed, and organized into clear sections (When to Use, Workflow, Tools, Important Notes, Fallback). The rubric's simple-skill exception explicitly allows a 5 for well-organized short skills without external file references.

5 / 5

Total

17

/

20

Passed

Description

53%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 is accurate and distinct but minimal: it states a single concrete action with no use-when trigger guidance and no mention of the skill's broader capabilities (search, preview, submission). Adding a "Use when..." clause and one or two more concrete actions would lift the completeness and specificity dimensions substantially.

Suggestions

Add a "Use when..." clause with concrete trigger phrases, e.g. "Use when the user asks to install, add, or download a skill from the store, mentions the Skill Store, or provides a Skill ID."

Mention one or two additional concrete actions from the body, such as searching store skills or inspecting a skill's license and ratings before install.

Include natural language variations users would actually say (e.g. "add skill", "安装技能") alongside the platform terminology to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ("OpenAkita Platform Skill Store") and one concrete action ("Install a Skill"), but omits the search, detail-preview, and repo-submission capabilities the body documents, matching the '1-2 concrete actions, not comprehensive' anchor. It is not generic enough for a 2, and does not list several specific actions required for a 4.

3 / 5

Completeness

It clearly answers "what" (installs a skill from the platform skill store) but contains no "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. Not a 2 because the "what" is clear, not vague; not a 4 because the "when" is entirely absent rather than just imprecise.

3 / 5

Trigger Term Quality

"Install", "Skill", and "Store" are relevant domain keywords comparable to the 'Works with PDF files' anchor, but natural user variations like "add skill", "download", or "安装" are missing. It rises above anchor 2 because the keywords are domain-specific rather than generic, but lacks the synonym coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

"OpenAkita Platform Skill Store" carves out a clear niche with minimal conflict risk against unrelated skills, fitting the 'mostly distinct' anchor. It falls short of 5 because the description offers no explicit trigger phrases and the body reveals overlap with the more general install_skill/GitHub path.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

openakita/openakita

Path

skills/system/install-store-skill/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.