BC agent-roundtable
Multi-agent roundtable discussion — topic-driven multi-round debate with convergence detection and conclusion generation
As a process C 60/100 · Has gaps — weak spots: result and completion, when it triggers, execution cost
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 77. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 120 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
body-longSKILL.md body ≈ 8820 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 60/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Result and completion. Does not say what the result is
- 40Execution cost. Instruction body is 8820 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 60Consistency. The Hermes dialect needs category and tags
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 75 steps, 1 vague phrases
- 100Failures and branches. 10 branches, has a failure section
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 21 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- -2localhost URLs: will not work for another user
- -45 reference files, but SKILL.md never points to them: the model will not open them
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 120: enough signal without eating the budget
- +4Structure: 34 headings
- +3Step-by-step instructions: 75 items
- +4Has examples (26 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 56.
External checks
ClawHub: suspicious
This looks like a real roundtable discussion tool, but it includes network sharing, external chat notifications, subprocess/browser behavior, and broad persistence that need review before installation.
LLM: suspicious (high) · VirusTotal: · 28 May 2026