CtrlK
BlogDocsLog inGet started
Tessl Logo

borg-live-debug

Live Borg debugging by exec-ing into the borg-web-ui Docker container. Use when debugging borg commands, writing tests against real borg output, developing borg 2.0 features, or verifying borg behavior before writing code.

71

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable, well-structured debugging skill with copy-paste commands and a clear workflow, held back only slightly by repeated boilerplate and the absence of an explicit error-recovery feedback loop.

Suggestions

Add an explicit validate→fix→retry feedback loop in the workflow (e.g., 'If stderr shows an error, adjust the command and re-run before writing code') to strengthen workflow_clarity.

Factor the recurring 'docker exec -u borg borg-web-ui bash -c' wrapper into a documented shorthand or helper snippet to reduce boilerplate repetition across code blocks.

Consider moving the borg1-vs-borg2 command cheat sheet into a references/ file (e.g., CHEATSHEET.md) and linking to it, keeping SKILL.md as a leaner overview.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude knows Docker/borg — no concept explanations — but the repeated 'docker exec -u borg borg-web-ui bash -c "..."' boilerplate across many blocks and the app-specific Python inspection section could be trimmed slightly.

4 / 5

Actionability

Fully executable, copy-paste-ready docker exec commands, enumerated environment variables, a borg1-vs-borg2 command cheat sheet, and complete temp-repo creation scripts cover the common debugging cases concretely.

5 / 5

Workflow Clarity

A clear Step 1–4 sequence exists with an explicit Step 1 validation checkpoint ('If it's not running, tell the user') and the 'Always run the command first, then write code' rule, but a structured validate→fix→retry feedback loop for error recovery is only implicit.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers and no nested references, and no bundle files exist; the inline borg1/borg2 cheat sheet and temp-repo scripts are reference-like material that could optionally live in separate files, a minor organization gap.

4 / 5

Total

17

/

20

Passed

Description

92%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, specific description that clearly conveys both capability and trigger conditions with concrete actions and minimal fluff. Only minor room for improvement in trigger-term synonym breadth.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'exec-ing into the borg-web-ui Docker container', 'debugging borg commands', 'writing tests against real borg output', 'developing borg 2.0 features', 'verifying borg behavior' — giving comprehensive coverage with no vague filler.

5 / 5

Completeness

Explicitly states the 'what' ('Live Borg debugging by exec-ing into the borg-web-ui Docker container') and the 'when' via a 'Use when ...' clause with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Natural phrases a borg user would say ('debugging borg commands', 'writing tests', 'borg 2.0 features', 'verifying borg behavior') are present, but synonyms and extension variations are thin, stopping short of the comprehensive bar.

4 / 5

Distinctiveness Conflict Risk

The borg-web-ui Docker container / borg 2.0 niche is highly specific with distinct triggers, making accidental activation by unrelated skills very unlikely.

5 / 5

Total

19

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
karanhudia/borg-ui
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.