CtrlK
BlogDocsLog inGet started
Tessl Logo

hub-status

Show DAG state, agent progress, and branch status for an AgentHub session. Use when the user runs /hub:hub-status or asks how the AgentHub agents are doing.

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./engineering/agenthub/skills/hub-status/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-structured, actionable status skill with concrete commands and clear conditional follow-up. Its main weakness is a redundant second output example, and the referenced scripts are not present in the bundle.

Suggestions

Remove or compress the second output example ("Example output for a content task") to a one-line note, since it duplicates the first block's structure.

Add a brief hint for obtaining a session id (e.g., listing recent sessions) when the user does not supply one.

Either include the referenced scripts (session_manager.py, dag_analyzer.py, board_manager.py) in a scripts/ bundle or note that they are provided by the AgentHub runtime.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the second full output block ("Example output for a content task") largely duplicates the first example's structure with different data — padding that could be trimmed to a brief note.

3 / 5

Actionability

Concrete, executable commands with flags are provided (e.g. `python {skill_path}/scripts/session_manager.py --status {session-id}`), and the usage block shows the session-id format; minor gaps remain around how to discover a session id when not supplied.

4 / 5

Workflow Clarity

Three numbered steps are clearly sequenced with the conditional "After Status" follow-up guidance providing a feedback path; as a read-only status skill it needs no destructive-operation validation, so the minor checkpoint gaps keep it at 4 rather than 5.

4 / 5

Progressive Disclosure

Content is well-organized into clearly labeled sections (Usage, What It Does, Output Format, After Status) with no nested references; however the referenced `{skill_path}/scripts/*.py` files do not exist in any bundle directory, a minor organization gap.

4 / 5

Total

15

/

20

Passed

Description

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

A strong, third-person description that clearly states both capability and trigger conditions with concrete, domain-specific language. The only weakness is a slight under-coverage of natural trigger synonyms.

DimensionReasoningScore

Specificity

"Show DAG state, agent progress, and branch status" names several concrete actions with comprehensive coverage of the skill's scope, but omits board updates which the body later surfaces — a minor gap keeping it just below a 5.

4 / 5

Completeness

It explicitly answers both what ("Show DAG state, agent progress, and branch status for an AgentHub session") and when ("Use when the user runs /hub:hub-status or asks how the AgentHub agents are doing") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"Use when the user runs /hub:hub-status or asks how the AgentHub agents are doing" gives good keyword coverage including a natural phrase and the command, but misses common synonyms like "status" or "progress" as trigger terms.

4 / 5

Distinctiveness Conflict Risk

"AgentHub session", "/hub:hub-status", and "how the AgentHub agents are doing" carve a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

18

/

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.

Validation15 / 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
alirezarezvani/claude-skills
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.