langbot-skills-maintenance

Maintain the langbot-skills repository with low duplication. Use when adding, editing, or auditing LangBot skills, references, cases, troubleshooting entries, indexes, or periodic entropy-control checks for this skills repository.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

93%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 tightly written, actionable maintenance skill with concrete commands, a clear workflow, and a clean one-level reference split. The only gap is that the post-edit validation checkpoint points to AGENTS.md rather than spelling out an inline validate-fix-retry loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, using terse classification rules and concrete commands with no padding or explanation of concepts Claude already knows, matching the lean score-5 anchor.	5 / 5
Actionability	It provides copy-paste-ready commands (e.g. `rg "<feature\|error\|case id>" skills`, `bin/lbs case list`, `bin/lbs index --check`) and concrete file-path classification covering the common change types, matching the fully-executable score-5 anchor for an instruction-only skill.	5 / 5
Workflow Clarity	A clear numbered workflow is present with a verification step ('Run the checks in AGENTS.md after edits') and an entropy-check command, but the validation checkpoint is referenced externally rather than given as an explicit inline validate-fix-retry loop, placing it just below the score-5 anchor.	4 / 5
Progressive Disclosure	The body is a concise overview that defers the detailed periodic-audit procedure to the verified one-level-deep file references/curation-workflow.md with a clear closing pointer, matching the well-signaled score-5 anchor.	5 / 5
	Total	19 / 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 pairs a concrete purpose with an explicit 'Use when' trigger covering the repository's asset types. It is comprehensive and distinct, with only minor room to add synonyms or file extensions for trigger coverage.

Dimension	Reasoning	Score
Specificity	The description lists several concrete maintenance actions ('adding, editing, or auditing LangBot skills, references, cases, troubleshooting entries, indexes, or periodic entropy-control checks') but frames them as asset categories rather than the discrete action verbs of the score-5 anchor, so it sits clearly above score 3 but below 5.	4 / 5
Completeness	It explicitly states both what ('Maintain the langbot-skills repository with low duplication') and when ('Use when adding, editing, or auditing...') with concrete trigger phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	It surfaces natural maintainer vocabulary ('adding, editing, or auditing', 'skills, references, cases, troubleshooting entries, indexes') with good coverage, though it omits some synonyms and file extensions, keeping it just below the comprehensive score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	The niche is sharply scoped to the langbot-skills repository and its specific asset types, with triggers unlikely to fire for unrelated skills, matching the clear-niche score-5 anchor.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: langbot-app/LangBot
Path: skills/skills/langbot-skills-maintenance/SKILL.md
Commit: 7803d56

Reviewed: about 3 hours ago

Table of Contents

Discovery Implementation Validation

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.