CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

orbit-cli

Old local

Quality

25%

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

Fix and improve this skill with Tessl

tessl review fix ./crates/orbit-cli/tests/fixtures/skills/old-local/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

18%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 body is an empty template remnant: an orbit:section comment block around a heading reading "Old local shared". It provides no actionable instruction, no workflow, and no content for a reader to act on, and appears to be leftover merge scaffolding rather than a skill document.

Suggestions

Replace the placeholder heading and orbit:section markers with actual instructions for the Orbit CLI, including executable commands (e.g. install, auth, and common task invocations).

Document a concrete workflow with sequenced steps and validation checkpoints (e.g. run the CLI, verify output, handle errors) so Claude knows exactly what to do.

State the "Requires Orbit CLI" dependency in the body with setup/verification commands, and move any lengthy reference material into a references/ file linked from the body.

DimensionReasoningScore

Conciseness

The body has no padded explanations, but the "<!-- orbit:section shared -->" template markers and the vague heading "Old local shared" are unnecessary tokens that could be trimmed, matching the anchor "includes some unnecessary explanation or could be tightened" rather than the level-5 anchor where every token earns its place.

3 / 5

Actionability

The body contains no code, commands, or concrete guidance of any kind — only a heading and HTML comments — matching the anchor "Entirely vague or abstract; no concrete code or commands; only describes rather than instructs" (it does not even reach the level-2 anchor's high-level hints).

1 / 5

Workflow Clarity

There are no steps, sequence, or validation checkpoints whatsoever; the body is a placeholder, matching the anchor "Steps missing or incoherent; no sequence."

1 / 5

Progressive Disclosure

The body has minimal structure (one heading wrapped in template markers), no references or navigation to any detail files, and no real content to organize — matching the anchor "Minimal structure"; it cannot score 3+ because there is no content or clearly signaled organization at all.

2 / 5

Total

7

/

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 local" is a placeholder with no informational value: it conveys neither capabilities nor usage triggers, and creates maximum conflict risk with other skills. It resembles the rubric's bad examples ("Helps with documents", "Does stuff with files") but is even vaguer.

Suggestions

Rewrite the description in third person to state concrete capabilities, e.g. "Runs Orbit CLI commands to build, test, and deploy Orbit projects. Use when the user mentions the Orbit CLI, orbit.yaml, or deploying Orbit services."

Add an explicit "Use when..." clause with natural trigger phrases (tool name, file names, common synonyms) so the skill fires only on relevant requests.

Differentiate the skill from generic build/deploy skills by naming Orbit-specific artifacts and workflows in the description.

DimensionReasoningScore

Specificity

The description is just "Old local" — it names no domain and no concrete actions, matching the anchor "Entirely vague; no concrete actions; pure abstract language" and falling below "Names the domain but actions are minimal".

1 / 5

Completeness

Neither what the skill does nor when to use it is stated in any form; this matches the anchor "Missing both what and when" and is below the level-2 anchor, which requires at least a vague what or a when.

1 / 5

Trigger Term Quality

"Old local" contains no natural keywords, synonyms, or file extensions users would say; it is entirely generic language, matching the lowest anchor and not the level-2 anchor ("One or two generic keywords").

1 / 5

Distinctiveness Conflict Risk

"Old local" is entirely generic with no niche or distinct triggers, so it is indistinguishable from and would conflict with virtually any other skill.

1 / 5

Total

4

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

description_field

'description' is very short (9 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-local/SKILL.md

Revision

ed321d9

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill