CtrlK
BlogDocsLog inGet started
Tessl Logo

help

Show skill-bus overview, status, and available commands. Quick reference for all skill-bus features.

66

Quality

78%

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 ./skill-bus/skills/help/SKILL.md
SKILL.md
Quality
Evals
Security

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 an appropriately minimal, actionable delegation stub for a simple skill — concise, executable, and unambiguous with no unnecessary references.

DimensionReasoningScore

Conciseness

The body is three lean lines that state the delegation and give the command, assuming Claude's competence with no padding, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

It provides a fully executable, copy-paste-ready command ('Run the command directly: /skill-bus:help'), fitting the 'fully executable code/commands; copy-paste ready' anchor rather than the pseudocode level 2.

3 / 3

Workflow Clarity

This is a simple single-purpose skill whose single action (run /skill-bus:help) is unambiguous, which the simple-skills note allows to score 3 without a multi-step workflow.

3 / 3

Progressive Disclosure

Under 50 lines with a clear heading and no need for external references (verified: no references/scripts/assets bundle files exist), so per the simple-skills note well-organized content scores 3.

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 concise and third-person with a clear niche, but it omits an explicit 'when to use' trigger clause and its action/trigger vocabulary is only moderately specific.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about skill-bus status, available commands, or how to use skill-bus.'

Expand the action vocabulary with natural user phrasings (e.g. 'help', 'commands list', 'what can skill-bus do') to improve trigger-term coverage.

Consider naming a couple more concrete sub-features to push specificity from 'some actions' toward a comprehensive multi-action list.

DimensionReasoningScore

Specificity

Names a domain and a few concrete actions ('overview, status, and available commands') but the list is not comprehensive, matching the 'names domain and some actions' anchor rather than the multi-action level 3.

2 / 3

Completeness

It states what the skill does ('Show skill-bus overview, status, and available commands') but lacks any explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Terms like 'skill-bus overview', 'status', and 'available commands' are relevant but somewhat generic/technical and miss common natural variations, fitting the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The 'skill-bus' qualifier carves a clear niche with distinct triggers that would not naturally fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor; it is not the vague level-2 'works with document files' case.

3 / 3

Total

9

/

12

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
composio-community/awesome-claude-plugins
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.