How do I install the Langbot Skills Maintenance skill?

Run npx skillmds@latest add gabrielmoreira/langbot-skills-maintenance in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Langbot Skills Maintenance safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Langbot Skills Maintenance?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Langbot Skills Maintenance free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Langbot Skills Maintenance?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Langbot Skills Maintenance by gabrielmoreira

Name: Langbot Skills Maintenance
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

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.

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

LangBot Skills Maintenance

Use this skill before changing reusable assets in this repository.

Workflow

Read AGENTS.md, skills/.env, and the relevant existing skill files.
Classify the change:
- SKILL.md for routing and concise operating rules.
- references/*.md for canonical detailed workflows.
- cases/*.yaml for executable test-plan skeletons.
- suites/*.yaml for reusable groups of case ids.
- fixtures/fixtures.json for deterministic fixture readiness metadata.
- reports/evidence/<run-id>/automation-result.json as automation output and reports/evidence/<run-id>/result.json as final judgment output; neither is a catalog asset to commit.
- troubleshooting/*.yaml for one reusable failure mode.
Search existing assets before adding new files:
- rg "<feature|error|case id>" skills
- bin/lbs case list
- bin/lbs suite list
- bin/lbs fixture list
Put detail in one canonical place and link to it from cases or routing bullets.
Run the checks in AGENTS.md after edits.

Entropy Rules

Prefer extending an existing reference or troubleshooting entry when the root cause is the same.
Keep cases short: setup, action, evidence, pass/fail checks. Do not paste long prompts or debug transcripts when a reference exists.
Put machine-checkable inputs in env, automation_env, or fixtures; put operator-confirmed assumptions in preconditions so test plan can surface manual_check.
Keep suites short: title, intent, tags, and ordered case ids. Do not duplicate case steps inside a suite.
Keep fixture manifests factual: id, title, path, kind, and related case ids. Do not encode environment-specific absolute paths.
Keep troubleshooting entries narrow: symptoms, patterns, likely causes, fixes, related assets.
Do not hardcode local ports, browser profile paths, secrets, tokens, or provider keys.
Use bin/lbs index --check to verify the committed index is current without writing it; run bin/lbs index when the index needs regeneration.

For periodic repository audits, read references/curation-workflow.md.

---name: langbot-skills-maintenancedescription: 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.--- # LangBot Skills Maintenance Use this skill before changing reusable assets in this repository. ## Workflow 1. Read `AGENTS.md`, `skills/.env`, and the relevant existing skill files. 2. Classify the change: - `SKILL.md` for routing and concise operating rules. - `references/*.md` for canonical detailed workflows. - `cases/*.yaml` for executable test-plan skeletons. - `suites/*.yaml` for reusable groups of case ids. - `fixtures/fixtures.json` for deterministic fixture readiness metadata. - `reports/evidence/<run-id>/automation-result.json` as automation output and `reports/evidence/<run-id>/result.json` as final judgment output; neither is a catalog asset to commit. - `troubleshooting/*.yaml` for one reusable failure mode. 3. Search existing assets before adding new files: - `rg "<feature|error|case id>" skills` - `bin/lbs case list` - `bin/lbs suite list` - `bin/lbs fixture list` 4. Put detail in one canonical place and link to it from cases or routing bullets. 5. Run the checks in `AGENTS.md` after edits. ## Entropy Rules - Prefer extending an existing reference or troubleshooting entry when the root cause is the same. - Keep cases short: setup, action, evidence, pass/fail checks. Do not paste long prompts or debug transcripts when a reference exists. - Put machine-checkable inputs in `env`, `automation_env`, or fixtures; put operator-confirmed assumptions in `preconditions` so `test plan` can surface `manual_check`. - Keep suites short: title, intent, tags, and ordered case ids. Do not duplicate case steps inside a suite. - Keep fixture manifests factual: id, title, path, kind, and related case ids. Do not encode environment-specific absolute paths. - Keep troubleshooting entries narrow: symptoms, patterns, likely causes, fixes, related assets. - Do not hardcode local ports, browser profile paths, secrets, tokens, or provider keys. - Use `bin/lbs index --check` to verify the committed index is current without writing it; run `bin/lbs index` when the index needs regeneration. For periodic repository audits, read `references/curation-workflow.md`.

Frequently asked questions