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.

72

Quality

88%

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

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable with executable commands and a clear, checkpointed workflow, but it is verbose in places (the Rules section duplicates step guidance) and monolithic — detail recipes could be split into reference files for better progressive disclosure.

Suggestions

Remove the redundant 'Rules' section or trim it to only points not already shown in the step commands (e.g. drop restatements of 2>&1, --json, and cleanup).

Move the borg1/borg2 cheat sheet and the temp-repo creation recipes into reference files (e.g. references/cheat-sheet.md, references/test-repo.md) and link to them from SKILL.md to improve progressive disclosure.

Add an explicit 'if the borg command fails, read stderr and adjust env vars before retrying' feedback loop in Step 3 to strengthen error recovery for destructive ops like delete/prune.

DimensionReasoningScore

Conciseness

The body is dense with executable commands, but the final 'Rules' section restates guidance already shown in the steps (capture stderr with 2>&1, use --json, clean up temp repos), so it could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready docker exec commands, a concrete borg1-vs-borg2 cheat sheet, and ready-to-run temp-repo recipes — matching the 'fully executable code/commands' anchor.

3 / 3

Workflow Clarity

Steps 1–4 are clearly sequenced with an explicit validation checkpoint ('Verify the container is running' → tell the user to start it) and a closing Rules checklist, satisfying the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

Well-sectioned with headers and no nested references, but it is a long monolithic SKILL.md with detail content (the cheat sheet, temp-repo and Python-inspection recipes) that could be split into reference files.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 states concrete actions, includes an explicit 'Use when' trigger, and is sharply scoped to the borg-web-ui container niche. It hits the top anchor on every dimension.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Live Borg debugging by exec-ing into the borg-web-ui Docker container' plus debugging commands, writing tests, developing borg 2.0 features, and verifying behavior — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('Live Borg debugging by exec-ing into the borg-web-ui Docker container') and when via a clear 'Use when debugging borg commands, writing tests... or verifying borg behavior' clause.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — 'debugging borg commands', 'writing tests against real borg output', 'developing borg 2.0 features', 'verifying borg behavior' — with good variation rather than jargon.

3 / 3

Distinctiveness Conflict Risk

Tightly scoped to 'borg-web-ui Docker container' and 'borg 2.0 features', giving it a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

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.