CtrlK
BlogDocsLog inGet started
Tessl Logo

smoke-test

Post-restart smoke tests + auto-fix for gbrain and OpenClaw environments. Tests critical services, auto-fixes known issues, extensible via user-defined test scripts in ~/.gbrain/smoke-tests.d/*.sh.

69

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a well-structured, token-efficient skill file: concrete commands, an explicit test-fix-retest feedback loop, and clean section navigation with no concept-explanation filler or over-nested references.

DimensionReasoningScore

Conciseness

The body is lean with no concept-explanation fluff; every section (Contract, Built-in Tests, design rules, Anti-Patterns, Output Format) carries skill-specific hard-won knowledge rather than padding Claude already knows.

3 / 3

Actionability

Provides concrete copy-paste commands (`gbrain smoke-test`, `bash scripts/smoke-test.sh`), a fully executable custom-test drop-in example, and real env vars; the built-in-test block is an explicitly-labeled template/pattern, which is justified flexibility rather than unexplained pseudocode.

3 / 3

Workflow Clarity

The design rules encode an explicit validate-fix-retest feedback loop ("Test first", "Re-test after fix", "Timeout everything") and the Anti-Patterns reinforce the `pass → fail-detected → fix → re-test` contract, with clear sequencing for an auto-fix/batch operation.

3 / 3

Progressive Disclosure

Single well-organized file with clearly-labeled sections and one-level-deep signaling (the `scripts/smoke-test.sh` path); no nested or over-deep references, and content is appropriately self-contained given no bundled reference files exist.

3 / 3

Total

12

/

12

Passed

Description

72%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and distinctive with strong trigger coverage, but stops short of listing concrete test actions and lacks an explicit "Use when" clause inside the description field itself, leaving "when" only implied.

Suggestions

Add an explicit "Use when ..." clause to the description (e.g., "Use after any gbrain/OpenClaw container restart or when the user asks whether the restart broke anything") so the when-condition is self-contained.

Expand the description with one or two concrete test actions (e.g., "verifies the Bun runtime, GBrain CLI and database, and OpenClaw Codex plugin") to raise specificity from domain-level to action-level.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ("Tests critical services, auto-fixes known issues, extensible via user-defined test scripts") but does not enumerate the specific test actions, which live in the body rather than the description.

2 / 3

Completeness

The description clearly answers "what" but the "when" is only implied by "Post-restart"; an explicit "Use when..." trigger clause lives in the separate triggers field rather than the description itself, so completeness caps at 2.

2 / 3

Trigger Term Quality

The triggers list ("smoke test", "run smoke tests", "container restart check", "health check", "did the restart break anything") gives strong natural-language coverage of phrases a user would actually say.

3 / 3

Distinctiveness Conflict Risk

"Post-restart smoke tests + auto-fix for gbrain and OpenClaw environments" carves out a clear niche that is unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

16

Passed

Repository
garrytan/gbrain
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.