Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

orbit

Old remote

Quality

18%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./crates/orbit-cli/tests/fixtures/skills/old-remote/SKILL.md

Quality

Content

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

The skill body is an empty shell: a single heading plus an include directive whose target is missing from the bundle. It provides no instructions, workflow, or references, so Claude cannot act on it. The content needs to be fully authored or the missing shared content restored.

Suggestions

Replace the "orbit:include local:shared" build comment with actual instructional content, or ship the referenced shared file in a references/ directory so the include resolves.

Add concrete, executable guidance (commands, code, or specific steps) describing what to do with the Orbit remote, per the description's stated purpose.

If the skill's operations are destructive or batch-oriented, include a numbered workflow with explicit validation and verification checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is only a "# Remote" heading and an HTML build comment, so while it uses almost no tokens, it delivers zero guidance — the occupied context earns nothing. This is the extreme-failure end of token efficiency, not the lean-but-complete anchor 5.	1 / 5
Actionability	There is no code, command, or concrete instruction anywhere in the body; the "orbit:include local:shared" comment is a build directive, not executable guidance. Matches anchor 1 (entirely vague; no concrete code or commands).	1 / 5
Workflow Clarity	No steps or sequence of any kind are present, so validation checkpoints are moot. Anchor 1 (steps missing or incoherent; no sequence) is the closest fit and anchors 2-3 require at least a rough sequence.	1 / 5
Progressive Disclosure	The body has no navigable structure or content, and its only reference ("local:shared") is a build-time include with no corresponding file — no references/, scripts/, or assets/ exist in the bundle. Anchor 1 (impossible to navigate) applies.	1 / 5
	Total	4 / 20 Passed

Description

0%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 "Old remote" fails on every dimension: it names no capability, no domain, no trigger conditions, and is indistinguishable from any other remote-related skill. It reads as a stale placeholder rather than a functional description.

Suggestions

Rewrite the description in third person naming concrete actions and the domain, e.g. "Manages Orbit remotes via the Orbit CLI: <action 1>, <action 2>.", replacing the placeholder "Old remote".

Add an explicit "Use when..." clause listing natural trigger phrases and file/command extensions users would actually say.

Include distinguishing details (Orbit CLI, specific remote types or operations) so the description cannot fire for unrelated remote/connection skills.

Dimension	Reasoning	Score
Specificity	The description is just "Old remote" — no concrete actions or domain are named. This matches anchor 1 (entirely vague, pure abstract language), and not anchor 2, which still requires naming a domain with minimal actions.	1 / 5
Completeness	Neither the "what" (two vague words with no capability statement) nor the "when" (no Use-when clause or equivalent) is present. This is anchor 1 (missing both what and when, or both extremely vague), below the missing-trigger cap of 3.	1 / 5
Trigger Term Quality	"Old remote" contains no natural keywords a user would say when needing this skill; the terms are entirely generic. Anchor 1 (no natural keywords; entirely generic language) fits; anchor 2 requires at least one or two generic keywords.	1 / 5
Distinctiveness Conflict Risk	"Old remote" is entirely generic and would collide with virtually any remote-related skill. Anchor 1 (entirely generic; would conflict with virtually any skill) is the best fit.	1 / 5
	Total	4 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
description_field	'description' is very short (10 chars), consider making it more detailed	Warning
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: gitlabhq/orbit-knowledge-graph
Path: crates/orbit-cli/tests/fixtures/skills/old-remote/SKILL.md
Revision: ed321d9

Reviewed: 27 days ago

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.

orbit

Table of Contents

Is this your skill?